A heuristic evaluation is only as useful as the report that comes out of it. Once you have inspected an interface and identified violations of Nielsen's 10 principles, you have to turn a pile of observations into a document that a design team, a product manager, or a client can actually act on. That document typically includes an executive summary, a description of scope and method (what was evaluated, by whom, under what conditions), a prioritized list of findings, and an appendix of supporting evidence.
The craft is in the findings themselves. A strong problem description names the specific screen or element, states the heuristic violated, explains the likely consequence for the user, and assigns a severity rating — all without blaming the designer or wandering into speculation. A strong recommendation is concrete enough to be implemented and is clearly separated from the finding, so stakeholders can see the problem even if they choose a different solution. Screenshots with callouts, annotated flows, and short illustrative quotes or scenarios make findings credible and quick to grasp.
The videos below come from Nielsen Norman Group. As you watch, pay attention to three things: how findings are organized and prioritized for an audience, how to represent evidence honestly rather than overstating what a small inspection can prove, and how supporting material such as quotes or visuals is edited and framed so it informs rather than misleads.
A short preview of an NN/g course covering the full heuristic evaluation workflow: planning the evaluation, conducting it, and reporting the results. Expect an overview of how the method fits into a UX process and what the reporting stage involves as the final deliverable.
It is the only video here that explicitly frames reporting as a distinct stage of heuristic evaluation, and it comes from the group that originated the method, so the vocabulary matches what the rest of this module uses.
This video addresses how to present research findings to stakeholders truthfully, likely covering common ways data gets overstated — small sample sizes, misleading percentages, cherry-picked results — and how to communicate uncertainty instead. The emphasis is on responsible framing rather than persuasive spin.
Heuristic evaluation reports are expert judgments, not user data, so honest framing and appropriate hedging are central to report quality standards; this video directly targets that skill.
Three practical tips for selecting, editing, and presenting quotes when sharing UX research, including how to trim a quote without distorting it and how to pair it with context so the audience understands what it illustrates. It treats quotes as evidence that needs curation, not raw filler.
The same discipline applies to the evidence in an HE report — choosing representative examples, annotating them, and keeping them tied to a specific finding — making this a good model for the Using Visual Evidence subtopic.
These videos sit at the end of the evaluation workflow and support the module outcomes by showing what happens after the inspection is done. The NN/g course preview places reporting inside the complete plan-conduct-report cycle that MO2 describes, reinforcing that classifying violations against Nielsen's heuristics is a step toward a communicable deliverable. The responsible-presentation and quote-editing videos support MO3: severity ratings and design recommendations only influence a team if they are stated accurately, prioritized clearly, and backed by well-chosen evidence. Together with the heuristic definitions from MO1, they help you produce findings that name the principle violated, justify the severity, and propose a fix a team can act on.
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.