Heuristic evaluation (HE) is a discount usability inspection method: a small group of evaluators independently inspects an interface against a set of recognized usability principles, then their findings are pooled into a single list of problems. Knowing the ten heuristics is only half the skill — the other half is running the evaluation properly, which is what this topic covers.
The process has distinct phases. Preparation means defining the scope of the interface, choosing representative tasks or screens, and briefing evaluators on the heuristic set and on any domain knowledge they need. The individual evaluation phase means each evaluator passes through the interface alone (usually at least twice — once to get a feel for the flow, once to inspect elements closely) so that no one's judgment is anchored by someone else's. Documentation means recording each problem separately, naming the heuristic it violates, pointing to the exact location in the interface, and rating severity. Finally, the findings from all evaluators are consolidated; Nielsen's well-known guidance is that a single evaluator finds only a fraction of the problems, and that roughly three to five evaluators give the best return on effort.
As you watch, pay attention to procedure rather than to the heuristics themselves: when do evaluators work alone versus together, how is a problem written up so someone else can act on it, and what makes a finding specific enough to be useful? Notice also how severity ratings and recommendations are attached to problems, since you will be asked to produce both in this module's assignment.
A short, practical walkthrough from Nielsen Norman Group on how to systematically review a product for usability and experience problems. Based on its title and description, it should cover the basic mechanics of an evaluation pass — what to inspect, how to work through an interface methodically, and how heuristics are applied to what you find.
NN/g originated the method, so this is an authoritative and compact overview that maps directly onto the "conducting the individual evaluation" subtopic.
A course preview that frames heuristic evaluation across its full lifecycle: planning, conducting, and reporting results. Expect it to outline why HE is fast and flexible, where it fits in a UX workflow, and what each phase of the process involves at a high level.
It explicitly covers planning and reporting — the preparation and documentation subtopics that shorter how-to videos often skip — and it comes from the same authoritative source.
A worked example from a university digital learning channel that applies heuristics to a concrete interface scenario, such as an equipment rental flow. The description suggests it walks through specific findings and proposed changes, like merging steps to simplify a task.
Seeing heuristics applied to a real screen and turned into stated problems and recommendations models the documentation step better than an abstract description can.
Together these videos take you from the principles themselves to their disciplined application. The two NN/g videos reinforce what the heuristics are and how to apply them during inspection (MO1, MO2) while covering planning, individual evaluation, and reporting, including severity and findings write-up (MO3). The QUT example grounds the method in a concrete interface, showing how an observed issue is named, tied to a heuristic, and paired with a specific design improvement — exactly the output expected of you in this module's evaluation exercise.
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.