Cognitive Walkthrough

The Cognitive Walkthrough (CW) to German cognitive passage, thinking through a problem, is a usability inspection method and belongs to the analytical evaluation method as opposed to empirical evaluation methods such as usability test. In the Cognitive Walkthrough is a usability expert put in a hypothetical user and analyzed concrete prescribed courses of action. He assumes that the user will go the path of least cognitive effort.

The Cognitive Walkthrough was developed in the early 90s by Wharton and others and based on the theory for exploratory -based learning that comes from cognitive science.

Objectives

With a Cognitive Walkthrough, especially the ease of learning the operation of a product is determined. Goal of Cognitive Walkthroughs is to tell the designer whether, where and why the design will affect the interaction user - product. Differences between the user and the developer regarding the management of tasks view will be revealed. Even a bad menu label and insufficient reporting of the system can be recognized by a cognitive walkthrough.

Implementation

The sequence of a cognitive walkthrough is divided into four steps.

Step 1: Define Input

First, the cognitive walkthrough needs to be well prepared.

• User characteristics: The typical user group of the product is defined, ie which groups of people mainly use the product and made ​​what knowledge and experiences with them.
• Example tasks: After determining the user characteristics one or more tasks are determined that the fictitious user wants done. It is important that typical and realistic tasks are selected.
• Action sequences: For each of the tasks is determined which way the visitor will go ideally, to do its job.

Step 2: Investigation of the sequence of actions

The appraiser will now check the individual steps of the correct solution path, with the previously necessary conditions, and the resulting consequences are to think through for each user input. The following questions may be helpful to:

• If the user try to achieve the right effect?
• If the user know that the correct action is available?
• If the user is a connection between the correct action and the desired effect?
• If the correct action is performed: If the user identify progress made, so get feedback?

Step 3: Logging of critical information

In this phase of the Cognitive Walkthroughs the appraiser maintains two types of information which he has obtained during the analysis of the product:

• What information needs in terms of knowledge and experience of the user to successfully completing the various action steps
• Data on actions that are likely to lead to incorrect operation and thus to problems when users
• In addition, the alleged reasons for the incorrect operation are indicated.

During the test, the pre-established processes should not be changed.

Step 4: Revision of the interface

To derive from a Cognitive Walkthrough for improvement, various possibilities for help in resolving this error. It is crucial to know what the problem occurs. As mentioned in the action sequences may also help the four questions to identify possible solutions.

Example: If the user does not realize that the correct function is available, different approaches to solving the problem offer:

• (highlight button link placed in the middle) clearer presentation of the required action
• Button, rename menu item
• Remove redundant information so that the required is immediately visible

Pros and Cons

The Benefits of Cognitive Walkthroughs compared to other methods are that it is the only method for checking the handling of a product. Furthermore, it is positive to note that it is quickly and easily performed and causes only a very low cost. In addition, it can already be used in a very early stage of development, when user testing are still impracticable.

The disadvantage is that experts test and not an actual user. Intricately is the previous very detailed task analysis and that a separate cognitive walkthrough must be developed for each task.