I received this while working with a design firm, Rolling Orange. It's an excellent concise description of how to react to an initial set of wireframes. People often skimp on this step and that's a big problem that will come back to haunt you. This description makes that clear and more importantly gives people a guide to interpret and analyze the wireframes.
Elaboration Phase: Concept & Design: Wireframes
ABOUT THIS MILESTONE
This is the first draft of the wireframes for the new site. This represents our initial recommendations for navigation, functionality, and content, based on the findings of our Research and Strategy phase. The purpose of these wireframes is to create a site structure, functionality, and messaging platform that will serve as the foundation of your site. We will address visual design ("look and feel") only after we have approved wireframes.
WHAT SHOULD I EVALUATE?
- Look at this phase as an opportunity‚ now is the time to make it right.
- This draft is a starting point, so it's flexible and we expect it will evolve. Now is the time to suggest changes and explore new solutions.
- Does the architecture reflect the recommendations made in the Research & Strategy phase?
- Does the navigation and architecture address the functional needs of the audience per the Persona document?
- Is the proposed design "buildable" based on your understanding of supporting technologies and systems?
- Can your organization sufficiently manage and sustain the proposed design?
- Did we miss anything?
WHAT'S NEXT?
We will refine these wireframes based on your feedback.
PROJECT TIP
Think like your customer! Think about user goals and their frame of mind (“I’m researching, I’m applying, I’m managing”). Pretend you don’t know any of this—would you understand it as a first-time reader? Think simple—include just what users need and no more. If it’s “nice to have,” cut it.
A blog about software development, primarily in Java and about web applications.
About Me
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment