- Defining a brand's design philosophy or a product team's long-term values.
- Auditing a physical product, hardware UI, or packaging — anything where craft, restraint, and longevity matter as much as task completion.
- You need a vocabulary for restraint — when a stakeholder wants "more," Rams gives you the language to push back.
- Reviewing a premium product where feeling cheap is the worst failure mode, not being unusable.
Side-by-side comparison
Dieter Rams' 10 vs Norman's 6: side-by-side comparison
Dieter Rams asks whether a designed object is good — honest, restrained, durable, made with care. Don Norman asks whether the user can actually understand it — what is visible, what affords action, what gives feedback. Same word "principles," two different questions, and about four of the sixteen rules genuinely overlap.
Dieter Rams197610 principlesProduct, industrial, and visual design
Don Norman19886 heuristicsCognitive friction in physical and digital products
See it in action
Run Rams and Norman against a live URL in one workflow.
Click anywhere on a real page, drop a heurio, pick the rule it violates — Dieter Rams' 10 or Norman's 6. No screenshots, no Loom, no separate doc.
The story
Two foundational design lists, twelve years apart.
Dieter Rams formalized his ten principles of good design in the 1970s while running industrial design at Braun, and the list has been maintained ever since by Vitsœ, the furniture company he has designed for since 1959. Don Norman, the cognitive scientist who coined the term "user experience" in the early 1990s, published his six principles of design in 1988 in The Design of Everyday Things, drawing on cognitive science and decades of research into why people misuse otherwise well-engineered objects. Two foundational lists, twelve years apart, written from opposite ends of the design process.
UX teams cite the two interchangeably because both are short, both are memorable, and both are taught in the first week of any design programme. But they answer different questions. Rams asks whether the object is good — honest, restrained, useful, durable, made with care. Norman asks whether the user understands the object — what is visible, what affords what, how the controls map to the effects, where the feedback is. One is a values system; the other is a diagnostic tool.
This page maps the two lists against each other, calls out where they actually overlap (less than people assume), and explains which one to reach for in which review.
At a glance
Dieter Rams' 10 vs Norman's 6 — the side-by-side facts.
| Dimension | Dieter Rams' 10 | Norman's 6 |
|---|---|---|
| Author | Dieter Rams | Don Norman |
| Year published | 1976 | 1988 |
| Origin | Braun / industrial design | The Design of Everyday Things |
| Scope | Product, industrial, and visual design | Cognitive friction in physical and digital products |
| Number of rules | 10 | 6 |
| In one line | Ten principles for what makes any designed object good — written by an industrial designer for makers of physical products. | 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 user keeps doing the wrong thing on a screen and you can't articulate why.
- Auditing a novel interface — dashboard, configurator, complex form — where users build a mental model from scratch.
- You suspect the problem is affordance, mapping, or missing feedback, not aesthetics or copy.
- Onboarding a junior designer who needs a diagnostic vocabulary for everyday usability problems.
Reviewing a premium digital product where understanding and craft both matter — high-end SaaS, design tools, premium e-commerce. Run Norman first to find the cognitive friction, then Rams to find the violations of restraint and craft that make the same screens feel cheap.
Principle map
Twenty principles. Nine themes. See where they meet — and where they don't.
Each theme groups the rules from Dieter Rams' 10 and Norman's 6 that address the same idea — including the rows where one framework has nothing to say.
Visibility & comprehension
2 rules · 1 / 1
Dieter Rams' 10
#4Good design makes a product understandable
Norman's 6
#1Visibility
Both insist the user grasp the product immediately. Rams #4 ("makes a product understandable") works through the product's own form; Norman #1 (visibility) works through which controls and states are surfaced. Same goal, two paths to it.
Honesty & feedback
2 rules · 1 / 1
Dieter Rams' 10
#6Good design is honest
Norman's 6
#2Feedback
Rams #6 demands the product not overstate its capabilities; Norman #2 demands the system signal the result of every action. Both treat deception — implicit or explicit — as a failure of integrity.
Consistency
2 rules · 1 / 1
Dieter Rams' 10
#4Good design makes a product understandable
Norman's 6
#6Consistency
Norman promotes consistency to a top-level principle: similar tasks should be done in similar ways. Rams treats it as part of understandability — the product's structure should match what it does — but never names it on its own.
Affordance & action possibilities
1 rule · 0 / 1
Dieter Rams' 10
—
Norman's 6
#3Affordance
Norman-only. Affordance — what an object signals about how it can be used — is Norman's distinctive contribution. Rams assumes form follows function but never isolates the cue layer that tells the user "I can be pressed, pulled, or dragged."
Mapping & natural correspondence
1 rule · 0 / 1
Dieter Rams' 10
—
Norman's 6
#4Mapping
Norman-only. The arrangement of a control should mirror the arrangement of its effect — stovetop knobs over burners, volume sliders going up to mean louder. Rams assumes good industrial form handles this implicitly.
Constraints & error prevention
1 rule · 0 / 1
Dieter Rams' 10
—
Norman's 6
#5Constraints
Norman-only. Constraints — disabled buttons, input masks, date pickers, step-gated wizards — limit possible actions to prevent invalid states. Rams's principles do not address error-state design; he assumes a well-formed product avoids invalid use through structure, not interaction guards.
Aesthetic restraint
3 rules · 3 / 0
Dieter Rams' 10
#3Good design is aesthetic#5Good design is unobtrusive#10Good design is as little design as possible
Norman's 6
—
Rams-only. Three of his ten rules — aesthetic quality (#3), unobtrusive (#5), and as little design as possible (#10) — codify restraint. Norman is silent on visual restraint: an ugly product that the user understands still passes Norman's six.
Detail craftsmanship
1 rule · 1 / 0
Dieter Rams' 10
#8Good design is thorough down to the last detail
Norman's 6
—
Rams-only. "Thorough down to the last detail" (#8) elevates micro-craft to a top-level concern. Norman's principles can be satisfied by a product whose details are sloppy as long as the cognitive bridge is intact.
Longevity & environmental responsibility
2 rules · 2 / 0
Dieter Rams' 10
#7Good design is long-lasting#9Good design is environmentally friendly
Norman's 6
—
Rams-only. Long-lasting (#7) and environmentally friendly (#9) are absent from Norman — his six were written about the cognitive bridge between user and object, not about the object's lifespan or its materials.
Innovation & forward motion
1 rule · 1 / 0
Dieter Rams' 10
#1Good design is innovative
Norman's 6
—
Rams-only. Rams demands the design move its category forward (#1). Norman's principles are diagnostic — they audit the cognitive friction of any existing or proposed design but do not require novelty.
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
What each list is for
Norman's six are a diagnostic tool — when a user struggles, you trace the friction back to visibility, feedback, affordance, mapping, constraints, or consistency. Rams's ten are a values system — they tell you whether the product is worth building at all. Diagnosis versus judgment.
02 · Difference
Cognitive vs aesthetic axis
Norman concentrates on the cognitive bridge: how the user forms an intention, executes it, and interprets the result. Rams concentrates on the object's character: its honesty, restraint, durability, and craft. A product can pass Norman and fail Rams (clunky but learnable) or pass Rams and fail Norman (beautiful but baffling).
03 · Difference
Treatment of error states
Norman has explicit principles for affordance, mapping, and constraints — the three levers that prevent users from doing the wrong thing in the first place. Rams's principles predate interactive software and assume invalid use is handled by the object's form, not by an interaction guard.
04 · Difference
Translatability to UI fixes
Every Norman violation maps to a concrete UI change — add a hover state, make the disabled button look disabled, fix the slider direction, surface the system response. Rams violations are higher-level: "this product is not honest" rarely yields a single component change and usually demands a redesign or a strategy conversation.
05 · Difference
Time horizon
Norman evaluates the current interaction: is the flow understandable today? Rams evaluates the object across years and generations: will this product still feel good in a decade? A Norman audit asks whether the design works on Tuesday; a Rams audit asks whether it deserves to still exist in 2036.
From theory to review
Pin findings on a live page and tag them with Dieter Rams' 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
Pick by the kind of friction you're trying to surface.
Use Dieter Rams' 10
Drafting a design manifesto for a new product team
Rams's principles read as a one-page philosophy — restraint, longevity, honesty, craft. They give a team shared values, not a diagnostic checklist.
Auditing a physical product, hardware UI, or packaging
Longevity, environmental responsibility, and detail craftsmanship are Rams-native concerns. Norman covers cognitive usability but is silent on whether the object itself deserves to exist.
Use Norman's 6
Onboarding flow where users drop off at step two
Almost always a visibility, affordance, or feedback problem. Norman's principles name the failure mode precisely; Rams's principles are too abstract to localize the fix.
Auditing a complex dashboard for first-time users
Mapping and visibility do most of the work in dashboards — which control affects which chart, what state am I in, what just happened. Norman's diagnostic frame fits this exactly.
Reviewing a control-heavy interface — settings, configurators, admin panels
Affordance, mapping, and constraints carry the experience. Norman's six map directly to those interaction primitives; Rams's principles don't reach this level of detail.
Use both
Reviewing a premium SaaS product or design tool
Norman catches the moments where the interface is hard to understand; Rams catches the moments where it works fine but feels cheap. Both axes matter when the brand promises premium.
Where they overlap
Common ground — about a fifth of the rules.
Both reject "the user will figure it out"
Rams's understandability (#4) and Norman's visibility (#1) and consistency (#6) all refuse to accept hidden, arbitrary, or counterintuitive behaviour. If a competent user has to guess, the design failed — both lists agree, even though Rams blames the object and Norman blames the cognitive bridge.
Both treat dishonest signalling as a top sin
Rams's honesty (#6) and Norman's feedback (#2) attack the same failure from opposite ends. Rams forbids the product from overstating its capabilities; Norman demands the system tell the user exactly what just happened. Either way, the user must not be left guessing.
Both are short enough to memorize
Ten principles and six principles are deliberately small enough that a single reviewer can hold them in their head while walking through a product. That structural similarity is part of why teams treat the lists as interchangeable — even when they aren't.
Both apply across physical and digital products
Rams wrote for industrial design but his rules are quoted by software teams every day. Norman wrote about doors, switches, and stovetops but his principles are now standard reading for digital product designers. Both transcend their original medium — which is why they keep getting compared.
Sources
- What is Heuristic Evaluation?wikipedia.org
- Dieter Rams: 10 Timeless Commandments for Good Designinteraction-design.org
- About Dieter Ramswikipedia.org
- The Design of Everyday Things — Don Normanwikipedia.org
- About Don Normannngroup.com
Frequently asked
Common questions about Rams and Norman.
Bottom line
Diagnose with Norman, judge with Rams — when to do which.
Use both — but use them for different things. Norman's six principles tell you why a user is confused and what to change on the screen. Rams's ten principles tell you whether the product deserves to exist in its current form. One is a diagnostic tool, the other is a values check, and a serious review of a premium product needs both. Heurio is a UX review tool that supports running both Dieter Rams's principles 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
Adjacent guidelines and other side-by-side comparisons
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.
