This work is licensed under the Creative Commons Attribution-Share
Alike 3.0 Unported License. To view a copy of this license, visit http://
creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
Commons, 171 Second Street, Suite 300, San Francisco, California,
• Drawing separate paper prototype(s) for each
functionality (user story)
• Making changes in the user story, if needed
• Putting the pieces together
• Taking photos of the process
• Finding missing stories / prototypes
• Creating tasks based on the scenarios
• Creating related interview questions
Designing the right tasks
“Years ago, we helped with a study of Ikea.com, looking at how people found
products on the site.When we got there, they'd already started the testing process
and were using tasks like "Find a bookcase." Interestingly, every participant did
exactly the same thing: they went to the search box and typed "bookcase".
Upon our suggestion, the team made a subtle change to the instructions they were
giving their participants: "You have 200+ books in your ﬁction collection, currently
in boxes strewn around your living room. Find a way to organize them."
We instantly saw a change in how the participants behaved with the design. Most
clicked through the various categories, looking for some sort of storage solution.
Few used Search, typing in phrases like "Shelves" and "Storage Systems". And,
nobody searched on "bookcase".”
(Jared M. Spool)
What to focus on?
• Terminology. Do they understand the terms in the
• Navigation. Does the ﬂow match what users
• Content. Does it provide the right level of
• Page layout. Is content organized as users expect?
• Functionality. What additional features are desired?
• Test person
• “Paper computer”
• Ginsburg, S. (2009). An agile approach to iPhone design: Paper prototyping +
user testing. http://www.slideshare.net/ginsburgdesign/an-agile-approach-to-
• Spool, J.M. (2005). Seven Common Usability Testing Mistakes. http://