Jakob Nielsen’s ten usability heuristics are broad rules of thumb for interface design. He developed them with Rolf Molich in 1990 and refined them in 1994, and the Nielsen Norman Group notes that the heuristics themselves have stayed unchanged since then, even though the explanations and examples have been updated. They are called “heuristics” because they are general principles, not exact rules.
They are useful in two ways: as a checklist while you design, and as a structured method, called heuristic evaluation, for reviewing an existing product. Below, each heuristic is explained in simple words with an everyday example and a quick check you can apply to your own screens.
1. Visibility of system status
People should never have to guess what the product is doing. Every action deserves a quick, visible response, and anything slow should show that it is still working.
Example: after you pay for a train ticket, the app shows “Payment received – generating your ticket” with a progress indicator, instead of a blank screen that makes you wonder whether to press “Pay” again.
Quick check: Does every action produce visible feedback within a moment? Do long operations show progress?
2. Match between the system and the real world
Talk the way your users talk. Labels, icons and the order of steps should reflect how people already think about the task, not how the database or the company org chart is structured.
Example: a banking app says “Money sent to Ravi Kumar” rather than “IMPS txn status: SUCCESS (code 00)”. A grocery app lists vegetables under names local customers use, and shows weights in grams and kilograms.
Quick check: Would a first-time user understand every label without a glossary?
3. User control and freedom
Everyone taps the wrong thing sometimes. Make it easy and obvious to step back, cancel or reverse an action, so people feel safe exploring.
Example: an email or chat app shows “Message deleted – Undo” for a few seconds. A multi-step form lets you go back without losing what you typed.
Quick check: Can users undo, cancel, go back and close dialogs easily?
4. Consistency and standards
Once people learn how something works, it should work the same way everywhere. Reuse familiar patterns from the platform and from other products, and keep your own terms and components uniform.
Example: if “Save” is a solid blue button on one screen, it should not be a grey text link on another. A cart icon should mean the same thing everywhere.
Quick check: Are the same components, terms and placements used for the same purpose throughout? A design system helps enormously here.
5. Error prevention
Helpful error messages are good; designs that make the mistake impossible or unlikely are better. Look for the places where slips happen and remove the opportunity.
Example: a travel booking form disables return dates that fall before the departure date. A transfer screen asks for confirmation and shows the recipient’s name before sending a large amount.
Quick check: Are risky actions confirmed? Do inputs use constraints (date pickers, dropdowns, input masks) where free text invites errors?
6. Recognition rather than recall
Human short-term memory is limited. Put the options and information people need right in front of them, instead of expecting them to carry details in their heads from one screen to the next.
Example: a food delivery app shows your recent orders with a “Reorder” button, instead of making you remember the restaurant and dishes. A checkout page shows the items you are paying for next to the payment form.
Quick check: Is any information hidden that users need in order to make a decision?
7. Flexibility and efficiency of use
Beginners need a clear, guided path; regular users want speed. Offer accelerators that experienced people can discover without getting in the way of newcomers.
Example: keyboard shortcuts in a web app (such as Ctrl + K for search), saved addresses, “Book again” for frequent trips, or customisable filters.
Quick check: Can frequent users complete common tasks faster than first-time users?
8. Aesthetic and minimalist design
Each element on a screen takes some of the user’s attention. Anything that does not support the current task makes the important things harder to see, so cut or move it.
Example: a product page puts price, delivery date and “Add to cart” first, with detailed specifications further down, rather than five promotional banners above the product.
Quick check: If you removed this element, would anyone miss it? Is the main action obvious? See visual hierarchy.
Tip: Minimalist does not mean “flat and empty”. It means focused on what users need. A dense table can be minimalist if every column is useful.
9. Help users recognise, diagnose and recover from errors
When something does go wrong, explain it in everyday words, point to exactly where the problem is and tell people what to do next.
Example: instead of “Invalid input”, a form says “Enter a 10-digit mobile number, for example 98765 43210”, right below the field, with the field highlighted and an error icon.
Quick check: Does each error message say what went wrong and how to fix it, without blaming the user or using codes?
10. Help and documentation
Ideally the interface explains itself. Where it cannot, short and easy-to-find help, placed close to where people get stuck, fills the gap.
Example: a tax-filing site shows a small “What is this?” link next to a confusing field, explaining it in two sentences, and offers searchable help articles focused on specific tasks.
Quick check: Is help available in context, searchable and focused on tasks rather than features?
Summary table of the 10 usability heuristics
| # | Heuristic | In one line |
|---|---|---|
| 1 | Visibility of system status | Always show what is happening |
| 2 | Match between system and real world | Speak the user’s language |
| 3 | User control and freedom | Provide undo and exits |
| 4 | Consistency and standards | Same thing, same look, same word |
| 5 | Error prevention | Stop mistakes before they happen |
| 6 | Recognition rather than recall | Show, don’t make users remember |
| 7 | Flexibility and efficiency of use | Shortcuts for experienced users |
| 8 | Aesthetic and minimalist design | Remove what does not help |
| 9 | Help users recover from errors | Clear, helpful error messages |
| 10 | Help and documentation | Easy-to-find, task-focused help |
How to run a heuristic evaluation
A heuristic evaluation is an expert review in which evaluators inspect an interface against the usability heuristics. It is quick and cheap, and it works well before a usability test to catch obvious problems.
- Define the scope. Choose specific flows, for example “sign-up” and “checkout”, rather than “the whole app”.
- Pick evaluators. Use several people, ideally three to five, who know the heuristics. Different evaluators find different problems.
- Evaluate independently. Each person goes through the flow at least twice: once to get a feel for it, then again to inspect each screen against the heuristics.
- Record each issue with a screenshot, the screen, the heuristic it violates and a short description.
- Merge findings. Combine everyone’s list and remove duplicates.
- Rate severity. Agree on a severity for each issue (see below).
- Recommend fixes and prioritise them with the product team.
| Severity | Meaning |
|---|---|
| 0 | Not a usability problem |
| 1 | Cosmetic; fix if there is extra time |
| 2 | Minor; low priority |
| 3 | Major; important to fix, high priority |
| 4 | Usability catastrophe; must fix before release |
Watch out: A heuristic evaluation does not replace testing with real users. Experts can miss problems that real users face, and they can flag issues that users do not actually mind. Use it alongside usability testing.
Simple template for your findings
| Screen | Issue | Heuristic | Severity | Recommendation |
|---|---|---|---|---|
| Checkout – payment | No feedback after tapping “Pay”; users may tap twice | 1. Visibility of system status | 4 | Show a loading state and disable the button after the first tap |
| Sign-up | Password rules shown only after an error | 5. Error prevention | 3 | Show rules below the field before typing |
| Profile | Two different icons used for “Edit” | 4. Consistency and standards | 1 | Use the same icon component everywhere |
The heuristics are also a great preparation tool for job interviews; many interviewers ask candidates to critique an app. See UI/UX interview questions. And because several heuristics overlap with accessibility, read web accessibility basics too.
Frequently asked questions
Who created the 10 usability heuristics?
Jakob Nielsen, together with Rolf Molich, developed the original heuristics in 1990. Nielsen refined them into the current list in 1994. The Nielsen Norman Group publishes the official descriptions.
How many evaluators do I need for a heuristic evaluation?
Several. A single evaluator misses many problems, so the commonly recommended number is around three to five independent evaluators whose findings are then combined.
Is heuristic evaluation the same as usability testing?
No. Heuristic evaluation is an expert review against principles, without users. Usability testing observes real users trying tasks. They complement each other.
Are Nielsen's heuristics still relevant?
Yes. They are broad principles about how people interact with systems, so they apply to websites, mobile apps, voice interfaces and new technologies, even though the examples change over time.
