Template Overview

User testing with real participants is invaluable, but asking users to test an interface riddled with basic usability violations is a waste of time and money. A formal Heuristic Usability Evaluation allows expert UX practitioners to systematically inspect an interface against proven cognitive design principles.

Developed by Jakob Nielsen and Rolf Molich, the 10 Usability Heuristics provide a time-tested diagnostic lens for finding navigation traps, ambiguous error states, cognitive overload, and broken mental models.

This template organizes your heuristic inspection: auditing the interface against each of the 10 principles, assigning standardized severity ratings (0 to 4), capturing visual defect evidence, and prescribing concrete design remediations.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Heuristic UX Audit: [Interface / Flow Name]"
date: [YYYY-MM-DD]
evaluator: "[[Senior UX Designer / Architect]]"
interface_audited: "Markdown Template Gallery & Category Navigation"
overall_usability_health: [High / Production Ready | Moderate Deficiencies | Severe Usability Deficits]
total_violations_found: 5
catastrophic_violations: 0
major_violations: 1
minor_violations: 4
tags: [heuristic-evaluation, ux-audit, nielsen-norman, usability, design]
---

# Heuristic UX Audit: [Interface / Flow Name] β€” [YYYY-MM-DD]

## 1. Audit Scope & Evaluation Framework
- **Evaluation Surface:** Web-based Template Gallery main hub (`/templates`), 12 category hubs (`/templates/[category]`), and template detail pages.
- **Methodology:** Systematic walk-through evaluating interface states against the 10 Nielsen-Norman Usability Heuristics.

## 2. Comprehensive Heuristic Inspection Matrix
| Heuristic Principle | Status | Violations Identified | Severity (0-4) |
| :--- | :--- | :--- | :--- |
| **1. Visibility of System Status** | 🟒 Pass | Copy button displays instant visual feedback ('Copied!') on click. | 0 - None |
| **2. Match Between System & Real World** | 🟒 Pass | Category names match real-world organizational rituals (Standups, 1-on-1s). | 0 - None |
| **3. User Control & Freedom** | 🟑 Minor Issue | Missing 'Back to Category' quick navigation on mobile layout. | 2 - Minor |
| **4. Consistency & Standards** | 🟒 Pass | Typography, badge pills, and button states adhere to design tokens. | 0 - None |
| **5. Error Prevention** | 🟒 Pass | Pre-commit validation guarantees 100% of links and canonical tags resolve. | 0 - None |
| **6. Recognition Rather Than Recall** | 🟒 Pass | Breadcrumbs show full hierarchical position at all times. | 0 - None |
| **7. Flexibility & Efficiency of Use** | 🟑 Minor Issue | Template code blocks lack keyboard shortcut hint for quick copy. | 1 - Cosmetic |
| **8. Aesthetic & Minimalist Design** | 🟒 Pass | Clean typography, ample whitespace, zero extraneous promotional banners. | 0 - None |
| **9. Help Users Recognize Errors** | 🟒 Pass | 404 page provides clear search links back to template hubs. | 0 - None |
| **10. Help & Documentation** | 🟑 Major Issue | FAQ cards lack quick jump links on long template pages. | 3 - Major |

## 3. Deep-Dive: Major Violations & Remediation Recipes
### Violation H10: Missing Quick Navigation for Extensive Template Documentation
- **Observed Defect:** On templates with >1,000 words, users must scroll through multiple screen heights to locate the FAQ and AI prompt sections.
- **Prescribed Remediation:** Implement a sticky sidebar table of contents or anchor jump pills at the top of the template prose area.

## 4. Prioritized Engineering & Design Backlog
- [ ] Implement mobile-responsive 'Back to Category' sticky link.
- [ ] Add anchor navigation pills for 'Structure', 'Example', 'FAQ', and 'AI Prompt'.
- [ ] Add `title` attribute tooltips to download buttons indicating file format.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "UX Audit: Templates Gallery Hub"
date: 2026-10-07
evaluator: "[[Kiran Shah]]"
total_violations_found: 3
tags: [heuristic-evaluation, ux-audit]
---

# UX Audit: Templates Gallery Hub β€” October 7, 2026

## 1. Summary
Overall usability is strong. Component tokens and breadcrumb trails adhere strictly to design system standards.

## 2. Fixes Prescribed
Add hover state tooltips to category count badges to explain total template coverage.

When to Use and When to Avoid

When to Use

  • Use during expert design audits of new or existing software interfaces.
  • Use to evaluate interfaces against the established 10 Nielsen-Norman usability heuristics.
  • Use prior to conducting user testing to eliminate low-level interface bugs and cognitive traps.

When to Avoid

  • Avoid using as a substitute for real user feedback from actual target customers.
  • Avoid using for backend API architecture reviews.

On-Device AI Integration

Compile heuristic usability audits with Oyma on macOS:

Analyze the design audit review notes or recorded walkthrough:
1. Synthesize the audited interface surface and overall usability health assessment.
2. Build the 10-heuristic inspection table evaluating each principle with identified violations and severities (0-4).
3. Detail deep-dive descriptions for all major and catastrophic usability violations with remediation recipes.
4. Record the prioritized design backlog items with assigned fixes.
Output in structured, professional CommonMark.

Your proprietary design evaluations and interface audit records stay private on your Mac.

Frequently Asked Questions

What are the 10 Nielsen-Norman usability heuristics?

Foundational UX principles including Visibility of System Status, Match Between System and Real World, User Control and Freedom, Consistency and Standards, and Error Prevention.

How does this template grade heuristic violation severity?

Severities range from 0 (Cosmetic problem only) to 4 (Usability catastrophe that blocks workflow).

Why perform heuristic audits before user testing?

Heuristic evaluations allow expert designers to identify and fix obvious interface flaws early, so user testing sessions can focus on deeper workflow validation.