Usability testing almost always produces more problems than you have time or budget to fix. The real skill is deciding what to fix first. Prioritizing usability improvements means taking a raw list of findings and turning it into an ordered, defensible plan: which issues block users outright, which merely annoy them, which are cheap to repair, and which require architectural change.
This topic introduces four related tools. Severity rating frameworks give you a consistent scale (typically combining how badly the problem hurts the user, how often it occurs, and how persistent it is). Impact versus effort mapping plots findings on a simple grid so quick wins and expensive long shots become visible. Aligning priorities with design goals keeps the ranking honest, so that you fix what matters for the product's purpose and target users rather than what is easiest to argue about. Finally, communicating priorities to stakeholders is what makes the whole exercise useful, since prioritization only pays off if developers, product owners, and clients accept the ordering.
As you watch the videos, pay attention to the specific criteria each method uses, and notice how a judgment call ("this feels bad") gets converted into something comparable and reportable. Ask yourself how you would apply each framework to the findings from your own test sessions, and what evidence you would cite when someone pushes back on your ranking.
A short Nielsen Norman Group explainer on assigning severity ratings to problems found in usability studies or heuristic evaluations. It walks through the small set of criteria normally used to judge severity, so that findings can be reported on a consistent scale rather than described subjectively. Expect practical guidance on how to phrase and justify a rating when writing up results.
This is the most direct coverage of the severity rating framework subtopic, from the research group that popularized the approach, and it is short enough to use as a reference while scoring your own findings.
A broader survey of prioritization methods used in UX work, built on the premise that you cannot and should not build everything. It is likely to compare several approaches for ranking work items and explain when each is appropriate. Watch for how different methods weigh user value against cost or effort.
At six minutes it gives the widest view of the topic, covering impact versus effort style trade-offs and the general logic of prioritizing against product and design goals.
An introduction to applying the Pareto principle, the idea that a small share of items produces most of the effect, to design decisions. The description points to applications across features, usability problems, customers, and personas. Expect guidance on identifying the vital few issues worth concentrated attention.
It supplies a simple mental model for focusing limited resources, which complements formal severity scoring and supports the argument you will need to make to stakeholders about why some issues are deferred.
Together these videos move you from raw findings to an ordered plan of action. The severity video supports MO1 and MO2 by giving you consistent criteria for rating the pain points and failure patterns you identified in your test data. The prioritization methods and Pareto videos directly serve MO2, offering impact-versus-effort reasoning and a focusing heuristic for deciding which issues deserve scarce time. Because each method makes its criteria explicit, all three also feed MO3: the rating or ranking you assign becomes the documented rationale you cite when you justify each iterative design change to instructors, teammates, or stakeholders.
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.