What it is
An inspection method where a few evaluators judge an interface against recognized usability heuristics, such as Nielsen’s ten, and record violations by severity.
When to use it
During Prototype or Implement, as a quick, low-cost screen before or between rounds of user testing.
Why (value)
Catches many obvious usability problems cheaply and quickly, without recruiting users.
How to run it
- Choose a heuristic set and severity scale.
- Have 3 to 5 evaluators inspect independently.
- Record each violation with heuristic and severity.
- Merge findings and remove duplicates.
- Prioritize fixes by severity.
Inputs and outputs
- Inputs: An interface, a heuristic set, evaluators.
- Outputs: A ranked list of heuristic violations.
Time and effort
Low. Hours per evaluator; no recruiting.
Evidence and limitations
Produces expert-review evidence, which is not direct-user data; it predicts likely problems and misses issues only real users reveal, and can flag false positives. Never present it as user research. See Evidence and limitations.
Tips and pitfalls
- Use multiple evaluators; one person misses most issues.
- Rate severity so fixes are prioritized.
- Do not substitute it for usability testing.
Variations
Nielsen’s heuristics, domain-specific heuristics, and persona-based inspection.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Cognitive walkthrough — Step through a task as a new user would, asking at each step whether they could figure out what to do.
- Expert review — Have an experienced UX practitioner assess a design and report likely problems and fixes.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
