A cognitive walkthrough is a structured usability inspection method in which an evaluator steps through a task the way a first-time user would, one action at a time, and asks a small set of questions at each step. The method focuses on learnability: whether someone who has never used the interface before can figure out what to do next without training or documentation. Because you simulate the user's reasoning rather than recruit participants, a walkthrough can be run early, cheaply, and repeatedly on sketches, wireframes, or working prototypes.
The operational heart of the method is the four-question framework applied at every action in the task sequence. Question 1 asks whether the user will try to achieve the right goal at this point. Question 2 asks whether the user will notice that the correct action is actually available on screen. Question 3 asks whether the user will recognize that this visible control is the one that advances their goal, which is often a labeling and wording problem. Question 4 asks whether, after acting, the user will understand the feedback well enough to know they made progress. A "no" at any question is a documented usability failure, and the question that failed tells you what kind of fix is needed.
As you watch the videos below, pay attention to how the evaluator defines the task and the correct action sequence before asking any questions, how a user persona or assumption set shapes the answers, and how failure stories are written down so they can later be rated for severity. Notice also how the same questioning logic shows up outside interface design, which is a good sign that you have understood the underlying idea rather than memorized four sentences.
This is the core overview video for the method: a short explanation from Nielsen Norman Group of what a cognitive walkthrough is, that it is a task-based usability inspection technique, and that its specific purpose is evaluating learnability for first-time users. Expect it to cover how you define tasks and the correct action sequence in advance, and how an evaluator walks each step asking the guiding questions about goals, visible actions, recognizing the right control, and interpreting feedback. It should also indicate when in a design process this method is worth using.
It is the most direct match to this topic, coming from the usability consultancy most associated with inspection methods, and it frames all four evaluative questions in the context of a single step-by-step procedure.
This video presents three ways to pretest a survey, one of which is a cognitive walkthrough used with target users to check whether questions are understood as intended. It contrasts that with mechanical testing and other checks, showing where each approach catches different kinds of problems. The walkthrough portion illustrates the method applied to wording and comprehension rather than to screens and buttons.
It reinforces Question 3 in particular, since recognizing an action as correct is largely a matter of whether labels and wording match the user's mental vocabulary, and it shows the questioning technique transferring to a different artifact.
This short video distinguishes research goals, research questions, and hypotheses and explains how each one focuses a user research study. It covers why a clearly stated goal comes before the questions you ask, and how vague goals lead to unfocused findings. The framing is general to user research rather than specific to inspection methods.
It supports Question 1 by sharpening what a "goal" actually is, which is exactly the distinction you need when deciding whether a simulated user would form the right goal at a given step, and it helps you set up a defensible task scenario before you begin walking through it.
Together these videos build the recall needed for MO1 by naming the method, its task-based setup, and the guiding questions asked at each action step. The main NNgroup walkthrough video gives you the procedure you will actually execute on a peer or self-developed prototype for MO2, while the research goals video helps you define the task and user assumptions precisely enough that your documented failures are credible. The survey testing video extends the same questioning logic to wording and comprehension, which feeds MO3 by helping you judge whether a given failure is a cosmetic labeling issue or a blocker that prevents task completion, and therefore how to prioritize revisions.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.