What is cognitive walkthrough?

A cognitive walkthrough is a usability inspection method where evaluators step through a specific task in an interface and, at each action, ask whether a new user would know what to do, find the control and understand the result.

Updated

Where it comes from

The method was developed by Clayton Lewis, Peter Polson and colleagues around 1990, based on a theory of how people learn software by exploring it. Wharton, Rieman, Lewis and Polson's practitioner's guide (1994) is the standard reference. It is built for learnability: how well a product supports someone using it for the first time without training.

The four questions

For every action in the correct sequence, the evaluators ask:

  • Will the user try to achieve the right effect? Do they know this step is needed?
  • Will the user notice that the correct action is available?
  • Will the user associate the correct action with the effect they want?
  • If the correct action is performed, will the user see that progress is being made?

How to run one

  • Define the user: who they are and what they already know. A new admin and a returning editor will fail at different steps.
  • Pick a few tasks that matter, such as creating a first project or inviting a teammate, and write down the correct sequence of actions for each. A task analysis is the usual source.
  • Walk through each action as a group, answer the four questions, and record a failure story for every "no": what the user would expect, and what they'd do instead.
  • Turn failure stories into fixes, and check the riskiest ones with a usability test.

Cognitive walkthrough vs heuristic evaluation

Both are expert inspections without participants, and they answer different questions. A heuristic evaluation reviews the whole interface against a set of principles, such as Nielsen's 10, and catches problems anywhere on the screen. A cognitive walkthrough follows one task, step by step, from a first-time user's point of view, and catches the places where that user would get lost. Use a walkthrough for onboarding and first-run flows; use a heuristic evaluation for a broad review.

Running the full four questions on every step is slow. Rick Spencer's streamlined cognitive walkthrough (2000) cut it to two questions per step, which is easier to fit into a product team's week.

Go deeper

Questions

Does a cognitive walkthrough replace usability testing?

No. It predicts where a first-time user might struggle, based on the evaluators' judgement. It's cheap and needs no recruiting, so it's useful early, but evaluators know the product and miss problems that only show up when someone unfamiliar tries the task. Test the flows that matter with participants.

Who should take part in a cognitive walkthrough?

A small group, often three to five people: a designer, a researcher, a product manager, and ideally someone who didn't build the flow. One person records failure stories. The designer of the flow should answer questions about it, not argue with each failure.

What questions does the streamlined cognitive walkthrough use?

Two per step: will the user know what to do at this step, and if they do the right thing, will they know they did the right thing and are making progress toward their goal?

Next step

Run the study, not just the method

Great Question handles recruiting from your own customers, scheduling, incentives, interviews, tests and analysis in one place.

Book a demo

No credit card required.

Related terms

Full glossary
  • Task analysis

    Task analysis in UX is the process of breaking down how people accomplish a goal into the steps, decisions, tools and information each step needs, so you can design a product around the work as people actually do it.

  • Think-aloud protocol

    A think-aloud protocol is a usability research method where participants say what they are thinking, looking at and trying to do while they complete a task, so you hear the reasoning behind each action instead of guessing at it.

  • Evaluative research

    Evaluative research tests an existing design, prototype or product against a goal, to find out whether people can use it and whether it does what the team intended. It checks a solution, where generative research looks for the problem.