Science of Apps - Launchpad · UX guide

Heuristic evaluation:
a founder's guide

A heuristic evaluation is a review of a product against a set of usability guidelines, usually Jakob Nielsen's 10 heuristics, to find likely problems without recruiting test users. Nielsen Norman Group recommends three to five people evaluating independently for one to two hours each, then merging findings and rating each one's severity from 0 to 4.

By , FounderUpdated 5 min read

Share

Quick answer: What is a heuristic evaluation?

  1. What: a review of an interface against usability guidelines.
  2. Usual guidelines: Nielsen's 10 usability heuristics (1994).
  3. Who: three to five evaluators, working independently.
  4. How long: about 1–2 hours each, per Nielsen Norman Group.
  5. Output: merged findings, each rated 0–4 for severity.

Key takeaways

  • A heuristic evaluation finds likely problems cheaply; it doesn't replace testing with users.
  • One reviewer misses issues; independent reviewers catch more.
  • Narrow the scope: one task, one user group, one device.
  • A violation isn't automatically a bug; context decides.
  • Severity ratings turn a long list into a fix order.

Founders rarely have budget for a usability lab, and they rarely need one to find their first ten problems. A heuristic evaluation, invented by Jakob Nielsen and Rolf Molich in 1990, lets a small team find likely usability issues in an afternoon by checking the product against a short list of proven principles. This guide covers Nielsen's 10 heuristics with startup examples, how to run an evaluation the way Nielsen Norman Group recommends, and how to rate what you find, as read on 17 November 2026. Jump to the 10 heuristics, how to run one or severity ratings.

Usability heuristics (Nielsen, 1994)
10
Independent evaluators recommended
3–5
Per evaluator, timeboxed
1–2 h
Nielsen's severity scale
0–4

What is a heuristic evaluation?

A heuristic evaluation is a method for finding design problems in an interface: evaluators judge it against a set of guidelines (heuristics) that make systems easy to use. It works on almost anything people interact with, from prototypes to live apps, and it's especially useful early, when fixes are cheap.

Nielsen Norman Group article How to Conduct a Heuristic Evaluation by Kate Moran and Kelley Gordon, June 25 2023, with free workbook downloads
NN/g's step-by-step guide, with a free evaluation workbook.Image: Nielsen Norman Group · Screenshot shown for commentary, 17 Nov 2026 · source

Nielsen's 10 heuristics, with startup examples

#HeuristicA startup example of a violation
1Visibility of system status"Generate report" clicked; nothing moves for 20 seconds
2Match between system and real worldOnboarding asks for a "workspace slug"
3User control and freedomNo way to undo deleting a project
4Consistency and standards"Save" is blue on one screen, grey on the next
5Error preventionA date field that accepts 31 February
6Recognition rather than recallUsers must remember an API key shown once, two screens ago
7Flexibility and efficiency of useNo keyboard shortcuts in a tool used all day
8Aesthetic and minimalist designPricing page with five banners competing with the plan cards
9Recognise, diagnose, recover from errors"Something went wrong" with no next step
10Help and documentationNo help link on the integration screen where everyone gets stuck

Table: Nielsen's 10 usability heuristics with startup examples (heuristics from Nielsen Norman Group; examples are ours)

Each heuristic has a behavioural reason behind it. Recognition rather than recall, for example, follows from limited working memory; see recognition over recall and the rest of the Laws of UX.

How to run a heuristic evaluation

Diagram of 7 steps for how to run a heuristic evaluation: 1. Pick the heuristics; 2. Train the team; 3. Narrow the scope; 4. Evaluate independently; 5. Note each issue against a heuristic; 6. Merge findings; 7. Rate severity.
How to run a heuristic evaluation
  1. Pick the heuristics — Nielsen's 10 for usability; add domain ones if you need them.
  2. Train the team — everyone reads the heuristics; do a practice round on a simple app.
  3. Narrow the scope — one task, one section, one user group or one device.
  4. Evaluate independently — 1–2 hours each; first pass to learn, second to find issues.
  5. Note each issue against a heuristic — with a screenshot and a possible fix.
  6. Merge findings — affinity-map duplicates, discuss disagreements.
  7. Rate severity — 0 to 4, then fix from the top.

Nielsen Norman Group stresses that evaluators shouldn't see each other's notes until they finish: the point of several reviewers is independent observations.

Rating severity

Nielsen's 1994 severity scale combines how often a problem happens, how hard it is to overcome and whether it keeps bothering users:

RatingMeaning
0Not a usability problem
1Cosmetic: fix if there's time
2Minor: low priority
3Major: high priority
4Catastrophe: fix before release

Table: Severity ratings for usability problems (Jakob Nielsen, Nielsen Norman Group, 1994)

Mistakes

Checklist: Mistakes — One evaluator; Treating every violation as a bug; Scope too wide; No severity; Skipping real users.
Mistakes
  • One evaluator — everyone misses things; use three to five
  • Treating every violation as a bug — NN/g's example: hamburger menus violate #6 but often make sense on mobile
  • Scope too wide — a whole product in an hour finds only the obvious
  • No severity — a flat list rarely gets fixed
  • Skipping real users — heuristics find likely issues; testing confirms them
Science of Apps product investigation page with the headline Product intelligence that shows its work
The Science of Apps product investigation: heuristics, accessibility and behaviour, with evidence.Image: Science of Apps · © Science of Apps · source

Ready for a second pair of eyes?

How we know

The method, evaluator numbers and timings come from Nielsen Norman Group's "How to Conduct a Heuristic Evaluation" (2023); the heuristics from Jakob Nielsen's article on NN/g; the severity scale from Nielsen's 1994 article; all read on 17 November 2026. The startup examples are our own illustrations.

Key terms, defined

  • Heuristic: a broad rule of thumb for usable design.
  • Heuristic evaluation: judging an interface against heuristics.
  • Evaluator: a person reviewing the interface.
  • Severity rating: a 0–4 score for how serious a problem is.
  • Affinity diagram: grouping similar findings to merge them.

Frequently asked questions

What is a heuristic evaluation?

A method for finding usability problems by judging an interface against a set of guidelines called heuristics, usually Jakob Nielsen's 10 usability heuristics. Evaluators review the product themselves rather than watching users.

What are Nielsen's 10 usability heuristics?

Visibility of system status; match between the system and the real world; user control and freedom; consistency and standards; error prevention; recognition rather than recall; flexibility and efficiency of use; aesthetic and minimalist design; help users recognize, diagnose and recover from errors; and help and documentation.

How many evaluators do you need?

Nielsen Norman Group recommends three to five people evaluating the same interface independently, because any single evaluator, however experienced, misses some problems.

How long does a heuristic evaluation take?

Nielsen Norman Group suggests timeboxing each evaluator's session to about one to two hours, then a team session to merge and prioritise findings.

Is a heuristic evaluation the same as a UX audit?

It's usually one part of a UX audit. A full audit also adds accessibility checks against WCAG, speed measurements, analytics and the whole user journey.

Can a heuristic evaluation replace user testing?

No. Nielsen Norman Group says it can't replace user research, because UX is contextual. It's a cheap way to find glaring problems and decide what to test.

Sources

  1. Nielsen Norman Group — How to Conduct a Heuristic Evaluation (Kate Moran, Kelley Gordon, 2023)
  2. Nielsen Norman Group — 10 Usability Heuristics for User Interface Design (Jakob Nielsen)
  3. Nielsen Norman Group — Severity Ratings for Usability Problems (Jakob Nielsen, 1994)
  4. W3C — Web Content Accessibility Guidelines (WCAG) 2.2
  5. Science of Apps — Product investigation
  6. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

List free on the Launchpad and, once live, get a free report on your landing page, discoverability and speed; paid reports review every screen against the Laws of UX.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition