Task Design - Paper Prototyping: The Fast and Easy Way to Define and Refine User Interfaces - page 107

Figure 6.2: This type of coffee maker is called a French press, but we didn't want to reveal that to
users because it might bias them toward using the site's search engine—coffee makers were easy
to find via the search engine but hard to find using the links. So we showed them this picture and
said, "Your friend has one of these and it makes great coffee, so you'd like to buy one."
Written, Not Oral
I usually give usability tasks to users in written format so that they can refer back to them as needed.
This is important if the user needs to enter data from the task instructions, such as a server name. But
there are exceptions to this rule. Sometimes for very simple tasks you can give the instructions orally.
Oral instructions are also helpful when you don't want to reveal the spelling of a term, such as, "See if
there are any new treatments for osteoporosis." But when in doubt, use written task instructions.
One Task Per Page
Print each task on a separate page and give them to the users one at a time. This gives you more
flexibility to skip or reorder tasks depending on what happens in the usability test. It also avoids making
users feel bad if they don't complete all the tasks (especially if you have a couple of extra tasks in
reserve). I like to use 5 × 8 index cards for tasks, but regular paper works fine too. See Figure 6.3 for
an example. Have an extra copy on hand in case the user jots something down on the task page.
You've been grading essays. You're seeing the same grammatical problems over and over,
don't they teach English in high school any more? You want to find some sections in The
Longman Handbook pertaining to comma splicing so you can have your students read them.
Figure 6.3: An example of a task used in a study with college-level English teachers. It contains a
subtle joke—can you see it?
Use Humor Carefully, If At All
Write your tasks in a professional but friendly tone. Most usability specialists agree that it's best to
avoid overly clever or "cutesy" tasks. Although humor is a good thing, using it in usability testing can
backfire if it accidentally strikes too close to home or the user feels insulted. I once heard of a task that
read, "You've just been laid off—ha ha! See what outplacement services the HR site offers."
Unfortunately, one of the users had just experienced a painful layoff and started crying. So that's
definitely an example of what not to do!
On the other hand, although paper prototyping is a serious activity, it isn't necessarily a solemn one. I
see nothing wrong with using subtle or lighthearted humor to help establish a relaxed atmosphere in the
test setting, provided that it's appropriate for your audience. The task shown in Figure 6.3 was used in a