In this phase, the first examples are derived. It is the most intense, complex phase and involves the most creativity, coordination, and inspiration. The project requirements document from the previous phase should provide all of the answers as to what the project should accomplish, but it is in this phase that the development team derives what the product will be.
We will:
decide on some ideas...
... define the information architecture for the product. I like to always have simplicity in mind when creating a structure.
balance giving the user a sense of control, and controlling their path
It is important when "designing the information" to always be thinking of your audience - your users. We have already logically organized the content, now were are crafting an experience. User scenerios help with this. One of the more basic ways I accomplish this is by simply asking questions that the user may have and providing those answers which are found in the content we have. The resulting groups of answers may form a structure. The questions are derived from both our knowledge of our audience and from our list of site goals.
The information architecture needs to be prototyped and checked for proper user interaction. When prototyping it is entirely necessary to include the content. This prototype should be shared with the client.
Remember we are crafting a logical user experience, logical-simple access to information, interaction, amd support for an interface first. Then we can look at visuals. The IA prototype will not use visuals.
Ahhh ... how will this information be delivered?
This is a good time for some usability testing.
After the first prototype is approved we move on.
to
storyboarding and visual design
( same time )
The purpose of visual design is to make it as easy as possible for users to understand your message - it supports and enhances the Information Design.
" Success is measured by how quickly and effectively you communicate your ideas to the users .... add emphasis to important elements design for clarity and impact ....
Visual design is a tool for relaying the message, it is not the message. "
... how content is interpreted is dictated by how it is visually communicated ...
less is more
In the end we will deliver a visual prototype and if necessary ( and if there
is time ) story boards (usually first but sometimes what we create is onften a
mix between storyboards and prototype). A visual prototype on paper or as an image
file is not good enough ( and in fact is only a story board). It must be presented
in the medium it will be delivered. Multiple story boards may be needed to illustrate
a particular "feature" or narrative.
After the prototype is approved, we create a style guide to govern production.
Deliverables: detailed site map, prototypes, usability test results, storyboards, visual style guide and specifications, technology project plan.
We must always indicate to the user:
where they are
what can they do
where can they go
storyboards
page mockups of all of the elements which need to be represented on the page and their rough locations
prototypes
the prototype is like a mini site that explores one of the main functions of the website.