- Running a heuristic evaluation on a near-final release to identify specific usability problems.
- You need broad coverage — help systems, real-world language, error recovery — beyond the cognitive bridge.
- Every finding must map to a fixable interaction: a missing confirmation, an unclear label, a broken back button.
- Onboarding a UX team on the industry-default audit checklist every UX practitioner knows by name.
Side-by-side comparison
Nielsen's 10 vs Norman's 6: side-by-side comparison
Nielsen's ten heuristics audit interactive systems for usability problems; Norman's six principles diagnose the cognitive friction that creates those problems. Both lists cover the same domain — software products people interact with — but from different vantage points. About five of the sixteen rules cover identical ground.
Jakob Nielsen199410 principlesSoftware and web product UX
Don Norman19886 heuristicsCognitive friction in physical and digital products
See it in action
Audit with Nielsen, diagnose with Norman — on the same screen.
Click anywhere on a real page, drop a heurio, pick the rule it violates — Nielsen's 10 or Norman's 6. No screenshots, no Loom, no separate doc.
The story
Two interactive-design lists, six years apart.
Jakob Nielsen published his ten usability heuristics in 1994 while at Sun Microsystems, refined from a 1990 paper with Rolf Molich. Don Norman published his six principles of design in 1988 in The Design of Everyday Things, drawing on his earlier cognitive-engineering work at UC San Diego. The two lists are often quoted in the same breath because both apply to digital interfaces and both are short enough to memorize — but they were developed independently, from different intellectual traditions.
Teams often conflate the two. People assume Norman's principles are Nielsen's heuristics by another name. They are not. Nielsen's heuristics describe what a usable interactive system looks like — written for an evaluator reviewing a release. Norman's principles describe how people perceive, plan, and execute action — written for a designer trying to understand why users fail. Audit checklist versus cognitive diagnostic.
This page maps the two lists row by row, names the five themes that genuinely overlap (visibility, feedback, consistency, error prevention, recognition), and explains which list answers which question in practice.
At a glance
Nielsen's 10 vs Norman's 6 — the side-by-side facts.
| Dimension | Nielsen's 10 | Norman's 6 |
|---|---|---|
| Author | Jakob Nielsen | Don Norman |
| Year published | 1994 | 1988 |
| Origin | Sun Microsystems / usability research | The Design of Everyday Things |
| Scope | Software and web product UX | Cognitive friction in physical and digital products |
| Number of rules | 10 | 6 |
| In one line | The default ten-rule checklist for evaluating digital interfaces — written by a usability researcher for usability practitioners. | Six cognitive principles that explain why people understand — or fail to understand — any designed object, from doors to dashboards. |
Quick verdict
The 30-second answer.
- A specific user behaviour is confusing the team and you need vocabulary — affordance, mapping, missing feedback — to explain why.
- Designing or reviewing a novel interface — dashboard, configurator, control panel — where mapping is non-obvious.
- Teaching the cognitive science behind usability problems, not just the symptoms.
- Working on a control-heavy interface where affordance signals and mapping logic carry most of the experience.
Reviewing a digital product where surface usability and deeper cognitive friction both matter. Walk the screens with Nielsen's checklist to catch the standard usability bugs, then walk the same screens with Norman's six principles to diagnose the harder-to-name issues — why this dashboard "feels off" even when every Nielsen rule technically passes.
Principle map
Twenty principles. Nine themes. See where they meet — and where they don't.
Each theme groups the rules from Nielsen's 10 and Norman's 6 that address the same idea — including the rows where one framework has nothing to say.
Visibility, system status & recognition
3 rules · 2 / 1
Nielsen's 10
#1Visibility of system status#6Recognition rather than recall
Norman's 6
#1Visibility
Both lists demand the system show — not hide — its state, options, and pending actions. Nielsen splits this into visibility of system status (#1) and recognition over recall (#6). Norman folds both into one principle: visibility.
Feedback
2 rules · 1 / 1
Nielsen's 10
#1Visibility of system status
Norman's 6
#2Feedback
Norman makes feedback its own principle because the action → result loop is what builds the user's mental model. Nielsen rolls feedback into visibility of system status — different framings, near-identical requirements.
Consistency
2 rules · 1 / 1
Nielsen's 10
#4Consistency and standards
Norman's 6
#6Consistency
Identical premise. Nielsen frames it as conformance to platform conventions and internal standards; Norman frames it as conformance to the user's learned mental model. Both forbid arbitrary variation.
Error prevention & constraints
2 rules · 1 / 1
Nielsen's 10
#5Error prevention
Norman's 6
#5Constraints
Nielsen demands the interface prevent errors before they happen. Norman names the mechanism — constraints, like disabled buttons, input masks, and step-gated wizards — that limit possible actions to valid ones.
Affordance
1 rule · 0 / 1
Nielsen's 10
—
Norman's 6
#3Affordance
Norman-only. Affordance — the cue that signals what an element can do — is Norman's distinctive contribution to design vocabulary. Nielsen never names it; his heuristics assume it is handled inside consistency and standards.
Mapping
1 rule · 0 / 1
Nielsen's 10
—
Norman's 6
#4Mapping
Norman-only. Whether a control's arrangement mirrors its effect — a volume slider going up to mean louder, knob arrangement matching burner arrangement — has no Nielsen equivalent.
Match with real-world language
1 rule · 1 / 0
Nielsen's 10
#2Match between system and the real world
Norman's 6
—
Nielsen-only. Norman assumes appropriate vocabulary is handled as part of consistency. Nielsen elevates it to its own heuristic because mismatched language — system jargon, technical labels, unclear icons — breaks every other rule downstream.
User control & error recovery
2 rules · 2 / 0
Nielsen's 10
#3User control and freedom#9Help users recognize, diagnose, and recover from errors
Norman's 6
—
Nielsen-only. Undo, emergency exits, and recovery messages — "help users recognize, diagnose, and recover from errors" — are not part of Norman's six. Norman's constraints prevent errors; Nielsen handles what happens once one occurs anyway.
Flexibility, restraint & help
3 rules · 3 / 0
Nielsen's 10
#7Flexibility and efficiency of use#8Aesthetic and minimalist design#10Help and documentation
Norman's 6
—
Nielsen-only. Three rules — flexibility for novices and experts (#7), aesthetic and minimalist design (#8), and help and documentation (#10) — have no analogue in Norman's principles. They cover ergonomic, editorial, and support concerns Norman's cognitive frame deliberately does not reach.
Key differences
Five things that actually separate them.
Both lists have ten items. Both read like commandments. Here is what's actually different once you start using them.
01 · Difference
Independent works, often conflated
Nielsen's heuristics (1994, refined from a 1990 paper with Rolf Molich) and Norman's principles (1988, in The Design of Everyday Things) were developed independently from different intellectual traditions — usability engineering for Nielsen, cognitive science for Norman. Teams treat them as one unified theory because both apply to digital interfaces; they are actually two distinct frameworks with different vantage points.
02 · Difference
What each list audits
Nielsen's heuristics audit the interaction — does the user accomplish the task, see the system's state, recover from errors, find help? Norman's principles audit the cognitive bridge — does the user form a correct mental model of what the interface does and how to act on it?
03 · Difference
Coverage breadth
Nielsen's ten cover more axes — real-world language, flexibility for experts, aesthetic restraint, error recovery, and help systems. Norman's six concentrate on the cognitive layer (visibility, feedback, affordance, mapping, constraints, consistency). Each list owns territory the other does not address.
04 · Difference
Cognitive specificity
Norman owns affordance and mapping — the two concepts UX teams quote when explaining why a control is or isn't intuitive. Nielsen's heuristics never name these primitives explicitly; he embeds them under consistency and visibility, leaving the cognitive vocabulary to Norman.
05 · Difference
Application timing
Nielsen's heuristics are written for an evaluator walking through a near-final interface — every rule maps to something visible on screen. Norman's principles are written for a designer thinking about user behaviour — every principle maps to a cognitive step in the user's flow.
From theory to review
Pin findings on a live page and tag them with Nielsen's 10 or Norman's 6.
Click anywhere on a real URL, drop a heurio, pick the rule it violates, and share the board. No screenshots, no Loom, no separate doc.
When to reach for which
Use the list that fits the question you're trying to answer.
Use Nielsen's 10
Heuristic evaluation of a finished release
Every finding needs to map to a fixable interaction. Nielsen's wording — "visibility of system status," "help with errors" — translates one-to-one into Jira tickets. Norman's principles are more diagnostic than prescriptive.
Communicating UX issues to engineers
Nielsen's heuristics map directly to UI primitives (labels, confirmations, error states). Engineers can reproduce and fix every violation. Norman's principles often require a design conversation before they yield a code change.
Onboarding a new UX hire
Nielsen's ten is the industry-default checklist; learning it gives new hires a shared vocabulary with the rest of the UX community on day one.
Use Norman's 6
Onboarding flow with high step-two drop-off
Almost always a visibility, affordance, or feedback problem. Norman's principles name the failure mode precisely; Nielsen's heuristics describe the surface symptom but not the cognitive root cause.
Reviewing a control-heavy interface
Mapping and affordance carry the experience in configurators, admin panels, and dashboards. Norman's six map directly to those interaction primitives; Nielsen's heuristics treat them as part of consistency.
Use both
Premium SaaS or design tool review
Nielsen catches the standard usability bugs; Norman catches the harder-to-name moments where the interface technically passes every heuristic but still feels confusing. Both axes matter when the product promises premium.
Where they overlap
Common ground — about a fifth of the rules.
Both demand visible system state
Nielsen's "visibility of system status" (#1) and Norman's "visibility" (#1) describe the same requirement: the user must always see what the system is doing, what options are available, and what the current state is. Nothing important should be hidden.
Both treat consistency as foundational
Nielsen's "consistency and standards" (#4) and Norman's "consistency" (#6) are functionally identical. Both make consistency a top-line rule because inconsistency forces the user to relearn the interface for every screen.
Both prevent errors through structure
Nielsen's "error prevention" (#5) and Norman's "constraints" (#5) describe the same fix from different ends. Nielsen names the goal — fewer errors — while Norman names the mechanism: limit possible actions to valid ones via disabled controls, masks, and step gates.
Both share an audit vantage point
Unlike Shneiderman's golden rules (written for designers building new systems), both Nielsen's heuristics and Norman's principles work as a walk-through of an existing interface. They identify what is wrong, not what to build from scratch.
Sources
- What is Heuristic Evaluation?wikipedia.org
- 10 Usability Heuristics for User Interface Designnngroup.com
- About Jakob Nielsennngroup.com
- The Design of Everyday Things — Don Normanwikipedia.org
- About Don Normannngroup.com
Frequently asked
Frequent questions about Nielsen, Norman, and how they relate.
Bottom line
Nielsen's heuristics, Norman's principles, or both?
Use both — for different things. Nielsen's ten heuristics are the industry-default audit checklist: they tell you what is wrong on screen and how to ticket it. Norman's six principles are the cognitive-diagnostic lens: they tell you why the user is failing even when nothing on screen is technically broken. The two frameworks share a brand and share a few core ideas — visibility, feedback, consistency, constraints — but they cover different territory, and the bulk of each list has no analogue in the other. Any serious UX review benefits from running both lists across the same screens. Heurio is a UX review tool that supports running both Nielsen's heuristics and Don Norman's principles against any live website in a single evaluation — pin findings to the page, tag each by the violated rule, and share the report with your team.
Keep exploring
More on heuristic evaluation and design principles
Silvia Martínez
Product Designer
Heurio is the tool we needed in our digital product team for a long time.
It has definitely improved the workflow between designers and the dev team. Now it is easier to make corrections on the web interface and follow its deployment.
Amber Sewell
Sr. Product Designer
Heurio is a real time-saver and helped a lot in breaking down a heuristic evaluation in an efficient way.
I've shared this with my team to boost understanding of UX and why a problem is a problem, share it with team members remotely, and also for QAing new feature rollout. The export feature is great to send a more formal report out to the team. Well designed tool overall as well.
