A cognitive walkthrough produces a pile of raw observations: at step 4 the user would not know the "Submit" control exists, at step 7 the feedback message does not confirm success, and so on. On its own, that list is not very useful to a design team. The real work of this topic is turning those individual breakdowns into something a designer can act on — grouping related failures into patterns, judging which ones matter most, writing recommendations that are specific enough to implement, and presenting them in a way that invites collaboration rather than defensiveness.
This topic also asks you to be honest about what the method can and cannot tell you. A cognitive walkthrough is an analytic, expert-driven inspection built around a specific task and an assumed user. It does not measure how long real people take, how they feel, or what they do when they wander off the happy path. Knowing those limits keeps your report credible and helps you say clearly which claims are evidence-based predictions and which would need user testing to confirm.
As you watch the videos below, pay attention to three things: how severity is decided (and on what criteria), how problems can be classified at different levels of scale, and how the social side of delivering findings — framing, context, and the kind of feedback you ask for — changes whether your recommendations actually get used. Note that these videos are drawn from usability testing and heuristic evaluation contexts; the reporting and prioritization practices transfer directly to cognitive walkthrough results.
A short Nielsen Norman Group explainer on assigning severity ratings to design issues found in usability studies or heuristic evaluations. It walks through the small set of criteria evaluators typically use to rate a problem's seriousness, so that a long list of findings can be ordered by importance rather than by the order they were discovered.
Severity rating is the mechanism that turns a flat list of walkthrough failures into a prioritized set of revisions, and NN/g is the standard professional source for how those ratings are defined and applied.
This video focuses on the communication side of UX work: how to set the stage with stakeholders before you present, what context to provide, and how to ask for the kind of feedback you actually need. It treats a presentation as a structured conversation rather than a one-way report.
It speaks directly to the "Presenting Findings to Designers" subtopic, giving concrete framing tactics for sharing walkthrough results so that designers engage with the problems instead of defending the design.
An overview of user pain points organized into three categories — interaction level, journey level, and relationship or organizational level — with examples of how problems range from small friction to large systemic issues. It gives a vocabulary for describing the scale and scope of a usability problem.
The three-level framing is a practical tool for synthesizing scattered walkthrough findings into patterns and for explaining to stakeholders why some issues are isolated fixes while others point to a deeper design problem.
Together these videos carry the module from documentation to decision-making. The severity-rating video supports MO3 most directly, giving you explicit criteria for ranking the issues you identified during your walkthrough so revisions can be sequenced by impact rather than convenience. The pain-points video supplies a classification scheme for grouping the issues you documented under MO2 into patterns at the interaction and journey levels, which is the first step toward meaningful prioritization. The feedback video addresses the final link in the chain: once you have recalled the method's guiding questions (MO1) and applied them to a peer or self-developed prototype, your findings only create value if designers and stakeholders can receive them productively.
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.