Occam's Razor
Among competing solutions that achieve the same outcome, the one with the fewest assumptions and moving parts should be preferred. Complexity is not a feature — it is a cost.
Overview
Occam's Razor is a philosophical principle stating that among competing hypotheses that predict equally well, the one requiring the fewest assumptions should be selected. Applied to design, it becomes a discipline of subtraction: if two designs solve the same problem, the simpler one is better — not just aesthetically, but functionally. Simpler designs have fewer failure modes, are faster to learn, and produce fewer errors.
The principle is deceptively difficult to apply. Designers and engineers have a natural tendency toward addition — adding features to solve problems, adding explanations to reduce confusion, adding options to serve edge cases. Occam's Razor demands the opposite instinct: to ask what can be removed while still meeting the goal, and to resist the pull toward unnecessary complexity that often masquerades as thoroughness.
Takeaways
- 01
Remove every element that does not directly serve the user's goal — decoration, redundant labels, rarely used features, and unnecessary steps all have a real cost.
- 02
When two designs solve the same problem equally well, the simpler one is the better design — it has fewer things to go wrong and less for the user to learn.
- 03
Simplicity is not the same as minimalism: the goal is the fewest assumptions required, not the fewest pixels or features. Sometimes complexity genuinely serves the user; Occam's Razor asks you to earn it.
How to Apply This
Question every element before adding it.
Before introducing a new UI element, feature, or step, ask: what problem does this solve, and is there a simpler solution that solves the same problem? The cost of adding is always higher than it appears — every addition increases cognitive load, maintenance burden, and the number of things that can break.
Audit existing designs for accretion.
Products accumulate complexity over time as features are added for edge cases that rarely occur. A periodic audit that asks 'what would we remove if we were starting fresh?' surfaces candidates for simplification. Features used by fewer than 5% of users often have a disproportionate cost in interface complexity for the other 95%.
Prefer clear over clever.
Complex, clever solutions often require more assumptions about the user than simple, clear ones. A tooltip that appears on hover assumes the user will hover. A help icon assumes they'll click it. Clear, inline copy requires no such assumption. The simpler path is almost always the more legible one.
Common Misconception
Occam's Razor is not a mandate for minimalism or aesthetic spareness. A complex tool — a code editor, a data visualisation platform — may legitimately require significant complexity to serve its users well. The principle doesn't say remove complexity; it says remove unnecessary complexity. The question is always whether the complexity present is doing work that cannot be eliminated without sacrificing the outcome.
Origin
The principle is attributed to the 14th-century English friar and philosopher William of Ockham, who wrote: 'Entities should not be multiplied beyond necessity' (often paraphrased as 'the simplest explanation is usually the correct one'). The principle was not invented by Ockham — similar ideas appear in Aristotle — but his consistent application of it gave it his name. In the 20th century, Occam's Razor became a foundational heuristic in science, mathematics, and engineering, and has since been adopted in design as a guiding principle for managing complexity.
FAQ
- What is Occam's Razor in UX design?
- In UX, Occam's Razor is the principle that simpler solutions are preferable to complex ones when they achieve the same outcome. It provides a framework for deciding what to cut: if removing an element, step, or feature doesn't reduce the product's effectiveness for its users, removing it is the better choice.
- Does Occam's Razor mean all interfaces should be minimal?
- No. Occam's Razor is about removing unnecessary complexity, not all complexity. A professional tool that serves expert users may legitimately need rich functionality, dense information, and many controls. The principle asks whether the complexity present is earning its keep — not whether it can be reduced to the barest possible form.
- How do you decide what's 'unnecessary' in a design?
- By asking whether a user goal is served by the element. If removing it doesn't change the ability of users to accomplish their core tasks, it's a candidate for removal. Usage analytics, task analysis, and direct observation all help identify features that look necessary but are rarely or never used in practice.
- What is the relationship between Occam's Razor and cognitive load?
- They are closely related. Cognitive load theory identifies the cost of unnecessary complexity in terms of mental effort — every element a user must process claims a share of limited working memory. Occam's Razor is the design discipline that keeps that cost in check: by removing what isn't necessary, you free cognitive resources for what is.
