ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
USABILITY TESTING TEMPLATE (make a copy of this template)
2
Goals/Objectives:Why are you doing the test? What are you hoping to learn?
3
Tasks:What are two tasks you want users to accomplish during your test? For each task, create a scenario to contextualize the action you are asking the user to perform.
4
Sample Task: Create a meeting in Outlook.
5
6
Goal/Output:Schedule a meeting with one other person in Outlook.
7
Assumptions:Meeting room is available.
8
Scenario/Steps:1. Open Outlook.
2. Click on New Appointment.
3. Enter Subject, Pick Location, Time.
4. Click on Invite Attendees.
A. Add one name to the "To:" field.
5. Click Send.
9
Success Criteria:The meeting is successfully scheduled.
10
Notes:
11
Usability Testing Template Rules
12
13
Task Number and Name: Give each task a brief descriptive name and a number. The name helps you remember what its purpose is, and the numbers are useful in usability testing because you can ask the observers things such as, “Shall we skip 3 this time and go right to 4?” without discussing the content of the tasks in front of the users.
14
Goal/Outputs: What will users have accomplished when they’re done with the task? Is there a tangible output? How will they know the task is complete? What might the users do to be sure?
15
Assumptions: Assumptions are the conditions and prerequisites that are in place at the start of the task. The assumptions depend on what you want to learn from the task. For example, if a task explores how users recover from an error caused by a duplicate record, your assumptions include the condition(s) that cause the error to occur, such as, “An employee with the same name already exists in the database.”
16
Scenario/Steps: Write down the steps you expect the user will go through in completing the task. This helps you identify the inputs and assumptions that you’ll need to create. Writing down the expected steps can also be helpful if there will be observers who aren’t as familiar with the interface as you are. Keep the steps mostly at a screen level—no need to list every field on the order form, just say, “Order form.” Some tasks have multiple paths that lead to success, so jot down any variations, such as “Search OR navigate to lawn and garden page.” Optional steps can be noted in parentheses (e.g., review privacy policy).
17
Success Criteria:Specific measurable criteria for determining that the task was successfully completed. For example, a URL or snippet of URL (e.g., thankyou.html), or a success question (e.g., “What was the cost of the quoted insurance policy?” A. $125.00 [success], B. $150.00, C. $300.00, D. $110.00).
18
Notes: The notes section might have several types of information, including the reasons why you created the task, how you’ll conduct it, specific things to watch for, and questions to ask users after the task is complete. Information to include in the notes varies depending on what’s being tested. Write down whatever information you think will be useful to have on hand during the usability tests, and give copies of the completed task templates to usability test observers.
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100