Cognitive walkthrough

This article or section is a stub. It does not yet contain enough information to be considered a real article. In other words, it is a short or insufficient piece of information and requires additions.

Draft

Interaction design, user experience and usability and Design and usability methods and techniques series
Type: Design and usability methods and techniques introductory article

Introduction

According to the NASA usability toolkit, retrieved 12:36, 18 March 2011 (CET), A cognitive walkthroug, is a “process of going step by step through a product or system design and getting reactions from key team players and typical users. One or two members of the design team can guide the walk through while one or more users will comment as the walk through proceeds.”

The Fluid project, retrieved 12:36, 18 March 2011 (CET), provides the following definition: “A cognitive walkthrough is a step-by-step exploration of a service to see how well a particular type of user, usually represented by a persona, is able to accomplish a particular objective or set of objectives. The objectives selected for testing are dictated by the persona that is chosen.”

James Hom defines cognitive walthrough as “review technique where expert evaluators construct task scenarios from a specification or early prototype and then role play the part of a user working with that interface--"walking through" the interface. They act as if the interface was actually built and they (in the role of a typical user) was working through the tasks. Each step the user would take is scrutinized: impasses where the interface blocks the "user" from completing the task indicate that the interface is missing something. Convoluted, circuitous paths through function sequences indicate that the interface needs a new function that simplifies the task and collapses the function sequence.”

Methods

Fluid project overview

The Fluid project roughly suggest the following procedure.

(1) Choose a user from whose perspective the walkthrough will be done. You may choose a persona for that.

(2) Define what the person wants to achieve

(3) Define the steps that this person should do in order to achive her/his goals

(4) Perform the task and take notes about the following kind of issues for each step:

Will the user know what to do at this step?
Is complex problem solving needed to figure out what to do?
Will they know that they did the right thing (if they manage) and are making progress towards their goal?
Is complex problem solving needed to interpret the feedback?

This project also defines a much more elaborated UX Walkthrough Process. In particular, it suggests to formalize the inspection process along three axis:

A protocol that clearly specifies what we are going to do, and what information we are going to capture along the way.
A predetermined clearly specified target that we are going to inspect: (product, version, instance, set of chunks) - the thing we're going to do it to.
A report template specifying the format, style and content of the report of the information we capture.

(retrieved 12:36, 18 March 2011 (CET))

Look at their Generic UX Walkthrough Report Template if you need an example

Wharton et al. 1994 (CW3)

According to Mahatody et al. (2010), this variant which the labelled "CW3" works like this: “the evaluator is invited to imagine a specific and credible scenario for each action that users must run to accomplish their task. To make the scenario credible, the evaluator must justify each action with respect to the user's background and knowledge and the feedback from the interface. To assess each action in the task, the evaluator must answer four questions related to various user thoughts and actions: 1) what is the user thinking at the beginning of the action (Q1: Will the user try to achieve the right effect?, 2) is the user able to locate the command (Q2: Will the user notice that the correct action is available?), 3) is the user able to identify the command (Q3: Will the user associate the correct action with the effect that user is trying to achieve?) and 4) is the user able to interpret the feedback (Q4: If the correct action is performed, will the user see that progress is being made toward solution of the task?).”

Mahatody et al. then report that “most of the reviewing authors agreed that CW is tedious, despite being easy to learn and use.”

Streamlined CW - Spencer, 2000

Spencer (2000), presents the following model for a streamlined Cognitive Walkthrough process, adapted directly from Wharton, et al. (1994). Spencer argued that implementing a cognitive walkthrough procedure is not obvious and suggest that in many situations a stream-lined version would be more successful. He suggests to adopt the following ground rules for two reasons: (1) Ensure that developers will not consider the procedure as "lost time" and (2) make sure that they don't become defensive:

Avoid design discussions (no designing, no defining of a design).
No debating of cognitive theory
The usability specialist is the leader of the session

Second, he argues in favor of simplication, in particular with respect to Warton:

Collapse/simplify Warton's walk-through questions.
Capturing Less Data

According to results of a study he conducted, {{quotation|Streamlining the walkthrough may trade-off granularity for coverage, but without that trade off, program managers and developers may perceive the walkthrough as being an inefficient use of time. Performing a streamlined CW is a good way to profile a user interface for potential problem areas, identify many steps that may be problematic for users, and accurately predict many usability problems. However the method will probably result in a few false positives.

Summary of the streamline cognitive walkthrough:

Define inputs to the walkthrough
1. Identification of users
2. Sample tasks for evaluation
3. Action sequences for completing the tasks
4. Description or implementation of interface
Convene the walkthrough
1. Describe the goals of the walkthrough
2. Describe what will be done during the CW
3. Describe what will not be done during the
4. lkthrough
5. Explicitly defuse defensiveness
6. Post ground rules in a visible place
7. Assign roles
8. Appeal for submission to leadership
Walkthrough the action sequences for each task
1. Tell a credible story for these two questions:
  - Will the user know what to do at this step?
  - If the user does the right thing, will they know that they did the right thing, and are making progress towards their goal?
2. Maintain control of the CW, enforce the ground rules (see below)
Record critical information
1. Possible learnability problems
2. Design ideas
3. Design gaps
4. Problems in the Task Analysis
Revise the interface to fix the problems