Heuristic Evaluation: The Audit Before the Test

Before you schedule participants, before you set up recordings, before you spend a single euro on incentives—ask yourself: are there obvious problems you could find without users?

Heuristic evaluation is the answer. It is a systematic expert review that catches the low-hanging fruit, so your user testing budget goes toward the problems only real users can reveal.

The "Save Your Budget" Rule

Do not test basic hygiene issues with real users. It is waste.

The Problem

Imagine running a usability test and discovering:

• The "Submit" button is gray and looks disabled
• Error messages do not explain what went wrong
• Users cannot get back to the homepage from the checkout flow
• The search icon is labeled "Find" in one place and "Search" in another

These are real problems—but they are obvious problems. You did not need to pay participants and spend hours in sessions to find them. An experienced practitioner could spot them in 20 minutes.

The Solution

Run a heuristic evaluation first to catch the obvious issues. Clean them up. Then run user testing to discover the complex, domain-specific problems that require real user context.

The ROI

The combined approach costs only slightly more than user testing alone but produces dramatically cleaner findings. Users encounter a product that at least makes basic sense, revealing deeper issues instead of stumbling over obvious flaws.

The Framework: Nielsen's 10 Heuristics

The most widely used framework is Jakob Nielsen's 10 Usability Heuristics. These are not rigid rules—they are principles for identifying common usability failures.

The 10 Heuristics

Using the Heuristics

Work through one heuristic at a time. For each heuristic, review every screen or component and ask: "Does this violate the principle?" If it does, document what the violation is, where it occurs, and how severe it is. If it does not, move to the next screen.

For how accessibility heuristics extend this evaluation framework, see Accessibility Testing: Beyond Compliance.

How to Execute

The Process

Step 1: Select Evaluators (3-5 experts)

More evaluators find more problems, with diminishing returns:

For most projects, 3-5 evaluators provide the best cost-benefit ratio.

Step 2: Brief the Evaluators

Provide:

• The interface (prototype, staging environment, or production)
• Target user personas and key tasks
• The heuristic framework to use
• Severity rating scale
• Documentation template

Step 3: Independent Evaluation

Each evaluator reviews the interface independently, without discussing with others. This prevents groupthink and ensures diverse perspectives.

Typical time: 1-2 hours per evaluator for a moderately complex interface.

Step 4: Document Findings

Each finding should include:

Step 5: Aggregate and Deduplicate

After independent evaluation:

1. Collect all findings into a single list
2. Merge duplicates (same issue found by multiple evaluators)
3. Note agreement level (issues found by 3+ evaluators are high confidence)
4. Prioritize by severity and frequency

Severity Ratings

When to Use Heuristic Evaluation

Before User Testing (Prototype Cleanup)

The most common use: clean your prototype before showing it to participants.

Timeline:

Design Complete → Heuristic Eval (1-2 days) → Fix Issues (1-3 days) → User Testing

Benefits:

• Users encounter fewer obvious issues
• User testing reveals deeper, domain-specific problems
• Sessions are more efficient (less time on basic issues)
• Findings are more actionable (focused on real complexity)

On Legacy Products (Building a Backlog)

For existing products with no recent evaluation, heuristic evaluation builds a prioritized improvement backlog.

Timeline:

Legacy Product → Heuristic Eval (2-3 days) → Prioritized Backlog → Incremental Fixes

Benefits:

• Quick baseline of current usability state
• Objective prioritization for improvement work
• Does not require user recruitment
• Can be done on short notice

After Major Redesigns (Quick Validation)

When you have redesigned a significant portion of the interface, heuristic evaluation provides fast feedback before investing in user testing.

Benefits:

• Catches regressions from the previous version
• Identifies new issues introduced by the redesign
• Faster turnaround than recruiting participants

For how heuristic evaluation feeds into the broader research plan, see The Research Plan.

What Heuristic Evaluation Cannot Do

Heuristic evaluation is powerful but limited:

The Evaluation Template

Use a structured template to ensure consistency:

HEURISTIC EVALUATION REPORT

Product: [Name/Version]
Evaluator: [Name]
Date: [Date]
Scope: [Screens/flows evaluated]

FINDINGS

#1
Location: [Specific screen/component]
Heuristic: [Number and name]
Issue: [Description of the problem]
Severity: [Critical/Major/Minor/Cosmetic]
Recommendation: [Suggested fix]
Screenshot: [If applicable]

#2
...

Running a Group Debrief

After independent evaluation, bring evaluators together:

1. Share findings (round-robin, each evaluator presents their top issues)
2. Discuss disagreements (different severity ratings, missed issues)
3. Merge duplicates (combine identical findings, note agreement level)
4. Prioritize (vote on top issues to address before user testing)
5. Assign owners (who will fix what, by when)

What This Means for Practice

Heuristic evaluation is the audit before the test. Use it to:

1. Save budget: Catch 60%+ of obvious issues without recruiting participants
2. Clean prototypes: Fix basic problems before users encounter them
3. Focus user testing: Let real users reveal complex, domain-specific issues
4. Build backlogs: Quickly assess legacy products for improvement opportunities
5. Use 3-5 evaluators: One finds 35%, five find 75%

The best usability test is one where users can actually engage with the core experience—not one where they stumble over obvious flaws you could have found yourself.

For the next step after heuristic evaluation, see Usability Test Scripting: Copy-Paste Templates.