Cognitive Walkthrough

Basic steps

1. Convene several analysts (typically usability experts)
2. Determine users and context
3. Specify representative task(s) and the actions needed to complete the task(s)
4. Walk through the action sequence, answering and documenting the analysis questions for each action

Possible levels of granularity for task analysis

• Micro level (e.g. mouse clicks, key presses)
• Intermediate level (e.g. entering a string, selecting a link)
• Abstract level (e.g. logging in, spell checking a document)

Analysis questions from Wharton et al. (in chapter 5 of Nielsen and Mack, 1993)

1. Will the user try to achieve the right effect?
2. Will the user notice that the correct action is available?
3. Will the user associate the correct action with the effect that user is trying to achieve?
4. If the correct action is performed, will the user see that progress is being made toward the solution of the task?

Revised questions from Lewis and Riemann

1. Will users be trying to produce whatever effect the action has?
2. Will users see the control (button, menu, switch, etc.) for the action?
3. Once users find the control, will they recognize that it produces the effect they want?
4. After the action is taken, will users understand the feedback they get, so they can go on to the next action with confidence?

Streamlined analysis questions (Rick Spencer)

1. Will the user know what to do at this step?
2. If the user does the right thing, will the user know that he or she did the right thing, and is making progress towards the goal?

Issues for discussion

• What is the appropiate level of task analysis?
• Which usability goals does the CW address?
• When can the CW be performed?
• When should design recommendations be discussed?