Consistency and Standards
The same thing should look and behave the same way everywhere, and follow platform convention where one exists.
Definition
Nielsen's fourth heuristic. Users should not have to wonder whether different words, situations or actions mean the same thing. Consistency operates internally, within your product, and externally, against platform and industry conventions.
Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.
On this plate
Reach for this when
- Building or auditing a design system.
- Reviewing terminology across surfaces.
- Deciding whether a one-off deviation is justified.
- Two teams have solved the same interaction differently and both solutions are defensible.
Common mistakes
- Uniformity applied without regard to context.
- Consistent visuals with inconsistent behaviour.
- Undocumented exceptions that become precedents.
Four kinds of consistency, in rough order of importance
- 1.Functional: the same control does the same thing everywhere. Breaking this is the most damaging.
- 2.Internal visual: the same meaning gets the same treatment across your product.
- 3.External: your product matches platform and category conventions.
- 4.Aesthetic: the product looks like itself. The cheapest to fix and the least costly to break.
Do
- Encode consistency in tokens and components so it is the path of least resistance.
- Keep one name per concept across UI, docs, support and email.
- Follow platform conventions for platform behaviours: back, share, date pickers, keyboard shortcuts.
- Document the intentional inconsistencies and the reasons for them.
Do not
- Ship three button styles that mean the same thing.
- Vary terminology between the interface and the help article.
- Enforce identical density across genuinely different contexts.
- Treat a component library as consistency. It is a mechanism for consistency, not a guarantee of it.
Where inconsistency actually costs
Not all inconsistency is equal. This is roughly the order in which it hurts.
| Inconsistency | What it costs |
|---|---|
| The same word meaning two things | Permanent confusion, and support tickets that start from the wrong premise |
| The same control behaving differently | Lost trust in the control, and slower use everywhere it appears |
| Different words for one thing | Failed search, and readers who believe there are two features |
| Visual drift between areas | A product that feels unowned, and a slow accumulation of maintenance |
| Departure from platform convention | A learning cost paid once per user, which is sometimes worth paying |
In practice
- i.
One name per concept
Product vocabularyA product using 'workspace', 'team' and 'organisation' for the same object across UI, billing and docs generated confusion at every support touchpoint. Standardising on one word was a content change with a measurable support impact.
- ii.
Justified inconsistency
Design systemsDestructive buttons deliberately break the primary button style. That is consistency of meaning, and it is more useful than consistency of appearance.
- iii.
Two buttons, one label, different outcomes
Behavioural inconsistencySave on one screen committed immediately and on another queued for approval. Both were correct in their own context, and together they meant nobody could trust what Save did.
Commonly confused with
Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.
Jakob's Law
LawReaders arrive with expectations built from every other product they use.
Key difference
Consistency is internal: the same thing behaves the same way across your product. Jakob's Law is external: your product should behave the way the rest of the web already does. A product can be perfectly consistent with itself and still surprise everyone who arrives.
Use Consistency and Standards when
- Two screens solve the same problem differently.
- The vocabulary drifts between areas or teams.
- The fix is a shared component, token or term.
Use Jakob's Law when
- You are considering a novel take on a familiar control.
- The question is whether to follow a platform or web convention.
- The cost of the difference lands on first-time users.
Local chart
HEUR·004 · Region I · Grid A2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
10 Usability Heuristics for User Interface Design
J. Nielsen, Nielsen Norman Group, 1994, revised 2020
- [2]
Consistency in Design is the Wrong Approach
J. Spool, UIE
Argues for consistency of user expectation over surface uniformity.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Why this works
The reasoning this entry rests on.
- Status Quo BiasBIAS·005 · Cognitive bias
- Mental ModelsMOD·001 · Mental model
- Mere Exposure EffectPSY·009 · Psychology
Applied through
Where this shows up as a concrete interface decision.
- ButtonCMP·001 · Component
- Component API DesignSYS·002 · Design system
- Design System GovernanceSYS·004 · Design system
- Design TokensSYS·001 · Design system
- Heuristic EvaluationRES·002 · Research method
- RepetitionFND·010 · UI foundation
- SimilarityFND·005 · UI foundation
- Voice and ToneWRT·003 · UX writing
Short definition
The one-paragraph version, for when that is all you need.
- Design DebtTERM·098 · Term
- Single Source of TruthTERM·087 · Term
Related concept
Connected closely enough to change how you apply this.
- Match Between System and the Real WorldHEUR·002 · Heuristic
- Power Law of PracticeLAW·015 · Law