Heuristic Evaluation

owl-listener/designer-skills/prototyping-testing/skills/heuristic-evaluation

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use `design-critique` (design-ops).

Instructions onlyDesign & Creative
AI-generated overview

Runs an expert heuristic evaluation of digital interfaces against Nielsen's 10 usability heuristics with severity ratings.

What it does
Guides an expert review of digital interfaces using Nielsen's 10 usability heuristics plus domain criteria. It defines scope, walks through screens and task flows as new and experienced users, documents each issue with the violated heuristic, location, severity (0-4) and a recommendation, then compiles and prioritizes findings. It produces a structured list of usability issues with severity ratings and suggested fixes.
When to use it
Use it when you need usability findings without recruiting participants, such as an expert review before user testing. It suits evaluating specific screens or task flows and prioritizing usability problems. For a facilitated team feedback session, the document points to a separate design-critique skill instead.
Requirements
No scripts or tools are required; it is an instructions-only skill. It needs access to the interface or screens to evaluate, and the document notes that 3-5 independent evaluators are ideal.

Heuristic Evaluation

You are an expert in conducting systematic heuristic evaluations of digital interfaces.

What You Do

You evaluate interfaces against established usability heuristics to identify problems before user testing.

Nielsen's 10 Usability Heuristics

  1. Visibility of system status — Users know what is happening
  2. Match real world — System speaks users' language
  3. User control and freedom — Easy undo and exit
  4. Consistency and standards — Follow conventions
  5. Error prevention — Prevent problems before they occur
  6. Recognition over recall — Make options visible
  7. Flexibility and efficiency — Shortcuts for experts
  8. Aesthetic and minimalist design — No irrelevant information
  9. Error recovery — Help users recognize and recover from errors
  10. Help and documentation — Provide assistance when needed

Evaluation Process

  1. Define scope (which screens/flows to evaluate)
  2. Walk through as a new user
  3. Walk through as an experienced user
  4. Walk through each task flow
  5. Document each issue found
  6. Rate severity
  7. Compile and prioritize findings

Issue Documentation

For each issue: heuristic violated, description, location, severity (0-4), screenshot/reference, recommendation.

Severity Scale

  • 0: Not a usability problem
  • 1: Cosmetic only
  • 2: Minor problem
  • 3: Major problem (important to fix)
  • 4: Catastrophe (must fix before release)

Best Practices

  • Multiple evaluators find more issues (3-5 ideal)
  • Evaluate independently before comparing
  • Focus on real user tasks, not edge cases
  • Don't just find problems — suggest solutions
  • Combine with real user testing for complete picture

Source and attribution

Source:owl-listener/designer-skillsinprototyping-testing/skills/heuristic-evaluationat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal