Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

UX Design · Lesson 11 / 13

Usability heuristics

Jakob Nielsen's 10 usability heuristics explained one by one with real examples and violations, plus how to run a heuristic evaluation and rate what you find.

5 min read · 5 quiz questions

What are heuristics?

A heuristic is a rule of thumb. Usability heuristics are broad principles that describe what makes interfaces easy to use. The best known are the 10 usability heuristics published by Jakob Nielsen in 1994 (based on earlier work with Rolf Molich). They are still widely used because they describe how people work, not a particular technology.

You can use them in two ways: as guidelines while designing, and as a checklist to evaluate an existing interface in a heuristic evaluation.

1. Visibility of system status

The design should always keep users informed about what is going on, through appropriate feedback within a reasonable time.

  • Good: a progress bar while uploading; "Saved" after editing; a step indicator "Step 2 of 4"; the current page highlighted in navigation.
  • Violation: a button that does nothing visible for three seconds after being clicked, so people click again and submit twice.

2. Match between the system and the real world

Speak the users' language, with words, phrases and concepts familiar to them. Follow real-world conventions and present information in a natural order.

  • Good: a shopping "cart"; a trash can for deleted items; dates shown in the local format; "Send money" instead of "Initiate transfer".
  • Violation: error messages like "Exception 0x80070005" or internal terms like "SKU entity".

3. User control and freedom

Users often make mistakes. They need a clearly marked "emergency exit" to leave an unwanted action without going through an extended process.

  • Good: Undo after deleting an email; a Cancel button in every dialog; a back button that doesn't lose form data; easy unsubscribe.
  • Violation: a multi-step form where going back clears everything you typed.

4. Consistency and standards

Users shouldn't have to wonder whether different words, situations or actions mean the same thing. Follow platform and industry conventions (external consistency) and be consistent within your product (internal consistency).

  • Good: the same icon and label for "Save" everywhere; links styled the same throughout; following iOS or Android patterns in native apps.
  • Violation: "Delete", "Remove" and "Trash" used for the same action on different screens.

5. Error prevention

Good error messages are important, but the best designs prevent problems from occurring in the first place.

  • Good: disabling dates in the past in a booking calendar; confirming before permanently deleting; suggesting "Did you mean gmail.com?"; constraints on input fields.
  • Violation: a free-text date field that accepts anything and fails only on submit.

There are two kinds of errors: slips (you meant to do the right thing but did the wrong one, like a typo) and mistakes (your understanding was wrong). Prevent slips with constraints and good defaults; prevent mistakes with clear information.

6. Recognition rather than recall

Minimise memory load by making elements, actions and options visible. Users shouldn't have to remember information from one part of the interface to another.

  • Good: showing recent searches; visible menus instead of hidden commands; showing the order summary while entering payment details.
  • Violation: asking users to type a product code they saw on a previous screen.

7. Flexibility and efficiency of use

Shortcuts — hidden from novices — may speed up interaction for experts, so the design can cater to both.

  • Good: keyboard shortcuts; saved payment methods; templates; customisable dashboards; "Reorder" buttons.
  • Violation: forcing frequent users through the same lengthy wizard every time.

8. Aesthetic and minimalist design

Interfaces shouldn't contain information that is irrelevant or rarely needed. Every extra unit of information competes with the relevant units and reduces their visibility.

  • Good: a checkout page focused only on completing the purchase; progressive disclosure of advanced options.
  • Violation: a homepage with ten banners, three pop-ups and a carousel all competing for attention.

Minimalist doesn't mean "flat" or "empty". It means every element earns its place by supporting the user's goal.

9. Help users recognise, diagnose and recover from errors

Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.

BadGood
Error 422Your card number is too short. Check the 16 digits on the front of your card.
Invalid inputEnter a date like 25/12/2026.
Something went wrongWe couldn't connect. Check your internet connection and try again — your draft is saved.

10. Help and documentation

Ideally the system doesn't need explanation. But it may be necessary to provide documentation that helps users complete their tasks. It should be easy to search, focused on the user's task, and list concrete steps.

  • Good: contextual tooltips; a searchable help centre; short onboarding tips at the moment they're needed.
  • Violation: a 60-page PDF manual as the only help.

Running a heuristic evaluation

  1. 1Define the scope: which flows or screens, and for which users.
  2. 2Recruit 3–5 evaluators. One evaluator finds only a fraction of the problems; several working independently find many more.
  3. 3Each evaluator reviews the interface alone, at least twice: once to get a feel for the flow, then again to inspect details.
  4. 4For every issue, record the location, the heuristic violated, a description and a screenshot.
  5. 5Rate severity (e.g. 0 = not a problem, 1 = cosmetic, 2 = minor, 3 = major, 4 = catastrophe).
  6. 6Merge findings from all evaluators, remove duplicates and agree on severity.
  7. 7Prioritise and recommend fixes.

Common mistake: Treating a heuristic evaluation as a replacement for testing with real users. Experts find many issues quickly, but they also miss problems real users have and flag some that don't matter in practice. Use both.

Key takeaways

  • Nielsen's 10 heuristics are broad principles for usable interfaces, still relevant decades later.
  • Key themes: feedback, familiar language, control and undo, consistency, error prevention, low memory load.
  • Good error messages are plain, precise and suggest a solution.
  • Heuristic evaluations use 3–5 evaluators working independently, then merge and rate findings.
  • Heuristic evaluation complements — never replaces — usability testing.

Exercise

Evaluate an app with the 10 heuristics

  1. Pick one flow in an app you use, e.g. booking a ride or paying a bill.
  2. Go through it twice, noting every issue you find.
  3. Label each issue with the heuristic it violates.
  4. Rate each from 1 (cosmetic) to 4 (catastrophe).
  5. Write a fix for your top three issues.

Test yourself

Usability heuristics quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.A file upload shows no progress indicator. Which heuristic is violated?
  2. 2.Disabling past dates in a booking calendar is an example of…
  3. 3.Showing recent searches supports…
  4. 4.Which is the best error message?
  5. 5.How many evaluators are typically recommended for a heuristic evaluation?