Cognitive Walkthrough
Cognitive Walkthrough Method · Also known as: Cognitive Walkthrough, CW Analysis
Cognitive Walkthrough is an inspection method for evaluating interface designs by simulating and analyzing how users will learn to use a system through exploration and trial. Developed by Clayton Lewis, Peter Polson, Cathleen Wharton, and John Rieman in 1990, this method is grounded in cognitive psychology and focuses specifically on learnability—whether first-time or occasional users can discover how to perform tasks without formal training. Evaluators role-play user actions, answer a set of critical questions about feedback and discovery at each step, and document usability problems.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Conduct Cognitive Walkthroughs early and iteratively, starting with wireframes or prototypes before full implementation. Best for learnability-critical interfaces where self-discovery is important (new systems, novel features, first-time user experience). Particularly effective for infrequent tasks where training is impractical. Do not use as a substitute for usability testing; combine with user studies for comprehensive evaluation.
Strengths & limitations
- Focuses specifically on learnability through exploration; identifies problems that affect first-time users.
- Requires no actual users, saving time and cost in early design iterations.
- Grounded in cognitive psychology; provides explanatory power for why problems exist, not just what they are.
- Thorough and systematic; structured questions ensure consistent evaluation across tasks and interfaces.
- Time-consuming; thorough walkthroughs of complex interfaces can take hours or days.
- Requires evaluator expertise in cognitive psychology and task domain; quality depends on reviewer skill.
- Difficult to simulate unexpected user strategies or behaviors; assumes somewhat rational task progression.
- May miss problems that emerge under time pressure, stress, or multi-tasking contexts.
Frequently asked
How detailed should my persona be for a cognitive walkthrough?
Include domain knowledge, prior experience with similar systems, and motivation for the task. A persona for a bank app might note: 'Occasional user, comfortable with web, new to mobile banking.' Personas should be specific enough to inform cognitive simulation.
What should I do if I find conflicting problems—one design choice helps one user learn but hinders another?
Document both observations and prioritize based on your target user. If primary users are novices, prioritize novice learnability; if they are power users, optimize for efficiency. Consider if a design can support both (e.g., progressive disclosure).
Can I skip the cognitive walkthrough if I plan to do user testing?
Ideally, no. Walkthroughs catch problems inexpensively in design iteration; testing validates fixes. Combining both is most effective. However, if time and budget are extremely constrained, prioritize walkthrough for novel interfaces and testing for iterative refinements.
Sources
- Lewis, C., Polson, P. G., Wharton, C., & Rieman, J. (1990). Testing a walkthrough methodology for specifying and evaluating user interface designs. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 387–392). link ↗
- Wharton, C., Rieman, J., Lewis, C., & Polson, P. (1994). The cognitive walkthrough method: A practitioner's guide. In J. Nielsen & R. L. Mack (Eds.), Usability Inspection Methods (pp. 105–140). John Wiley & Sons. ISBN: 0-471-01877-5
How to cite this page
ScholarGate. (2026, June 3). Cognitive Walkthrough Method. ScholarGate. https://scholargate.app/en/human-computer-interaction/cognitive-walkthrough
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Heuristic EvaluationHuman Computer Interaction↔ compare
- KLM-GOMSHuman Computer Interaction↔ compare
- Pluralistic WalkthroughHuman Computer Interaction↔ compare
- Think-Aloud ProtocolHuman Computer Interaction↔ compare