Process and Philosophy

In our experience over the years we've found the most successful projects have clear-cut expectations of process, communication, timeline and scope. Any project -- whether it be a website redesign, email campaign or even just a new interactive feature for an existing website -- can get frustrating and disruptive if these core values aren't in place to start.

Below we've detailed the basic "flow" and other considerations for some common projects we encounter. Adhering to these guidelines will ensure a productive process that ends up with your complete satisfaction!

Website Design/Redesign

The mainstay of your online presence, your website can be everything from a corporate brochure to an interactive sales & support resource. Its purpose will dictate how we build it.

1. Develop Site Map and Purpose
2. Identify any interactive technology or features for website
3. Gather sample content and create "formatting rules" for your pages
4. Design layouts
5. Build working template files and "shell" of your pages
6. Build back-end technology to be used to create pages, interact with features, etc.
7. Insert content for all the pages as provided by the client
8. Final proofs
9. Launch!

Email Campaign

There is so much more to an email campaign than just "hitting 'Send'". Our goal is to flush out all those questions ahead of time.

1. Identify Goal of campaign
2. Review policies and procedures for effective, compliant email marketing
3. Develop content (or sample content) of email
4. Design layout, create proofs
5. Test mailing
6. Import your list, then send it out!

Interactive Feature (Dynamic Content)

When dynamic content is done right, everything is in place, navigation and flow are logical and planned, both for the visitor and the administrator. In short, you take it for granted (and you're supposed to!).

1. Start with the result - what is the visitor supposed to see?
2. Identify the data points that build this result
3. Identify how those data points are going to be manipulated (this part is key, and is usually requires choices by the client)
4. What data points are being administered versus pre-programmed (or updated without an administrative tool)?
5. Build the framework, sample output
6. Build the administrative section
7. Test, test, test!
8. Input the rest of your data
9. Go live