Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 36 ยท UX Fundamentals

Usability Heuristics

Learn the ten classic usability heuristics, with plain examples of each, and how to run a heuristic evaluation to find interface problems without recruiting any users.

A heuristic is a rule of thumb. In UX, the best-known set is the ten usability heuristics written by Jakob Nielsen and Rolf Molich, later refined by Nielsen. They are broad principles, not strict rules, and they describe what usually goes wrong in interfaces. You can use them while designing and as a checklist for reviewing an existing product.

The ten heuristics

  1. Visibility of system status. Tell people what is going on. A progress bar, a "Saved" message, a highlighted current page.
  2. Match between the system and the real world. Use words and ideas users know, not internal jargon. "Basket" and "Pay now" beat "Order object" and "Submit transaction".
  3. User control and freedom. People make mistakes. Offer undo, cancel and a clear way out.
  4. Consistency and standards. Similar things look and behave alike, and follow platform conventions. A magnifier icon means search everywhere.
  5. Error prevention. Better than a good error message is a design that stops the error: disable impossible choices, confirm destructive actions, accept both 12/03 and 12 Mar.
  6. Recognition rather than recall. Show options instead of making people remember them. Menus beat memorized commands.
  7. Flexibility and efficiency of use. Offer shortcuts for experts without hiding the basics from beginners.
  8. Aesthetic and minimalist design. Every extra element competes with the important ones. Remove what does not help.
  9. Help users recognize, diagnose and recover from errors. Plain-language messages that say what happened and how to fix it.
  10. Help and documentation. Best if not needed, but when needed it should be searchable, short and task-focused.

Keep users informed

Status Show progress and saves
Real words Speak the user's language
Control Undo and cancel

Heuristics 1 to 3.

1 / 2

Heuristics in action

Consider a file-upload screen. It scores badly if clicking Upload shows nothing for ten seconds (status), says "Error 0x80" on failure (plain language and recovery), and has no way to cancel (control). The same screen improves when it shows a progress bar with a Cancel button, and says "That file is 40 MB; the limit is 25 MB. Choose a smaller file or compress it."

Heuristic evaluation

A heuristic evaluation is a review where a few evaluators go through an interface and note every place it breaks a heuristic. It is fast and cheap, and finds many obvious problems before you spend time on user testing. Typical steps:

  1. Pick the tasks to review (for example "change my email address").
  2. Each evaluator works alone, going through the interface at least twice.
  3. For each problem, record where it is, which heuristic it violates, and how severe it is.
  4. Combine the lists and rank by severity.

A common severity scale runs from 0 (not a problem) to 4 (catastrophe, must fix). Several evaluators matter: one person finds only a fraction of the problems, and different people catch different ones.

Heuristic evaluation does not replace testing. Evaluators are not real users and may miss problems that only appear with real tasks and real confusion. Use both; see The UX Design Process.

A stand-in: a findings log

This stand-in is a tiny log that stores findings and ranks them by severity. It teaches the structure of a good finding (place, heuristic, severity), not a real evaluation tool.

JS Heuristic findings log (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The grouping at the end hints at patterns: if many findings share a heuristic, there is a systemic gap, not a one-off slip.

Using heuristics well

  • Treat them as questions. "Does the user know the system status here?" is more useful than "Is this a violation?"
  • Respect context. A game may break consistency for fun; a medical device must not.
  • Keep them in tension. Minimalism and help both matter; error prevention may add steps. Judgment is the skill.
  • Combine with evidence. A heuristic points to likely problems; observing users confirms them.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A page shows no sign that a payment is processing. Which heuristic is mainly violated?

    Users need feedback about what the system is doing.
  2. 2. Which is an example of error prevention rather than error recovery?

    Prevention stops the error from happening in the first place.
  3. 3. What is a heuristic evaluation?

    It is an expert-style review that finds likely problems quickly.
  4. 4. Why use several evaluators?

    A single evaluator misses many issues.

Summary

  • The ten heuristics are broad rules of thumb for usable interfaces.
  • They cover status, real-world language, control, consistency, prevention, recognition, flexibility, minimalism, error recovery and help.
  • A heuristic evaluation finds likely problems cheaply; it does not replace testing with users.
  • Record each finding with place, heuristic and severity.

Next: Mental Models and Conceptual Models