Skip to main content

Heuristic Review Tool

Use this checklist to evaluate an interface against Nielsen's 10 usability heuristics. Each section includes specific questions to assess during your review.

Last updated: February 2025

How to use this tool​

  1. Select a specific task flow or area to review
  2. Work through each heuristic, assessing the interface
  3. Check items that pass; note issues for items that don't
  4. Document severity for each issue found
  5. Compile findings with recommendations

This checklist works best with 3-5 evaluators reviewing independently, then comparing findings.

Severity ratings

For each issue found, rate severity: Critical (prevents task completion), Major (significant difficulty), Minor (annoyance but workaround exists), Cosmetic (minor polish issue).

1. Visibility of system status​

The system should keep users informed about what is going on through appropriate feedback within reasonable time.

Questions to ask:

  • Does the user always know what's happening?
  • Is there ever a delay without feedback?
  • Can users tell what mode or state they're in?

2. Match between system and the real world​

The system should speak the users' language, with words, phrases, and concepts familiar to the user.

Questions to ask:

  • Would a new user understand this terminology?
  • Does the interface match how users think about this task?
  • Are metaphors appropriate and consistent?

3. User control and freedom​

Users often choose system functions by mistake and need a clearly marked "emergency exit."

Questions to ask:

  • What happens when a user makes a mistake?
  • Can users always get back to where they were?
  • Is there a clear way to cancel or exit?

4. Consistency and standards​

Users should not have to wonder whether different words, situations, or actions mean the same thing.

Questions to ask:

  • Does the same thing always look and work the same way?
  • Are there unexpected differences between similar pages or features?
  • Do standard patterns (like menus, forms) behave as expected?

5. Error prevention​

Even better than good error messages is a careful design that prevents problems from occurring.

Questions to ask:

  • What mistakes might users make? Does the design prevent them?
  • Are irreversible actions adequately protected?
  • Do users have enough information to avoid errors?

6. Recognition rather than recall​

Minimize user's memory load by making objects, actions, and options visible.

Questions to ask:

  • Does the user need to remember anything from previous screens?
  • Are all available actions discoverable?
  • Is contextual help available where needed?

7. Flexibility and efficiency of use​

Accelerators—unseen by the novice user—may speed up interaction for the expert user.

Questions to ask:

  • Can experienced users work efficiently?
  • Are there shortcuts for common tasks?
  • Is the interface adaptable to different skill levels?

8. Aesthetic and minimalist design​

Interfaces should not contain information which is irrelevant or rarely needed.

Questions to ask:

  • Does every element serve a purpose?
  • Is the most important content most visible?
  • Is there visual noise that could be removed?

9. Help users recognize, diagnose, and recover from errors​

Error messages should be expressed in plain language, precisely indicate the problem, and suggest a solution.

Questions to ask:

  • Would a user understand this error message?
  • Does the message help the user fix the problem?
  • Is user data preserved when errors occur?

10. Help and documentation​

Even though it is better if the system can be used without documentation, it may be necessary to provide help.

Questions to ask:

  • Can users find help when they need it?
  • Does the help actually help (not just describe features)?
  • Is help necessary, or could the interface be clearer?

Documenting findings​

For each issue discovered:

  1. Location: Where in the interface
  2. Heuristic violated: Which principle(s)
  3. Description: What's wrong
  4. Severity: Critical / Major / Minor / Cosmetic
  5. Recommendation: How to fix it
  6. Evidence: Screenshot or recording if helpful

Tips for effective reviews​

  • Review the interface before filling out the checklist to understand context
  • Complete the checklist independently, then compare with other evaluators
  • Don't try to review everything at once—focus on specific flows
  • Distinguish between personal preference and usability issues
  • Prioritize findings by severity and frequency
Related resources