I like to break things down into chunks. So the first thing I do when I talk with a client is to get a feel for what the overall purpose of the web project is. What’s the end game, or goal of this endeavor?
It always helps me know the history of the project and how it has morphed over the years. Once I feel like I have a feel for what my client wants, it’s time to jump into the details…
- Measurable goals for success
- Defining the audience
- Stakeholders and their needs
- Unique branding constraints
- Current competition for this type of project
Ok, so now we have some details. This is a great first step, but we need to break these things down into more granular details and put a timeframe on them.
- Specific deliverables
- User stories
- Specific timelines
Yay! Deliverables and dates to stick them to! User stories to understand the proper flow! Now let’s start framing this house out.
The overall features of the site
Now we have a structural understanding, and can flesh out the visual side.
- Mood boards
- Brand reinforcment
- Define the visual style
- Mockup pages
Ok all we need to do now is take the mockups and build them into real web pages!
- Hosting and domains
- Site configuration & page setup
- Coding templates and scripts
- Widgets or plugins
Once the site or application is built, it’s time to hammer it with testing. We need to make sure that all content is there and that every deliverable is in it’s final state. Does it make sense to the user? If we’re having strange experiences while using the developed product, we need to iterate and go back to the drawing board.
- Staging link
- Quality assurance and browser/device testing
- User testing