UX Audit Form: Heuristic Evaluation

Product Name:

Date of Audit:

Auditor:

Executive Summary

Product Usability Score (out of 100):

Total Issues Identified:

High Criticality Alerts:

Section 1: Heuristic Evaluation Matrix

Evaluate the interface against the 10 Jakob Nielsen Heuristics. Use the formula:Issue Criticality = Severity * Complexity

	Heuristic	Status	Severity (1-4)	Complexity (1-5)	Issue Criticality
	A	B	C	D	E
1	1. Visibility of System Status				0
2	2. Match: System & Real World				0
3	3. User Control and Freedom				0
4	4. Consistency and Standards				0
5	5. Error Protection				0
6	6. Recognition vs. Recall				0
7	7. Flexibility & Efficiency of Use				0
8	8. Aesthetic & Minimalist Design				0
9	9. Error Recovery (Help / Diagnose)				0
10	10. Help and Documentation				0

Section 2: Primary Violation Log

Note: Use this section to document the most critical failure identified in Section 1. If multiple heuristics failed, list the primary blocker here.

Target Heuristic:

Observation & Path:

User Impact Analysis:

Evidence Attachment (Upload Screenshot Proof):

Choose a file or drop it here

Describe what the screenshot highlights:

Section 3: Severity & Complexity

To ensure consistency across different auditors, use the following scales:

Severity Scale (Impact on User):

Cosmetic: No real barrier; slight visual annoyance.
Minor: Fix is low priority; user can easily work around it.
Major: Important to fix; causes significant frustration/delay.
Catastrophic: Must fix; prevents task completion or causes data loss.

Complexity Scale (Effort to Fix):

Trivial: Simple text change or CSS tweak.
Easy: Minor layout adjustment or icon update.
Moderate: Requires logic changes or new component behavior.
Difficult: Significant backend or architectural overhaul.
Extensive: Requires complete redesign and multi-team coordination.

Severity:

scale_onescale_twoscale_threescale_four

Complexity:

scale_onescale_twoscale_threescale_fourscale_five

Section 4: Strategic Prioritisation & Roadmap

Instructions: Group the failed heuristics from Section 1 into the following categories based on their Criticality Scores.

Priority 1: Critical Blockers (Score 16–20)

High impact, often high effort. These are non-negotiable fixes.

	Issue	Required Action	Owner
	A	B	C
1
2
3
4
5
6
7
8
9
10

Priority 2: "Quick Wins" (High Severity, Low Complexity)

The best ROI. These fix major pain points with minimal coding effort.

	Issue	Required Action	Owner
	A	B	C
1
2
3
4
5
6
7
8
9
10

Priority 3: Technical Debt / Backlog (Low Severity, High Complexity)

Issues that are annoying but difficult to fix. Schedule for future sprints.

	Issue	Required Action	Owner
	A	B	C
1
2
3
4
5
6
7
8
9
10

Section 5: Auditor's Qualitative Assessment

General Impressions:

Accessibility Note:

Suggested Next Steps:

Form Template Insights

Please remove this form template insights section before publishing.

UX Audit Form Template: Strategic Insights

This UX Audit Form is a structured diagnostic tool designed to evaluate a digital product's usability through the lens of Nielsen’s 10 Heuristics. Unlike a general feedback survey, this form provides a quantitative and qualitative framework to identify design flaws, calculate their business impact, and prioritize engineering efforts.

The form acts as a bridge between User Experience Design and Project Management, turning subjective observations into actionable data.

1. The Scoring Philosophy (Data-Driven UX)

The core of this form is the Criticality Formula (Severity * Complexity). This ensures that the audit doesn't just list "what is broken," but also "how hard it is to fix."

It prevents "Analysis Paralysis" by mathematically distinguishing between a catastrophic bug that is easy to fix (The Quick Win) and a minor visual glitch that requires a total backend rewrite (Technical Debt).
The Product Usability Score (0–100) provides a high-level KPI that stakeholders can use to track design improvements over successive development sprints.

2. Logic and Data Structure

The form is designed with relational dependencies. Each "Fail" marked in the initial evaluation matrix triggers a requirement for evidence in the detailed log section.

Data Types: The form utilizes Integers for scoring, Booleans for pass/fail status, and String/Text for qualitative observations.
Validation: The use of standardized scales (1–4 and 1–5) ensures "Inter-rater Reliability," meaning two different auditors should, in theory, arrive at a similar Criticality Score for the same issue.

3. Evidence-Based Documentation

By including a mandatory Screenshot Proof and User Impact section, the form moves beyond opinion. It requires the auditor to demonstrate the "Path to Failure," providing developers with a visual reference to reproduce the issue. The "User Impact" field forces the auditor to justify the severity by explaining the psychological or functional cost to the end-user (e.g., cognitive load, frustration, or task abandonment).

4. Strategic Prioritization

The form's final output is a Categorized Roadmap. It automatically segments findings into three tiers:

The Firefighters (Priority 1): High-risk issues that threaten the product's core functionality.
The Value Boosters (Priority 2): Low-effort changes that significantly improve the user’s perception of quality.
The Long-Term Vision (Priority 3): Complex architectural issues that require roadmap planning rather than immediate patching.

5. Qualitative Context

The final section provides a "Human Layer" to the data. While the scores provide the "What," the Auditor’s Qualitative Assessment provides the "Why." This section captures nuances like brand trust, aesthetic cohesion, and accessibility—elements that are sometimes too subjective for a strict 1–4 scale but are vital for a premium product experience.

Summary of Purpose:

This form is built to transform a standard design review into a prioritized backlog. It allows Product Managers to see at a glance where the product stands, what the most "expensive" UX debts are, and which fixes will yield the highest return on investment for the next release cycle.

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.