What it is
In a heuristic evaluation, evaluators inspect an interface and judge it against recognized principles. Jakob Nielsen's ten usability heuristics are the most common set. They are broad rules of thumb, not strict rules, and they apply across products.
The ten heuristics
| Heuristic | Ask yourself |
|---|---|
| Visibility of system status | Does the user always know what is going on? |
| Match with the real world | Does it speak the user's language? |
| User control and freedom | Can people undo and exit easily? |
| Consistency and standards | Do similar things look and act alike? |
| Error prevention | Is it hard to make a costly mistake? |
| Recognition over recall | Is information visible instead of remembered? |
| Flexibility and efficiency | Are there shortcuts for experts? |
| Aesthetic and minimalist design | Is everything on screen necessary? |
| Error recovery | Are error messages plain and helpful? |
| Help and documentation | Is help available in context? |
How to run one
Define scope
Pick the flows and screens to evaluate, and the user type in mind.
Evaluate alone
Each evaluator spends one to two hours per pass, noting violations.
Combine
Meet to merge duplicates and discuss disagreements.
Rate severity
Score each issue by frequency, impact, and how hard it is to overcome.
Recommend
Pair each issue with a suggested fix.
NN/g recommends each evaluator works independently first, then compares. Independent passes catch more than a group walkthrough.
Use it well
Heuristics find likely problems quickly. They do not tell you how real users will behave. Use the evaluation to clean up the obvious issues, then spend your user testing time on the harder questions.



