UI/UX Design Heuristic Evaluation Expert Reviews
Usability testing with real users takes time to plan, recruit, and run. Heuristic evaluation is a faster expert-driven method that can identify many usability problems in a single day. An evaluator examines a product against a set of established usability principles — called heuristics — and reports every violation they find. This page teaches you how heuristic evaluation works, what the heuristics are, and how to conduct and report one yourself.
What Is Heuristic Evaluation?
Heuristic evaluation is a usability inspection method where one or more experts review a product's interface against a list of recognized usability principles. The goal is to find problems before users encounter them — making it ideal for early-stage designs, prototype reviews, and design critiques.
HEURISTIC EVALUATION OVERVIEW: WHO does it: UX designers, researchers, or usability specialists (Not the person who built the product — too familiar with it) Ideally 3–5 evaluators for best coverage WHAT they use: A set of usability heuristics (principles) The product itself (live, prototype, or design mockup) A severity rating scale HOW LONG it takes: 1–2 hours per evaluator for a single product flow Half a day for a more complex multi-flow product WHAT it finds: Violations of usability principles Missing feedback states Inconsistencies Navigation problems Confusing labels and copy WHAT it CANNOT find: Problems specific to your particular user's mental models Cultural usability issues Task-specific workflows users need for real jobs → These require actual usability testing with real users
Jakob Nielsen's 10 Usability Heuristics
Jakob Nielsen developed the most widely used set of heuristics in 1994. Despite being over 30 years old, they remain the standard for evaluating digital interfaces. Every serious UI/UX designer should know all ten by heart.
Heuristic 1: Visibility of System Status
The system should always keep users informed about what is going on through appropriate feedback within reasonable time.
HEURISTIC 1 EXAMPLES:
VIOLATION:
User clicks "Upload File" button. Nothing happens visually.
User clicks again. Still nothing. User has no idea if it worked.
CORRECT:
User clicks "Upload File" → Button immediately shows spinner
→ Progress bar appears: "Uploading... 45%"
→ Completes: "✓ Upload successful"
MORE EXAMPLES:
Violation: No active state in navigation — user cannot tell
which section they are currently in.
Correct: Active navigation item is highlighted/underlined.
Violation: Form submits but page just reloads — no confirmation.
Correct: "✓ Your message was sent. We'll reply within 24 hours."
Violation: No loading state during a network request.
Correct: Skeleton screen or spinner while content loads.
EVALUATION QUESTIONS:
→ Does every action have immediate visual feedback?
→ Does every process (loading, saving, uploading) have a status?
→ Can the user always tell what the system is currently doing?
Heuristic 2: Match Between System and the Real World
The system should speak the users' language, with words, phrases, and concepts familiar to them. Follow real-world conventions and make information appear in a natural and logical order.
HEURISTIC 2 EXAMPLES: VIOLATION: A file storage app uses internal engineering terms: "Blob storage container" instead of "Files folder" "Authentication token expired" instead of "Please log in again" CORRECT: Use words and metaphors users already know: Trash/Bin icon for delete (real-world object) Folder icon for grouping files (real-world object) Shopping cart for adding items before purchase Envelope icon for email or messages EVALUATION QUESTIONS: → Is any language technical or internal-company jargon? → Do icons use real-world metaphors users will recognize? → Does the flow match the order users would naturally think? → Do any labels require explanation?
Heuristic 3: User Control and Freedom
Users often choose functions by mistake. They need a clearly marked "emergency exit" to leave unwanted states without having to go through an extended dialogue.
HEURISTIC 3 EXAMPLES:
VIOLATION:
User accidentally deletes a message. There is no undo.
User must recreate the entire message from scratch.
CORRECT:
"Message deleted. [Undo] (5 seconds remaining)"
MORE EXAMPLES:
Violation: Modal with no close button or Escape key support.
Correct: Every modal has × button AND closes on Escape key.
Violation: Multi-step form with no Back button on step 3.
Correct: Back button on every step. Data is preserved.
Violation: Clicking a button starts an irreversible action immediately.
Correct: Confirm dialog: "Are you sure? This cannot be undone."
Then: 30-day trash before permanent deletion.
EVALUATION QUESTIONS:
→ Can users undo the most recent action?
→ Can users exit any state or modal easily?
→ Does the back button work correctly throughout?
→ Are destructive actions reversible or at least confirmed?
Heuristic 4: Consistency and Standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
HEURISTIC 4 EXAMPLES: VIOLATION: The same action is called "Delete" in one place, "Remove" in another, and "Clear" in a third. Different button styles for the same action on different pages. Cancel button is on the left in some dialogs, right in others. CORRECT: Consistent terminology: "Delete" everywhere for permanent removal. Consistent visual style: Same button style for same button type. Consistent position: Cancel always on the left. PLATFORM CONSISTENCY: iOS: Back button in top-left corner. Always. Android: System back button navigates back. Always. Web: Ctrl+Z undoes. F5 refreshes. Ctrl+C copies. Violating these platform conventions disorients experienced users. EVALUATION QUESTIONS: → Is the same action called the same thing everywhere? → Do all similar components look and behave identically? → Does the product follow OS/platform conventions? → Are button positions (confirm/cancel) consistent?
Heuristic 5: Error Prevention
A careful design prevents problems from occurring in the first place. Even better than good error messages is preventing the problem from happening at all.
HEURISTIC 5 EXAMPLES:
VIOLATION:
Date input accepts any text. User types "tomorrow" and
the form submits silently with a broken date value.
A "Send to All" button sits next to "Send Test" with no
confirmation. Users frequently send campaigns early by mistake.
CORRECT:
Date field only accepts valid date formats (use a date picker).
"Send to All" requires typing "SEND" in a confirmation field.
MORE EXAMPLES:
Violation: Form accepts and submits with empty required fields.
Correct: Disable Submit button until all required fields are filled.
Violation: Credit card number field accepts letters.
Correct: type="tel" forces numeric input only.
Violation: Dropdown contains both "Delete Account" and
"Delete Post" next to each other.
Correct: Separate destructive options visually. Add confirmation.
EVALUATION QUESTIONS:
→ Are users constrained from entering invalid data?
→ Do dangerous actions require a confirmation step?
→ Are potentially confusing similar options clearly differentiated?
→ Does the form prevent submission until minimum requirements are met?
Heuristic 6: Recognition Over Recall
Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another.
HEURISTIC 6 EXAMPLES:
VIOLATION:
A settings panel requires users to remember what they set
in a previous panel to make the current decision.
A search bar shows no recent searches when the user opens it.
User must remember what they searched before.
An icon-only navigation with no labels. Users must remember
what each icon means.
CORRECT:
Show users the information they need at the moment they need it.
Recent searches appear when search opens.
Navigation icons have visible labels.
Wizard shows a summary of choices from previous steps.
MORE EXAMPLES:
Violation: Keyboard shortcut panel that lists shortcuts only.
User must memorize them to use them.
Correct: Contextual hints show shortcuts next to their actions
in menus.
Violation: Error message says "Value out of range" without
reminding user what the valid range is.
Correct: "Value must be between 1 and 100. You entered 150."
EVALUATION QUESTIONS:
→ Are icons labeled or do users need to memorize their meaning?
→ Does the interface surface relevant context at decision moments?
→ Do error messages include the relevant constraint information?
→ Are recent actions, searches, or history shown where useful?
Heuristic 7: Flexibility and Efficiency of Use
Accelerators — unseen by novice users — may speed up interaction for expert users. The design should cater to both inexperienced and experienced users.
HEURISTIC 7 EXAMPLES:
FEATURES FOR EXPERTS (That do not confuse beginners):
Keyboard shortcuts: Ctrl+S saves, Ctrl+Z undoes
Command palette: Cmd+K opens searchable command list (Figma, VS Code)
Batch actions: Select multiple items, delete all at once
Customizable views: Save custom dashboard layout
Filters and search: Advanced filtering for power users
FEATURES FOR BEGINNERS (That do not bore experts):
Guided tours: Step-by-step onboarding (skippable)
Inline hints: Tooltips on hover explaining options
Defaults: Smart pre-filled values so beginners start faster
Simplified views: "Simple" vs "Advanced" toggle for complex tools
GOOD BALANCE EXAMPLE (Notion):
Beginner: Can use it like a word processor. Type and format text.
Expert: Slash commands (/table, /callout), keyboard shortcuts,
custom database properties, API access.
Both users get value from the same product without friction.
EVALUATION QUESTIONS:
→ Are there keyboard shortcuts for frequent actions?
→ Can expert users skip guided flows?
→ Can users customize or personalize their workflow?
→ Do power features coexist without overwhelming new users?
Heuristic 8: Aesthetic and Minimalist Design
Dialogues should not contain irrelevant or rarely needed information. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
HEURISTIC 8 EXAMPLES: VIOLATION: Dashboard shows 14 different widgets, all visible at once, including data the user checks twice a year. A confirmation dialog contains three paragraphs of legal text that users will never read. Navigation has 12 top-level items when 4 are used 80% of the time. CORRECT: Show the 4-6 most important metrics on the main dashboard. Allow users to add more if they want. Confirmation dialog: One clear question. Two clear buttons. Navigation: Surface 5 primary items. Group the rest under "More." MINIMALISM ≠ REMOVING USEFUL FEATURES: Minimalism means removing UNNECESSARY information. Never remove information that users need to make decisions. The goal is signal over noise — not bare-bones at the cost of utility. EVALUATION QUESTIONS: → Is there any content on screen that users rarely or never need? → Do dialogs and confirmations use plain, brief language? → Does every visual element on screen serve a clear purpose? → Is the most important information the most visually prominent?
Heuristic 9: Help Users Recognize, Diagnose, and Recover from Errors
Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.
HEURISTIC 9 — GOOD vs BAD ERROR MESSAGES: VIOLATION: "Error: 403" "Invalid input detected." "Something went wrong." "Upload failed." CORRECT: "Access denied. You don't have permission to view this page. Contact your admin to request access." "Phone number must be 10 digits. You entered 9 digits." "We couldn't connect to our servers. Check your internet connection and try again. If the problem continues, visit our status page at status.example.com" "File upload failed — your file is 24MB and the maximum is 10MB. Try compressing the file first." ERROR MESSAGE FORMULA: 1. What went wrong (specific, not generic) 2. Why it went wrong (if helpful and not obvious) 3. How to fix it (clear next step) EVALUATION QUESTIONS: → Do all error messages use plain language (no codes, no jargon)? → Does each error message identify what went wrong specifically? → Does each error message tell the user what to do next? → Are errors shown near the element that caused them?
Heuristic 10: Help and Documentation
Even though it is better if the system can be used without documentation, it may be necessary to provide help. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
HEURISTIC 10 EXAMPLES:
VIOLATION:
Help section is a giant unorganized text dump.
Search in help center does not return relevant results.
Help is only accessible from a hidden footer link.
Help content uses product-internal terminology.
CORRECT:
Contextual help: "?" icon next to complex fields that
opens a short tooltip with an explanation.
Searchable help center organized by task, not feature name.
Inline error messages with links to relevant help articles.
"What is this?" link next to unfamiliar terms.
PROGRESSIVE HELP:
Level 1: Tooltip on hover (10 words max)
Level 2: Contextual help panel (explains this specific feature)
Level 3: Full documentation (for complex, rare scenarios)
Level 4: Support chat/email (for unresolved issues)
Most users need Level 1 or 2.
Avoid forcing users to Level 4 for common questions.
EVALUATION QUESTIONS:
→ Is help accessible from within the flow where users need it?
→ Does the help center have a functional search?
→ Are help articles written in user language (not product jargon)?
→ Are empty states and errors linked to relevant help content?
How to Conduct a Heuristic Evaluation
HEURISTIC EVALUATION PROCESS:
STEP 1 — DEFINE SCOPE:
Which flows will you evaluate?
Example: Onboarding, checkout, settings, help center.
Do NOT try to evaluate the entire product in one session.
Focus on the most critical or most problematic flows first.
STEP 2 — CHOOSE EVALUATORS:
Ideal: 3–5 evaluators who are not the product's creators.
Each evaluator independently reviews the interface.
They do not confer until after individual reviews are complete.
Why multiple evaluators?
Research shows: 1 evaluator finds ~35% of usability problems.
3 evaluators find ~65%.
5 evaluators find ~75%.
Diminishing returns beyond 5.
STEP 3 — EACH EVALUATOR REVIEWS INDEPENDENTLY:
Walk through the flow 2–3 times.
First pass: Get an overview of the experience.
Second pass: Inspect each element against each heuristic.
For each violation found, note:
- What heuristic it violates
- Where it occurs (screen name, element)
- Why it is a problem
- Severity rating (1–4)
STEP 4 — AGGREGATE FINDINGS:
Collect all evaluators' findings into one list.
Combine duplicates. Note frequency of independent agreement.
(Problems found by 4 of 5 evaluators are high priority.)
STEP 5 — PRIORITIZE BY SEVERITY:
Use the severity scale to prioritize fixes.
STEP 6 — REPORT AND PRESENT:
Present findings to the design and product team.
Group violations by heuristic or by product area.
Include screenshots with annotations showing the violation.
Include a recommended fix for each finding.
Severity Rating Scale
HEURISTIC VIOLATION SEVERITY SCALE: 0 — NOT A USABILITY PROBLEM: The evaluator's concern, but not an actual usability issue. 1 — COSMETIC ONLY: Violates a heuristic but does not affect task completion. Fix only if time permits. Example: Inconsistent spacing between two secondary screens. 2 — MINOR USABILITY PROBLEM: Low priority. Does not prevent task completion. Users notice and may be briefly confused but recover. Fix before next major release. Example: An icon without a label that users take 5 seconds to decode. 3 — MAJOR USABILITY PROBLEM: High priority. Causes significant difficulty or delay. Many users will struggle here. Fix as soon as possible. Example: The error message does not explain how to recover. 4 — CATASTROPHIC / USABILITY DISASTER: Fix before launch. Users cannot complete the task. Product should not ship with this problem. Example: Submit button does not respond to click on mobile Safari. AVERAGE SEVERITY ACROSS EVALUATORS: If 5 evaluators rate a problem 2, 3, 3, 4, 3 Average: (2+3+3+4+3)/5 = 3.0 → Major problem
Heuristic Evaluation Report Format
EVALUATION REPORT TEMPLATE:
─────────────────────────────────────────────────
FINDING #7
─────────────────────────────────────────────────
Location: Checkout flow → Step 3: Payment page
Screenshot: [Annotated screenshot attached]
Heuristic violated:
H1 — Visibility of System Status
H9 — Help Users Recognize and Recover from Errors
Description:
When a credit card is declined, the system clears
the entire form and shows only: "Payment failed."
The user must re-enter all card details and has no
guidance on why the card was declined or what to try next.
Impact:
Users experiencing a declined card — already a stressful
moment — face the additional frustration of re-entering
all payment details with no guidance.
Severity: 3 (Major)
Frequency: Confirmed by 4 of 5 evaluators
Recommendation:
1. Do NOT clear the form on decline. Preserve entered data.
2. Show the specific decline reason if the payment processor
provides it (e.g., "Insufficient funds" or "Card expired").
3. Suggest alternatives: "Try a different card or use UPI."
─────────────────────────────────────────────────
Heuristic Evaluation vs Usability Testing
COMPARISON TABLE:
Heuristic Evaluation Usability Testing
─────────────────────────────────────────────────────────
Who does it: UX experts Real users
Time to run: 1–2 days 1–2 weeks
Cost: Low Medium to High
Recruitment: Not needed Required
Best for: Early-stage designs, Validating specific
quick review flows with target users
Finds: Principle violations Real task failures
Cannot find: User-specific issues Expert-only insights
Depth: Broad coverage Deep behavioral data
When to use: Before usability test After design is stable
Key Points
- Heuristic evaluation is an expert review method — evaluators inspect a product against established usability principles and report violations.
- Use 3–5 independent evaluators working separately, then combine findings — more evaluators find more problems up to the fifth evaluator.
- Jakob Nielsen's 10 heuristics cover: system status visibility, real-world language, user control, consistency, error prevention, recognition over recall, flexibility, minimalism, error recovery, and help documentation.
- Rate every violation on a severity scale from 0 (not a problem) to 4 (catastrophic — ship-blocker).
- Each finding in the report should include: what heuristic is violated, where it occurs, why it matters, severity rating, and a concrete recommendation.
- Heuristic evaluation is fast and low-cost but cannot replace usability testing — it finds principle violations, not user-specific behavior patterns.
- Use heuristic evaluation before usability testing to catch obvious problems first, then use testing to validate specific flows with real target users.