Occam’s Razor
When explanations or designs account for the same requirements equally well, prefer the one that depends on fewer unnecessary assumptions.
Direct explanation
What it means
Parsimony is a tie-breaker, not an instruction to make every screen sparse. A simpler design must still explain state, support edge cases, and meet real user goals.
Teams accumulate modes, controls, and architecture to cover imagined cases. Testing sufficiency helps remove accidental complexity without erasing necessary capability.
Research anchor: Elliott Sober
Research and interpretation
What the research found
Occam-associated maxims counsel against multiplying entities or assumptions without necessity.
Parsimony remains a methodological value, but philosophers distinguish syntactic, ontological, explanatory, and pragmatic forms of simplicity.
Popular advice versus careful use
Common shorthand: The interface with the fewest elements is best.
Prefer the least complicated solution that fully satisfies evidence, safety, accessibility, and user-control requirements.
How designers apply it
- 01
Remove a mode when one reversible interaction serves both cases.
- 02
Choose a plain permission explanation over an elaborate metaphor.
- 03
Consolidate duplicate components that share behavior and semantics.
Original UI examples
responsive collaboration
File sharing
One Share action opens people, link, and access scope in a single review.
The model avoids separate invite and publish modes while preserving consequences.
desktop system docs
Design-system input
One field component accepts composable label, help, and error slots.
The team removes three duplicated variants without hiding their states.
Privacy controls
Less effective
Delete granular controls so the page appears minimal.
Better fit
Use a safe summary with clearly available detail and one consistent model for inheritance.
Necessary user control is not accidental complexity.
Limits and failure modes
There is no context-free simplicity score, and simpler hypotheses or interfaces can be less accurate or less humane.
Common mistakes
- Equating fewer controls with fewer assumptions.
- Ignoring rare but high-consequence requirements.
When it should not dominate
- When simplification removes informed consent, safety, or expert capability.
- Before requirements and failure states are understood.
Responsible use
Accessibility
Do not remove labels, instructions, alternate input, or redundant cues in the name of visual simplicity; accessible redundancy can be essential.
On mobile: Use staged detail to fit the viewport while keeping consequences and recovery available.
Ethics and context
A simplified choice must not hide terms, consequences, or meaningful alternatives.
On desktop: Avoid filling space with secondary mechanisms; let one coherent model scale to richer workflows.
Designer checklist
- Write the requirements both solutions must satisfy.
- Identify assumptions added by each design.
- Retest edge cases after simplification.
Check your understanding
Which statement applies Occam’s Razor most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
Simplicity
Elliott Sober · Stanford Encyclopedia of Philosophy
Authoritative secondary
Continue the graph
Related principles
principle
Law of Prägnanz
Ambiguous visual input tends to organize into a stable, coherent form under the conditions present, often favoring relative simplicity or regularity.
heuristic
Tesler’s Law
Some task complexity is irreducible, so design determines whether the system, the user, or an organization carries that work.
usability heuristic
Progressive Disclosure
Progressive disclosure presents the information and controls needed now, then reveals additional detail when the user asks or the task reaches it.