UX Heuristic Evaluation Template - Nielsen's 10 Heuristics Applied to SaaS

This template is a structured evaluation framework based on Jakob Nielsen's 10 Usability Heuristics (originally published 1994 by Nielsen & Molich, refined based on factor analysis of 249 usability problems — the definitive set remains unchanged since 1994). Each heuristic is contextualized for SaaS products with specific checkpoints, severity scoring, and space for findings.

Instructions:

1. Select 3-5 key user workflows to evaluate (e.g., "Signup → First value," "Create report," "Invite teammate," "Upgrade plan")
2. Walk through each workflow while evaluating against all 10 heuristics
3. For each finding, note: the heuristic violated, the specific screen/interaction, the severity, and a recommended fix
4. Compile findings into a prioritized action list

Severity Scale (Nielsen's 0-4 Scale):

• 0 — Not a usability problem
• 1 — Cosmetic problem only; fix if time allows
• 2 — Minor usability problem; fixing this has low priority
• 3 — Major usability problem; important to fix, high priority
• 4 — Usability catastrophe; imperative to fix before release

Evaluator Information:

• Evaluator Name:
• Product Name:
• Version / Date Evaluated:
• Workflows Evaluated:

Principle: The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

Source: Nielsen Norman Group — "When users know the current system status, they learn the outcome of their prior interactions and determine next steps. Predictable interactions create trust in the product as well as the brand."

SaaS Checkpoints:

Common SaaS Violations:

• Save button clicked → no feedback for 3 seconds → user clicks again → duplicate save
• Data import running → no progress indicator → user navigates away → import fails silently
• Dashboard data is 6 hours stale but shows no "last updated" timestamp → user makes decisions on old data

Principle: Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

Source: Nielsen Norman Group — "When it's easy for people to back out of a process or undo an action, it fosters a sense of freedom and confidence. Exits allow users to remain in control of the system and avoid getting stuck and feeling frustrated."

SaaS Checkpoints:

Common SaaS Violations:

• User accidentally deletes a project → no undo, no trash, permanently gone
• User starts a multi-step form → can't go back to step 2 from step 4 → must restart
• User enters a modal → no close button visible, clicking outside doesn't close it

Principle: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action.

Source: Nielsen Norman Group — "There are two types of errors: slips and mistakes. Slips are unconscious errors caused by inattention. Mistakes are conscious errors based on a mismatch between the user's mental model and the design."

SaaS Checkpoints:

Common SaaS Violations:

• User types "jan 5 2024" in a date field → error → field expected "2024-01-05" format → should have used a date picker
• User accidentally clicks "Delete Account" → no confirmation → account gone
• User types 3,000 words in a text area → navigates away → no unsaved warning → content lost

Principle: Shortcuts — hidden from novice users — can speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

SaaS Checkpoints:

Common SaaS Violations:

• No keyboard shortcuts in a product used 8 hours/day by power users
• Every new report requires entering the same 10 filters — no ability to save filter presets
• No bulk actions — deleting 50 items requires 50 individual delete confirmations

Principle: Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.

SaaS Checkpoints:

Common SaaS Violations:

• "An error occurred" — no specifics, no solution, no help
• "Error 500" — a server error code shown to end users
• "Invalid input" on a form with 12 fields — which field? What's invalid? How to fix?

After evaluating all 10 heuristics across your selected workflows, compile your findings:

Sort by severity (4 → 0) to create your prioritized fix list.