UX, behavior & design · Evaluation principles
Nielsen’s Usability Heuristics
Inspect an interface systematically for common usability risks before or alongside user testing.
Start here · 5-minute visual lesson
Inspect an interface against ten broad usability principles, record evidence and consequences, then prioritize findings by severity.
Think of it like this: A pre-flight checklist for interaction design: expert inspection catches known risk patterns before or alongside real-user testing.
- 1Inspect independently
- 2Name the violated principle
- 3Describe the consequence
- 4Calibrate severity
Feedback becomes “I do not like this screen,” and design critique turns into taste.
A finding names the state, violated heuristic, user consequence, frequency, and evidence needed.
Learn by deciding
The button that appeared to do nothing
A patient submits insurance details and sees no response. Which lens fits?
Visibility of system status: the product must show that work is happening and what comes next.
One evaluator notices it. Is that enough to redesign?
Record the finding, then compare independent reviews and validate high-consequence issues with users.
How do you prioritize it?
Combine frequency, impact, and persistence—then add domain, accessibility, and safety context.
01 · Understand
In plain English
Ten broad interaction-design principles help trained reviewers identify visibility, control, consistency, error, recognition, flexibility, clarity, recovery, and help problems.
Origin and context
Jakob Nielsen published the current set in 1994 based on earlier work with Rolf Molich. NN/g stresses that they are broad heuristics—not specific guidelines.
The problem it solves
Unstructured critique produces taste debates and misses repeatable interaction risks. A heuristic evaluation supplies shared lenses and severity-based findings.
The concepts, explained
Learn the vocabulary first. Each concept changes a decision you will make when using the framework.
Visibility of system status
Keep people informed about what is happening through timely, understandable feedback.
Match with the real world
Use language, concepts, and sequences that feel natural to the people using the product.
User control and freedom
Provide clear exits, undo, and recovery when people choose the wrong path or change their minds.
Consistency and standards
Similar things should look and behave similarly, while familiar platform conventions should be respected.
Error prevention
Remove error-prone conditions or ask for confirmation before a consequential action occurs.
Recognition rather than recall
Make choices, context, and instructions visible so people do not have to remember information between screens.
Flexibility and efficiency
Support both newcomers and experienced users with accelerators, sensible defaults, and adaptable workflows.
Aesthetic and minimalist design
Remove irrelevant information so important content and actions receive the attention they need.
Error recognition and recovery
Explain what went wrong in plain language and show a constructive way to fix it.
Help and documentation
When guidance is needed, make it easy to search, focused on the task, and concrete enough to follow.
02 · Deep dive
Go beyond the definition
Follow the reasoning inside Nielsen’s Usability Heuristics, then challenge it before you use it.
1 of 4mental model
The mental model
What changes in the way you see the problem
Visibility of system status
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Match with the real world
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
User control and freedom
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Consistency and standards
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Error prevention
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Recognition rather than recall
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Flexibility and efficiency
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Aesthetic and minimalist design
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Error recognition and recovery
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Help and documentation
Use this concept to examine the problem from a distinct Nielsen’s Usability Heuristics perspective.
Reasoning trace
Watch each step earn the next one
Three reviewers inspect a hospital appointment flow. They log 27 observations and merge them to 14 issues. A silent insurance-eligibility check violates system-status visibility and can cause duplicate submissions; it receives high severity. An inconsistent date label is lower severity. The team adds progress feedback and tests it with six representative users.
- 01Frame
Choose representative tasks, users, platforms, and states.
Decision question: Which finding is merely preference? - 02Interrogate
Brief three to five evaluators on scope and severity.
Decision question: What could a reviewer never learn without users? - 03Interrogate
Inspect independently to avoid group anchoring.
Decision question: Which finding is merely preference? - 04Interrogate
Record the violated heuristic, evidence, context, and consequence.
Decision question: What could a reviewer never learn without users? - 05Interrogate
Include empty, loading, error, permission, and recovery states.
Decision question: Which finding is merely preference? - 06Interrogate
Merge duplicates and calibrate severity by frequency, impact, and persistence.
Decision question: What could a reviewer never learn without users? - 07Interrogate
Prioritize fixes with product evidence and constraints.
Decision question: Which finding is merely preference? - 08Decide
Validate important issues with users and re-inspect.
Decision question: What could a reviewer never learn without users?
Failure-mode lab
Which mistake is most likely on your team?
Choose one to turn it into a control for your next workshop.
Context adaptation
The canonical version is only a starting point
Startups can run a 60-minute team pass; enterprises can add domain, content, accessibility, and platform experts. For internal tools, include expert-user efficiency and recovery from bulk actions.
Signals it fits
- A design or product can be inspected
- Testing time is limited but not eliminated
- Teams need a shared critique vocabulary
Signals to switch tools
- Reviewers lack domain and accessibility context
- Findings will be treated as proof of user behavior
- The problem is purely visual preference
Now use the framework. The workbench below turns your own context into a first decision draft.
Work my problem03 · Apply
How to use Nielsen’s Usability Heuristics
- 01
Choose representative tasks, users, platforms, and states.
- 02
Brief three to five evaluators on scope and severity.
- 03
Inspect independently to avoid group anchoring.
- 04
Record the violated heuristic, evidence, context, and consequence.
- 05
Include empty, loading, error, permission, and recovery states.
- 06
Merge duplicates and calibrate severity by frequency, impact, and persistence.
- 07
Prioritize fixes with product evidence and constraints.
- 08
Validate important issues with users and re-inspect.
04 · See it work
A worked example
Three reviewers inspect a hospital appointment flow. They log 27 observations and merge them to 14 issues. A silent insurance-eligibility check violates system-status visibility and can cause duplicate submissions; it receives high severity. An inconsistent date label is lower severity. The team adds progress feedback and tests it with six representative users.
Business case study
Illustrative fictional scenario
A fictional healthcare product illustrates independent review and severity calibration. No real patient data or company practice is claimed.
Across company types
Startups can run a 60-minute team pass; enterprises can add domain, content, accessibility, and platform experts. For internal tools, include expert-user efficiency and recovery from bulk actions.
05 · Work your problem
Turn the framework into a result
Explore the mechanics
Copy the working template
Task / state: Evidence observed: Heuristic: User consequence: Frequency (1–4): Impact (1–4): Persistence (1–4): Severity decision: Recommended direction: Validation needed:
06 · Use judgment
Where it helps—and where it breaks
Use when
- A design or product can be inspected
- Testing time is limited but not eliminated
- Teams need a shared critique vocabulary
Do not use when
- Reviewers lack domain and accessibility context
- Findings will be treated as proof of user behavior
- The problem is purely visual preference
Advantages
- Fast and relatively low cost
- Covers states teams often forget
- Creates traceable findings
Limitations & criticisms
- Reviewer skill affects results
- Cannot replace observation with users
- General principles require contextual judgment
Common failure modes
- One evaluator declaring certainty
- Listing violations without consequences
- Ignoring accessibility standards
Often confused with
A heuristic evaluation is expert inspection; usability testing observes representative people attempting tasks. Use both for different evidence.
Practical checklist
Reflection questions
- Which finding is merely preference?
- What could a reviewer never learn without users?
07 · Check
Five-question knowledge check
Key takeaways
- Inspect an interface systematically for common usability risks before or alongside user testing.
- Fast and relatively low cost
- Reviewer skill affects results
08 · Go deeper
Sources and further reading
- 10 Usability Heuristics for User Interface DesignJakob Nielsen · Nielsen Norman Group · 1994; reviewed 2024
Names, intent, and status as broad rules of thumb.
- What is Heuristic Evaluation?Interaction Design Foundation · IxDF
Independent explanation of evaluator practice and the practical meaning of Nielsen–Molich heuristics.