Cognitive Walkthrough: See Through a New User's Eyes
A cognitive walkthrough is like role-playing a new user trying a specific task for the first time. It finds usability flaws early by simulating a first-time user's journey. The footgun is confusing it with a holistic review; this method is for specific tasks.
WHY IT EXISTS Most users learn a new system by exploring and doing, not by reading a manual. We need a way to check if a design supports this natural behavior, especially for first-time users. Full usability testing is slow and expensive, so a faster, cheaper inspection method is needed to catch issues early in the design cycle.
THE MENTAL MODEL Think of it as putting on "new user glasses." You pick one critical task, like "sign up for an account," and walk through the interface step-by-step. At each point, you ask: "Would a new user know what to do here? Is the feedback clear?" You are simulating their exploration and potential confusion, not evaluating the system as an expert.
HOW IT WORKS A team defines a specific, realistic task a new user would perform. Then, they go through the interface screen by screen, action by action, asking four key questions at each step: 1. Will the user try to achieve the right outcome? 2. Will the user notice that the correct action is available? 3. Will the user associate the correct action with the outcome they expect? 4. If the correct action is taken, will the user see that progress is being made? This structured questioning reveals gaps in the design's guidance.
WHEN TO USE IT Use it early in the design process, even on paper prototypes or wireframes before any code is written. It is ideal for evaluating critical task flows where a user has a clear goal. It serves as a quick, low-cost method to find major usability hurdles when a full usability study isn't feasible.
WHEN NOT TO USE IT Do not use it for a holistic, big-picture review of your entire system; use a heuristic evaluation for that. A cognitive walkthrough is intentionally task-specific. It is also not a complete replacement for testing with real users, as it only simulates their perspective and cannot capture the full range of unexpected behaviors.
ONE CANONICAL EXAMPLE Imagine evaluating a new e-commerce checkout flow. The task is "buy a single item." The walkthrough starts on the product page. Step 1: "Add to Cart." Question: Is the button obvious to a new user? Step 2: The cart page. Question: Is the "Proceed to Checkout" button clear and does it look like the next logical step? This step-by-step analysis for a single, focused task is the essence of a cognitive walkthrough.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.