UX Heuristics

UX Heuristics Framework

Practical usability principles for evaluating and improving user interfaces. Users don't read, they scan; they don't make optimal choices, they satisfice; they don't figure out how things work, they muddle through.

Core Principle

"Don't Make Me Think" — every page should be self-evident. If something requires thinking, it's a usability problem. Users have limited patience and cognitive bandwidth, so design for the scanning, satisficing, and muddling-through behavior described above.

Scoring

Goal: 10/10. Audit the interface, rate every issue on the severity scale below, then score the interface from its Quick Diagnostic results: start at 10 and subtract per failed diagnostic row, weighted by the worst severity it triggers (catastrophic/major rows cost ~2, minor/cosmetic ~1). Bands: 9-10 = no severity-3+ issues and ≤1 failed diagnostic row; 6-8 = some major issues or several failed rows; 3-5 = a catastrophic issue or many failed rows; ≤2 = core tasks blocked. Always state the current score, the highest-severity issues, and the specific fixes needed to reach 10/10.

Krug's Usability Principles

Laws 1-3 are Krug's Three Laws of Usability; #4, the Trunk Test, is his navigation orientation check.

1. Don't Make Me Think

Core concept: Every question mark that pops into a user's head adds cognitive load and distracts from the task.

Why it works: Users are on a mission — they don't want to puzzle over labels or decode clever marketing language. The less thinking required, the more likely they complete the task.

Key insights:

• Clever names lose to clear names every time
• Marketing-speak creates friction; plain language removes it
• Unfamiliar categories force users to stop and interpret
• Ambiguous links and buttons cause hesitation

Product applications:

Copy patterns:

• Action-oriented buttons: verb + noun ("Create account", "Download report")
• Avoid jargon: "Save" not "Persist", "Remove" not "Disassociate"
• If a label needs explanation, simplify the label

Ethical boundary: Clarity should serve users — never use plain language as a veneer to hide unfavorable terms.

See: references/krug-principles.md when you need the full Krug method — scanning/satisficing/muddling psychology, the goodwill reservoir, homepage and tagline guidance, and the $0 usability-testing protocol (how many users, the test script).

2. It Doesn't Matter How Many Clicks

Core concept: The myth says "users leave after 3 clicks." In reality users don't mind clicks if each one is painless, obvious, and confidence-building.

Why it works: Cognitive effort per click matters more than click count. Users abandon when they lose confidence, not when they run out of patience for clicking.

Key insights:

• Each click should be painless, obvious, and confidence-building
• Three mindless clicks beat one click that requires deliberation
• Shallow nav with clear labels beats deep nav with vague ones

Product applications:

Copy patterns:

• Progress indicators: "Step 2 of 4: Shipping details"
• Confirmations at each step: "Great, your email is verified. Now let's set up your profile."
• Clear link text: "View all running shoes" not "Click here"

Ethical boundary: Never use extra steps to bury cancellation flows — every click should move users toward their goal, not away from it.

3. Get Rid of Half the Words

Core concept: Remove half the words on each page, then half of what's left. Brevity makes useful content prominent and respects the user's time.

Key insights:

• Happy-talk ("Welcome to our website!") wastes space
• Instructions nobody reads should be removed
• "Please" and "Kindly" and polite fluff add noise
• Shorter pages mean less scrolling and faster scanning

Product applications:

Copy patterns:

• Before: "Please kindly note that you will need to enter your password in order to proceed to the next step." → After: "Enter your password to continue."
• Before: "We've received your message and will get back to you as soon as possible." → After: "Message sent. We'll reply within 24 hours."

Ethical boundary: Brevity must not omit critical information — concise disclosures for pricing, terms, and data usage are a user right.

4. The Trunk Test

Core concept: Drop a user on any random page (like being released from a car trunk at a random spot) — they should instantly answer six orientation questions: What site is this? What page? What are the major sections? What are my options here? Where am I in the hierarchy? Where's search?

Why it works: Good navigation gives constant orientation. Users who can't tell where they are feel lost and leave.

Apply it as the navigation check: page titles must match the link the user clicked, a "you are here" indicator (highlighted nav item, bold breadcrumb) must be present, and section headings must orient ("Your Account > Billing" not just "Settings").

Ethical boundary: Navigation labels must honestly represent site structure — never use misleading labels to funnel users into marketing pages.

See: references/krug-principles.md when running the Trunk Test or designing navigation — it maps each of the six questions to the page element that answers it, plus breadcrumb and permanent-navigation rules.

Nielsen's 10 Usability Heuristics

1. Visibility of System Status

Keep users informed through timely feedback. Every action needs acknowledgment — progress bars for uploads, confirmations for submissions, skeleton screens for loading. Silent failures destroy trust. Copy pattern: "Saving..." → "Saved".

2. Match Between System and Real World

Speak users' language: "Sign in" not "Authenticate", "Search" not "Query." Follow real-world metaphors (trash bin, shopping cart) and natural ordering (street → city → state → zip).

3. User Control and Freedom

Provide clear "emergency exits." Undo beats "Are you sure?" dialogs — users click through confirmations without reading. Every flow needs cancel/exit, and back buttons must never break.

4. Consistency and Standards

Same words, styles, and behaviors mean the same thing throughout. Internal consistency (your app) plus external consistency (platform conventions: logo top-left, search top-right). One term per concept — "Projects" everywhere, never mixed with "Workspaces."

5. Error Prevention

Prevent problems before they occur: constrained inputs (date pickers over text fields), autocomplete, sensible defaults, "unsaved changes" warnings. Slips (accidental wrong action) and mistakes (wrong intention) need different prevention.

6. Recognition Rather Than Recall

Minimize memory load — show options, don't require memorization. Breadcrumbs, recent searches, pre-filled fields, dropdowns with decoded values. Working memory holds ~7 items; recognition is far easier than recall.

7. Flexibility and Efficiency of Use

Serve both novices and experts: keyboard shortcuts, bulk actions, saved searches, command palettes (Cmd+K). Progressive disclosure keeps it simple for beginners while experts access full power.

8. Aesthetic and Minimalist Design

Every element must earn its place — when everything screams for attention, nothing stands out. Show what matters now, hide what doesn't. One primary CTA per page.

9. Help Users Recognize, Diagnose, and Recover from Errors

Error messages need three parts: what happened, why, and how to fix it. Plain language ("Connection failed" not "ECONNREFUSED"), specific ("Password must be 8+ characters" not "Invalid"), never blame the user, preserve their input.