Cognitive Walkthrough

from Wikipedia, the free encyclopedia

The Cognitive Walkthrough ( CW ), in German cognitive passage , thinking through a problem , is a usability inspection method and belongs to the analytical evaluation method in contrast to empirical evaluation methods such as the usability test . In the cognitive walkthrough, a usability expert puts himself in the position of a hypothetical user and analyzes specific, predetermined courses of action. He assumes that the user will take the path with the least amount of cognitive effort.

The Cognitive Walkthrough was developed in the early 1990s by Cathleen Wharton, among others, and is based on the theory of exploratory learning that comes from cognitive science .

aims

A cognitive walkthrough is primarily used to determine how easy it is to use a product. The aim of a cognitive walkthrough is to explain to the designer whether, where and why the design will affect the interaction between user and product. Differences between the user's and the developer's point of view regarding the accomplishment of tasks are revealed. Bad menu names and insufficient feedback from the system can also be recognized by a cognitive walkthrough.

execution

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

1st step: define input

First of all, the cognitive walkthrough must be well prepared.

  • User characteristics: The typical user group of the product is defined, ie which groups of people mainly use the product and what knowledge and experience they have.
  • Sample tasks: After determining the user characteristics, one or more tasks are determined that the fictitious user wants to do. It is important that typical and realistic tasks are chosen.
  • Action sequences: For each of the tasks, it is determined which path the visitor will ideally take in order to complete his task.

Step 2: Examination of the sequence of actions

The expert now checks the individual steps of the correct solution, whereby the previously necessary requirements and the resulting consequences must be thought through for each user input. The following questions can be helpful:

  • Will the user try to get the right effect?
  • Will the user realize that the correct action is available?
  • Will the user make a connection between the correct action and the desired effect?
  • If the correct action has been taken: Will the user recognize the progress, i.e. receive feedback?

3rd step: logging of critical information

In this phase of the cognitive walkthrough, the appraiser records two types of information obtained during the analysis of the product:

  • Which information, in the form of knowledge and experience, is required by the user to successfully complete the various steps
  • Data on actions that are likely to lead to incorrect operation and thus to problems for the user
  • In addition, the presumed reasons for the incorrect operation must be stated.

The previously defined processes should not be changed during the test.

4th step: Revision of the interface

In order to derive suggestions for improvement from a cognitive walkthrough, various options can help to correct these errors. It is crucial to know what the problem is. As with the action sequences before, the four questions can help to identify the possible solutions.

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

  • Clearer presentation of the required action (highlight button, place link in the middle)
  • Rename button, menu item
  • Remove unnecessary information so that what you need is immediately visible

Advantages and disadvantages

The advantages of the cognitive walkthrough compared to other methods are that it is the only method for checking the handling of a product. Furthermore, it should be noted positively that it can be carried out quickly and easily and only causes low costs. In addition, it can be used at an early stage of development when user testing is still impractical.

The disadvantage is that experts test and not actual users. The preceding detailed task analysis is complex and a separate cognitive walkthrough must be developed for each task.

literature

  • Clayton Lewis, Cathleen Wharton: Cognitive walkthroughs. In: Martin G. Helander, Thomas K. Landauer, Prasad V. Prabhu (eds.): Handbook of Human-Computer Interactions. 2., completely revised edition. Elsevier Press, Amsterdam 1997, ISBN 0-444-81862-6 , pp. 717-732.
  • Cathleen Wharton, John Rieman, Clayton Lewis, Peter Polson: The cognitive walkthrough method. A practioner's guide. In: Jakob Nielsen, Robert L. Mack (Ed.): Usability Inspection Methods. John Wiley & Sons, New York NY et al. 1994, ISBN 0-471-01877-5 , pp. 105-140.
  • Ursula Schulz, Ulrike Spree: Cognitive Walkthrough ( Memento from March 6, 2016 in the Internet Archive ) University of Applied Sciences Hamburg.