- Defining your team's design philosophy — what the product should be, not how it should behave.
- Auditing a physical product or hardware UI where the object's character matters.
- Pushing back on feature creep — Rams's restraint gives you vocabulary against "more."
- Reviewing the brand impression of a premium digital product, where feeling cheap is the worst failure mode.
Side-by-side comparison
Dieter Rams' 10 vs Tognazzini's 18: side-by-side comparison
Bruce Tognazzini's 18 first principles spell out the specific interaction mechanics every web product should get right — anticipation, defaults, latency, state preservation, Fitts's Law. Dieter Rams's 10 principles ask the higher question of whether the product the interaction serves is worth building at all: honest, restrained, durable, made with care. Two lists at completely different altitudes, with about four of the twenty-eight rules genuinely overlapping.
Dieter Rams197610 principlesProduct, industrial, and visual design
Bruce Tognazzini200318 heuristicsInteractive software and web application mechanics
See it in action
Run both lists across a real product in one workflow.
Click anywhere on a real page, drop a heurio, pick the rule it violates — Dieter Rams' 10 or Tognazzini's 18. No screenshots, no Loom, no separate doc.
The story
Ten values and eighteen mechanics, decades apart.
Bruce "Tog" Tognazzini wrote Apple's first Human Interface Guidelines in 1978 while leading the company's Human Interface evangelist programme, then refined his First Principles of Interaction Design across decades on AskTog and in two books — Tog on Interface (1992) and Tog on Software Design (1996). Dieter Rams, working a decade earlier as head of industrial design at Braun, formalized his ten principles of good design in the 1970s, and the canonical list has been maintained by Vitsœ ever since. Two design lists from two completely different industries.
The two lists are short, memorable, and cited by UX teams every day, but they operate at completely different altitudes. Rams asks whether a designed object is good — honest, restrained, useful, durable, made with care. Tognazzini asks whether every specific interaction detail is right — does the system anticipate the user's next need, does it reduce latency where it can, does it protect the user's work, does it use Fitts's Law for important targets? Ten values versus eighteen mechanics.
This page maps the two lists against each other, calls out where they actually overlap (about four of the twenty-eight rules — consistency, simplicity, honesty, and craft), and explains which list to reach for in which kind of review.
At a glance
Dieter Rams' 10 vs Tognazzini's 18 — the side-by-side facts.
| Dimension | Dieter Rams' 10 | Tognazzini's 18 |
|---|---|---|
| Author | Dieter Rams | Bruce Tognazzini |
| Year published | 1976 | 2003 |
| Origin | Braun / industrial design | Apple Human Interface Group / AskTog |
| Scope | Product, industrial, and visual design | Interactive software and web application mechanics |
| Number of rules | 10 | 18 |
| In one line | Ten principles for what makes any designed object good — written by an industrial designer for makers of physical products. | Eighteen principles for the mechanics of usable software — anticipation, defaults, latency, state, Fitts's Law — written by Apple's first Human Interface evangelist. |
Quick verdict
The 30-second answer.
- Auditing a content-heavy web app, dashboard, or admin console for specific interaction problems.
- You suspect issues like slow latency, lost state, broken back-navigation, mis-sized targets, or non-discoverable features.
- Reviewing a settings panel, form, or configurator for the small mechanics that wreck otherwise good design.
- Looking for a more comprehensive checklist than Nielsen's ten — Tognazzini's eighteen covers more interaction territory.
Reviewing a premium digital product end-to-end. Rams's principles ask whether the product as a whole deserves to exist; Tognazzini's first principles ask whether every interaction detail is nailed. The two lists work at completely different altitudes and together cover both the philosophy and the mechanics.
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 Tognazzini's 18 that address the same idea — including the rows where one framework has nothing to say.
Consistency
2 rules · 1 / 1
Dieter Rams' 10
#4Good design makes a product understandable
Tognazzini's 18
#4Consistency
Both make consistency a top-line rule. Rams frames it as the product's form revealing what it does ("understandable"). Tognazzini specifies the standard: identical interactions should look and behave identically across screens, with platform standards as the baseline.
Simplicity & restraint
4 rules · 3 / 1
Dieter Rams' 10
#3Good design is aesthetic#5Good design is unobtrusive#10Good design is as little design as possible
Tognazzini's 18
#16Simplicity
Rams treats restraint as three separate principles — aesthetic quality (#3), unobtrusive (#5), and as little design as possible (#10). Tognazzini compresses this into one operational rule: "as simple as possible, but no simpler." Same value, different granularity.
Honesty & discoverability
2 rules · 1 / 1
Dieter Rams' 10
#6Good design is honest
Tognazzini's 18
#6Discoverability
Rams demands the product not overstate its capabilities (#6 honest). Tognazzini demands features be findable without documentation (#6 discoverability). Both treat hidden behaviour as a failure of integrity — different scopes, same root.
Detail craftsmanship
5 rules · 1 / 4
Dieter Rams' 10
#8Good design is thorough down to the last detail
Tognazzini's 18
#3Color#5Defaults#11Latency Reduction#14Protect Users' Work
Rams elevates "thorough down to the last detail" (#8) to a top-level principle. Tognazzini names which details matter: color used as more than a single channel (#3), sensible defaults (#5), reduced latency (#11), and protected user work (#14). Rams's principle, Tognazzini's specifics.
Innovation & forward motion
1 rule · 1 / 0
Dieter Rams' 10
#1Good design is innovative
Tognazzini's 18
—
Rams-only. Rams demands the design move its category forward (#1). Tognazzini's first principles audit how an existing interface behaves; they do not require novelty from the product itself.
Longevity & environmental responsibility
2 rules · 2 / 0
Dieter Rams' 10
#7Good design is long-lasting#9Good design is environmentally friendly
Tognazzini's 18
—
Rams-only. Long-lasting (#7) and environmentally friendly (#9) are industrial-design concerns. Tognazzini's first principles apply to digital interfaces and do not address the object's lifespan or material cost.
Interaction physics — time and space
2 rules · 0 / 2
Dieter Rams' 10
—
Tognazzini's 18
#9Fitts's Law#11Latency Reduction
Tognazzini-only. Fitts's Law (#9, target acquisition time as a function of distance and size) and Latency Reduction (#11, 100ms feels instant, a one-second wait without feedback feels broken) describe the physics of interaction. Rams's principles predate the screen-based vocabulary entirely.
State, navigation & exploration
3 rules · 0 / 3
Dieter Rams' 10
—
Tognazzini's 18
#8Explorable Interfaces#17Track State#18Visible Navigation
Tognazzini-only. Track State (#17), Visible Navigation (#18), and Explorable Interfaces (#8) describe how a multi-screen interactive product holds together. Rams's principles assume the product is a single object; the concept of navigating between screens does not apply.
User autonomy & efficiency
3 rules · 0 / 3
Dieter Rams' 10
—
Tognazzini's 18
#1Anticipation#2Autonomy#7Efficiency of the User
Tognazzini-only. Anticipation (#1), Autonomy (#2), and Efficiency of the User (#7) put the user in control of an interactive system. Rams's principles treat the product as inert; there is no equivalent vocabulary for an active user negotiating with the system.
Readability & accessibility primitives
2 rules · 0 / 2
Dieter Rams' 10
—
Tognazzini's 18
#3Color#15Readability
Tognazzini-only. Color (#3, never the only carrier of information) and Readability (#15, real conditions: small screens, bright sunlight, tired eyes) explicitly cover accessibility primitives. Rams's principles predate the modern accessibility framing.
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
Altitude of the question
Rams operates at the altitude of "is this product good?" — values like honesty, restraint, and longevity. Tognazzini operates at the altitude of "is this interaction right?" — mechanics like latency, defaults, Fitts's Law, and state preservation. Different altitudes, different work.
02 · Difference
Where the overlap actually sits
Roughly four of the twenty-eight rules map cleanly across — consistency, simplicity/restraint, honesty/discoverability, and detail craftsmanship. The remaining twenty-four are framework-specific: Rams has the entire values axis (innovation, longevity, environmental responsibility), Tognazzini has the entire interaction-mechanics axis (Fitts's Law, latency, state, navigation, defaults).
03 · Difference
List size and scope
Rams's ten are deliberately compact — they fit on a single page and can be memorized in an afternoon. Tognazzini's eighteen are deliberately granular — they cover the specific interaction primitives a comprehensive checklist needs to surface. The size difference is a feature: each list is sized for its purpose.
04 · Difference
Treatment of the user
Tognazzini's principles describe what the user can do, anticipate, undo, restore, and protect — the user is the protagonist of every rule. Rams's principles treat the product as the protagonist; the user is implicit, sometimes invisible. Two completely different vantage points.
05 · Difference
Audit translatability
Every Tognazzini violation translates one-to-one into a fix: increase target size, hide the latency, save the form state, surface the hidden menu. Rams violations rarely yield a single component change — "this product is not honest" usually demands a strategy conversation, not a Jira ticket.
From theory to review
Pin findings on a live page and tag them with Dieter Rams' 10 or Tognazzini's 18.
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
Choose by altitude — values or mechanics.
Use Dieter Rams' 10
Drafting a design philosophy for a new product team
Rams's principles read as a one-page manifesto — restraint, longevity, honesty, craft. They give a team shared values for what the product should be, not how it should behave on screen.
Reviewing the brand impression of a premium digital product
Rams catches the violations of restraint and craft that make a product feel cheap. Tognazzini's mechanics-level rules can all pass while the product still feels overdesigned, dishonest, or generic.
Use Tognazzini's 18
Auditing a content-heavy web app or admin console
Tognazzini's eighteen cover the small mechanics that break large applications — state preservation, visible navigation, latency reduction, defaults. Rams's principles are too abstract to localize the fix.
Reviewing a settings panel, form, or configurator
These screens live or die on Fitts's Law (target size and position), defaults (most users never change them), and protected work (form state survives back-navigation). Tognazzini names them all; Rams names none.
Looking for a more comprehensive UX checklist than Nielsen's ten
Tognazzini's eighteen cover more ground — anticipation, learnability, Fitts's Law, color accessibility, latency. Pair them with Nielsen's ten when surface coverage is the priority.
Use both
End-to-end review of a premium SaaS product
Tognazzini catches the mechanical interaction problems users actually hit; Rams catches the higher-level violations of restraint and integrity. Both axes matter when the product promises premium.
Where they overlap
Common ground — about a fifth of the rules.
Both demand consistency
Rams's understandability (#4) and Tognazzini's consistency (#4) both reject arbitrary variation. The user must be able to transfer their learning across the product — whether the product is a Braun radio or a web admin panel.
Both treat simplicity as a positive force
Rams's "as little design as possible" (#10) and Tognazzini's "simplicity" (#16) arrive at the same conclusion through different roads. Rams reasons from restraint as a value; Tognazzini reasons from cognitive load as a constraint. Same destination.
Both reward visible, honest behaviour
Rams's honesty (#6) and Tognazzini's discoverability (#6) both reject hidden mechanics. Rams forbids the product from misrepresenting itself; Tognazzini forbids the system from hiding what the user needs to find.
Both refuse "more is better"
Tognazzini's defaults rule (#5) and Rams's three restraint rules (#3, #5, #10) both reject the assumption that adding more options or visual texture improves the design. Strip what is not essential.
Sources
- What is Heuristic Evaluation?wikipedia.org
- Dieter Rams: 10 Timeless Commandments for Good Designinteraction-design.org
- About Dieter Ramswikipedia.org
- First Principles of Interaction Design (Revised & Expanded)asktog.com
- First Principles of Interaction Design — NN/gnngroup.com
Frequently asked
Frequent questions about Rams's values and Tognazzini's mechanics.
Bottom line
Values from Rams, mechanics from Tognazzini.
Use both — at different altitudes. Tognazzini's eighteen first principles tell you whether the interaction mechanics are right: does anticipation work, does latency hide, does state survive, does Fitts's Law cover the important targets? Rams's ten principles tell you whether the product the interaction serves is worth the user's time at all: honest, restrained, durable, made with care. Tognazzini operates at the keystroke; Rams operates at the brand. The overlap is small — about four of the twenty-eight rules — and the rest is territory neither list shares. A serious review of a premium digital product benefits from both. Heurio is a UX review tool that supports running both Tognazzini's first principles and Dieter Rams'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.
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.
