Heuristic evaluation (HE) is a usability inspection method: instead of recruiting end users, a small group of evaluators inspects an interface on their own and judges it against a short list of recognized usability principles. The method was popularized by Jakob Nielsen and Rolf Molich in the early 1990s, and it remains one of the fastest, cheapest ways to surface usability problems in a design before (or alongside) user testing. In this course it serves as your bridge from abstract design principles to concrete, defensible critique of real interfaces.
The subtopics here frame four questions. What is HE, procedurally — who evaluates, how many evaluators, how findings are merged? Where did it come from, and how does it relate to other inspection methods such as cognitive walkthroughs? When should you reach for it — early in design, between usability tests, or as a quick audit of an existing product? And what are its limits — evaluators are not users, findings can be subjective, and HE tends to catch surface-level problems more reliably than deep task or workflow failures.
As you watch, pay attention to process details you will need to reproduce in your own evaluation: evaluating independently before discussing, documenting each issue with the heuristic it violates and where it occurs, consolidating duplicate findings across evaluators, and assigning severity. Also note where each video says HE should not stand alone — that caveat is part of understanding the method, not a footnote to it.
A concise walkthrough from Nielsen Norman Group of the heuristic evaluation procedure, including evaluating independently, working through an example interface, and consolidating issues found by multiple evaluators into a single list. The chapter markers indicate it closes with a summary of the overall workflow.
It comes from the organization that originated the method, and in under five minutes it maps directly onto the "what is heuristic evaluation" and "how to run one" subtopics with a worked example.
A longer practitioner-oriented tutorial on assessing a product's UX through heuristic evaluation, with a free template offered for structuring findings. The description frames heuristics as a way to catch a large share of usability problems, so expect discussion of why teams use the method and how to apply it to a real product.
It complements the NN/g overview with a studio practitioner's perspective on when to use HE and what deliverable it produces, which supports the "when to use" and "advantages" subtopics.
An NN/g explainer on cognitive walkthroughs, a task-based usability inspection technique focused on how learnable a system is for a first-time user. It should clarify how the walkthrough procedure is structured around specific tasks rather than general principles.
Seeing a sibling inspection method makes the boundaries of heuristic evaluation clearer, which is exactly what the "origins and context" and "limitations" subtopics ask you to understand.
Together these videos give you the procedural grounding the module outcomes require. The NN/g walkthrough and the Adam Fard tutorial show evaluators inspecting an interface against principles, documenting violations, and consolidating them, which is the core skill behind MO2, and both touch on recording and prioritizing issues in a way that feeds the severity rating and recommendation work in MO3. The cognitive walkthrough video positions HE among alternative inspection methods so that when you apply Nielsen's 10 heuristics in MO1 you understand both what they are good for and where another method would serve you better.
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.
Jakob Nielsen's ten usability heuristics are the most widely used set of general principles for interface design. They are deliberately broad "rules of thumb" rather than strict guidelines, which is what makes them useful across websites, mobile apps, desktop software, and even physical devices. In this topic you will work through each heuristic in turn: visibility of system status, match between the system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency of use, aesthetic and minimalist design, helping users recognize and recover from errors, and help and documentation.
These principles matter in this course because they are the vocabulary of heuristic evaluation. When you inspect an interface, you are not simply saying "this feels bad" — you are naming the specific principle that is violated, explaining why it causes a problem for users, and proposing a concrete fix. Being able to recall all ten heuristics and recognize them in the wild is the prerequisite for everything that follows in this module, including severity rating and recommendation writing.
As you watch, keep two questions in mind for each heuristic: what user problem does this principle prevent, and what does a violation actually look like in a real interface? Try to collect at least one positive example and one violation for each of the ten. Also notice that heuristics sometimes pull against each other — a minimalist design may hide status information, and an innovative pattern may break consistency — so part of your job as an evaluator is judgment, not just pattern matching.
A beginner-oriented walkthrough of all ten of Nielsen's usability heuristics, taking each principle in turn and illustrating it with real UX examples drawn from interfaces you are likely to recognize. At roughly thirteen minutes it is long enough to give each heuristic its own explanation and example rather than just listing the names.
This is the most complete single-video coverage of the topic, mapping directly onto all ten subtopics from visibility of system status through help and documentation, and the example-driven format helps you move from memorizing definitions to spotting violations.
A short, memorable video in which the presenter uses an ordinary kitchen toaster to demonstrate eight of the usability heuristics. Because the subject is a physical product rather than a screen, it forces you to think about the principles as general design ideas — feedback, mappings to the real world, error prevention, and recognition over recall — rather than as web-specific rules.
Produced by Envato Tuts+, it is a clear and concise reinforcement that shows the heuristics apply beyond software, which is exactly the kind of transfer you need when evaluating unfamiliar interfaces; note that it covers eight rather than all ten, so pair it with the full walkthrough.
A focused five-minute piece on the tension between following established interface conventions and introducing novel patterns. It discusses why any innovation forces users to learn something new and when the cost of departing from convention is justified.
It comes from NNgroup, the organization founded by Nielsen himself, and it deepens Heuristic 4 (consistency and standards) by showing that applying a heuristic requires judgment — a distinction that will matter when you justify and rate violations in your own evaluation.
Together these videos build the foundation the module outcomes require. The ten-heuristic walkthrough supports MO1 by naming, defining, and exemplifying each principle, while the toaster video reinforces the same ideas in a different context so that the definitions stick and transfer. Both videos' use of concrete examples and violations gives you practice at the core skill behind MO2 — looking at an interface, identifying a problem, and labeling it with the correct heuristic. The NNgroup video on consistency versus innovation supports MO3 by modeling the kind of trade-off reasoning you need when deciding how serious a violation is and what specific change you would recommend instead.
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.
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.
Finding usability problems is only half the work of a heuristic evaluation. Once you have a list of heuristic violations, someone has to decide which ones get fixed first, because development teams rarely have time to address everything. Severity ratings are the tool evaluators use to communicate how much each problem matters, turning a long, flat list of issues into a prioritized set of recommendations.
Nielsen's severity scale runs from 0 (not a usability problem at all) to 4 (usability catastrophe that must be fixed before release), with cosmetic, minor, and major problems in between. The rating you assign is a judgment call, but it is not arbitrary: it is based on how frequently users will encounter the problem, how much trouble it causes them when they do, and whether users can learn to work around it or are blocked by it every time. Because judgment varies between people, evaluations usually combine ratings from several evaluators and record each issue with its heuristic, its severity, and a suggested fix.
As you watch these videos, pay attention to the criteria the speakers use to justify a rating rather than just the numbers themselves. Notice how severity is described in terms of user impact, and think about how you would document a rating so that a teammate reading your report could understand why you chose it. This habit of recording and defending ratings is exactly what you will be asked to do in your own evaluation assignments.
A short, focused video from Nielsen Norman Group on assigning severity ratings to design issues found in usability studies or heuristic evaluations. It discusses the small set of criteria evaluators use to judge how serious a problem is, such as how often users hit it and how much it impedes them, and how those criteria translate into prioritized findings in a report.
This is the most directly on-topic video for the subtopics: it comes from the organization that defined the severity scale and it addresses purpose, criteria, and prioritization in just three minutes.
An overview of how to run a heuristic evaluation systematically: reviewing an interface against a set of heuristics, identifying potential usability and experience problems, and documenting what you find. Severity rating fits in as the step that follows identification, so this video supplies the surrounding process in which ratings are assigned and recorded.
It places severity rating in context by showing the full evaluation workflow, which helps you understand when and why ratings get assigned rather than treating the scale in isolation.
An explanation of the System Usability Scale, a standard ten-question survey given at the end of a usability test that produces a single score for perceived usability. It covers how the questionnaire works and how the resulting score is interpreted as a measure of overall usability.
It offers a useful contrast: SUS measures perceived usability of a whole system from users, while severity ratings are expert judgments about individual problems, and seeing both clarifies what severity ratings are and are not.
Together these videos move you from identifying problems to prioritizing them. The heuristic evaluation walkthrough reinforces MO1 and MO2 by showing how an interface is reviewed against heuristics and how violations are captured and classified. The severity video directly supports MO3, giving you the criteria and vocabulary to rate each violation and to justify that rating when you recommend specific design improvements. The SUS video rounds out your understanding of usability measurement, helping you distinguish an overall perceived-usability score from the issue-level severity judgments you will produce in this module.
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.
Heuristic evaluation is deliberately done by several evaluators working independently, because any single person catches only a fraction of the usability problems in an interface. That design choice creates a follow-up task: once everyone has finished inspecting on their own, the separate lists of findings have to be combined into one clean, agreed-upon set of problems that a team can actually act on. That combining step is called aggregation.
Aggregation usually happens in a structured meeting. Evaluators walk through their findings one at a time, merge duplicates that were described in different words, decide whether two similar observations are really one underlying problem or two distinct ones, settle which heuristic each violation maps to, and negotiate a single severity rating when individual ratings disagree. The output is a deduplicated, prioritized problem list with enough detail (location, heuristic violated, severity, suggested fix) for designers to use.
As you watch the videos below, pay attention to two things. First, how the evaluation process is structured from the start, since consistent note-taking and clear problem descriptions during individual evaluation are what make deduplication possible later. Second, how small numbers of evaluators or test users can still produce trustworthy, decision-ready conclusions — the same logic that justifies why we aggregate across a handful of evaluators rather than relying on one.
A short walkthrough from Nielsen Norman Group on how to run a heuristic evaluation systematically: reviewing the interface against a set of heuristics, recording the problems found, and working through the product in an organized way. Expect it to cover the roles of multiple independent evaluators and how their individual findings feed into a combined set of results.
It comes from the group that originated the method, and it frames the full process end to end — which is exactly where aggregation fits, immediately after individual evaluations are complete.
This video addresses the common objection that a small number of participants cannot represent all users, and explains how limited-scale usability work still supports sound business decisions. It discusses what small-sample findings can and cannot tell you, and how to reason about risk when acting on them.
It directly supports the "why aggregation is necessary" subtopic: the value of combining a few evaluators' or users' findings rests on understanding why small samples surface most of the important problems, and it gives you language for defending a merged problem list to stakeholders.
Together these videos reinforce the practical side of the module. The heuristic evaluation walkthrough supports MO2 by showing how violations are identified and recorded against Nielsen's principles (MO1), and it sets up the aggregation step where those individually classified violations are merged into one list. The small-sample video supports MO3 and the negotiation of severity by explaining why findings from a handful of evaluators are credible enough to prioritize and act on, which is the reasoning behind assigning agreed severity ratings and recommending specific fixes.
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.
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.
In this topic you move from learning heuristic evaluation (HE) to performing it on real work produced by your classmates. The module assignment asks you to independently evaluate three peer prototypes, applying the full HE process to each: inspect the interface, identify usability problems, classify each problem under one of Nielsen's 10 heuristics, assign a severity rating, and recommend a concrete fix. The key word is independently — in a proper heuristic evaluation, each evaluator works alone first, and findings are only pooled afterward. Comparing notes with a peer before you finish contaminates your results and robs the designer of a genuinely independent perspective.
Two other expectations shape this assignment. The first is professional conduct: you are critiquing an interface, not a person. Write findings that are specific, evidence-based, and actionable ("the Save button gives no confirmation, violating Visibility of System Status") rather than vague or personal ("this screen is bad"). The second is calibration. Because you are reviewing three different prototypes, your severity ratings should mean the same thing across all three. A severity 3 on prototype A should represent roughly the same user impact as a severity 3 on prototype C, which usually means revisiting your earlier ratings once you have seen all three.
The two videos below come from Nielsen Norman Group, the organization that originated the method. As you watch the first, pay attention to the step-by-step workflow — especially the practice of evaluating alone and merging findings later, and how problems are tied to specific heuristics. The second video is about facilitating usability tests rather than HE, but watch it for tone: how an experienced professional frames a session, sets expectations, and makes clear that the interface is under scrutiny, not the person. That framing is exactly the attitude to bring to peer evaluation.
A short, practical walkthrough from Nielsen Norman Group on how to systematically inspect a product for usability and experience problems. It is likely to cover who performs the evaluation, how many evaluators are typically used, the steps of reviewing an interface against a set of heuristics, and how individual findings are recorded and later combined. Expect guidance on documenting each issue clearly enough that someone else can act on it.
This is the core procedural video for the assignment: it comes from the group that developed the method and should directly address the independent-then-aggregate workflow you are required to follow across three peer prototypes.
Facilitation experts demonstrate how to introduce and prepare a participant at the start of a usability test session, including the use of a facilitator's script. The demonstration shows how to set expectations, explain that the product rather than the person is being evaluated, and establish a neutral, respectful tone.
Although it depicts usability testing rather than heuristic evaluation, it models the professional, non-judgmental communication standard expected when you deliver critique to a peer, and the scripted consistency it shows parallels the calibration you need across three prototypes.
The heuristic evaluation walkthrough gives you the procedure behind MO2: inspecting an interface systematically and attaching each observed problem to a specific one of Nielsen's 10 heuristics (MO1), which is also the backbone of the three-prototype assignment. Its emphasis on documenting findings so they can be understood and acted on by others supports MO3, where you must justify a severity rating and propose a targeted design improvement rather than a general complaint. The facilitation demonstration reinforces the professional conduct and consistency expectations of this topic, modeling the neutral, prepared tone that makes severity ratings and recommendations credible and comparable across all three peer prototypes you review.
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.