Database Reference
In-Depth Information
Figure5.6:
Asamplepaperprototype.PartsoftheUIaredifferentiatedwithstickynotes;informationishand-
written so it can be added to or changed with users on the fly. Note that the popup leaves space for adding or
changing information in the moment.
The validation rounds of prototype interviews take the product concepts back into the
real world of the user and put them in the context of the user's life. This is another round
of immersion and “get real” for the design team. It is the ultimate test of product recep-
tion—inviting the user to do their real tasks using a mockup in a “let's pretend” situation
instead of getting a demo and being asked for an opinion. Just as in the initial Contextu-
al Inquiry interviews, people can respond with reliable information when they are doing
their own activities in their own life context. This is very different from a lab or simulator
with pre-defined tasks set up by the interviewer. Immersing the new product concept in the
world of the user is the best way to determine if the team came up with something of last-
ing value—while at the same time working out the final details of the design itself.
*
Identifyingproductconceptsinthiswayalsosupportsiterativedevelopmentprocesses.Itwouldbenatural
to assign each product concept to a different Scrum team, for example; and the vision elements can be
quickly evolved into user stories.
*
This is a similar approach to that advocated by Lean Design—get quickly to a prototype good enough to
testyourkeydesignquestionsandnomore.Whenthosequestionsareanswered,thenyou'rereadyforthe
next level of detail.
