TABLE OF CONTENTS Task design is one of the most important aspects of usability testing. You don't just watch users do whatever they want with the interface; you create specific tasks that cover what you want to learn. A good task is like a spotlight that illuminates your interface, showing you the parts that work well and the issues that get in users' way. A good task provides reliable data about key issues so that you get the most from your usability study. But a poor task can mask problems or even turn up false ones. For example, if you ask users to do something that they would never do in real life and they fail, it's difficult to tell whether the interface really has a problem or if you've created an artificial one.
As important as task design is, it isn't easy to do it well. I think task design is probably the hardest part of usability testing, and even after 10 years I'm still learning. This chapter shows you what has worked for me and helps you avoid some common pitfalls.
So what makes a good task? A good task has the following characteristics. (Except as noted, this discussion applies to tasks used for any type of usability testing, not just paper prototypes.)
Is based on a goal that matters to the user profile you've chosen.
Covers questions important to the success of your product and business.
Has appropriate scope not too broad, not too specific.
Has...
