Occam's Razor
Also known as Law of Parsimony
Among solutions that work equally well, prefer the one with the fewest assumptions and parts — in design, the simplest option that does the job.
See it in action
The same screen without and with Occam's Razor. Watch both sides play out, then compare the outcome.
Every extra field is another assumption about what's needed — and another reason to quit.
One field achieves the same goal with fewer moving parts, fewer errors and less to maintain.
What to watch: both flows create an account — one with a fraction of the parts.
Among solutions that work, choose the one with the fewest steps, parts and assumptions.
Simplify away things people genuinely need; simplest-that-works, not simplest possible.
Key takeaways
- Remove any element that doesn't support the user's goal.
- Simpler solutions are easier to learn, test and maintain.
- Simplicity is the result of hard decisions, not missing features.
Quick facts
- Also known as
- Law of Parsimony
- Described by
- William of Ockham
- Year
- 14th century
- Category
- Product strategy
- Related laws
- Tesler's Law, Law of Prägnanz, Pareto Principle, Gall's Law
Occam's Razor explained
Occam's Razor states that among competing explanations, the one with the fewest assumptions should be preferred. In design, it means the simplest solution that fully solves the problem is usually the best.
Every element in an interface adds weight: something to read, understand and maintain. Removing what is not needed makes the remaining elements clearer and the product easier to use and build.
Simplicity does not mean minimalism for its own sake. The goal is to remove unnecessary complexity while keeping everything users need to succeed.
Where it comes from
Named after William of Ockham, a 14th-century English philosopher and friar, who used the principle that 'entities should not be multiplied beyond necessity'. The idea is older, but his name became attached to it.
How it shows up in apps
Feature creep is a common reason products feel heavier over time. Applying Occam's razor during reviews helps teams cut steps, settings and screens that add complexity without improving outcomes.
Occam's Razor examples
Instead of building a custom multi-step referral wizard, a team ships a single share sheet with a prefilled link — and it performs better.
One-tap actions
Ride-hailing apps reduced booking to choosing a destination and confirming, removing many steps that earlier taxi apps required.
Feature pruning
Teams that remove rarely used features often see improved satisfaction, because the remaining features are easier to find and the product feels focused.
Simpler sign-up
Replacing a multi-field registration form with email-only sign-up and asking for other details later often increases sign-ups without hurting activation.
How to apply Occam's Razor
- For every element on a screen, ask whether removing it would hurt users. If not, remove it.
- Prefer the simplest interaction that achieves the user's goal.
- Test simplified versions against the current design before adding new features.
- Defer optional information and advanced settings.
- Revisit features regularly and retire those with little use.
Want Occam's Razor checked in your own product? Our saas ux audit evaluates it alongside the other principles that shape how users decide, onboard and stay.
Common mistakes
- Removing essential information or controls in the name of simplicity.
- Adding complexity to handle rare edge cases in the main flow instead of in secondary paths.
- Mistaking visual minimalism for simplicity while the underlying flow remains complicated.
How to measure it
Compare task success, time on task and conversion between simplified and current versions. Feature usage analytics reveal which elements can be removed with little impact.
Frequently asked questions
What is Occam's Razor?
Among solutions that work equally well, prefer the one with the fewest assumptions and parts — in design, the simplest option that does the job.
Where does Occam's Razor come from?
Named after William of Ockham, a 14th-century English philosopher and friar, who used the principle that 'entities should not be multiplied beyond necessity'. The idea is older, but his name became attached to it.
How does Occam's Razor apply to app design?
Feature creep is a common reason products feel heavier over time. Applying Occam's razor during reviews helps teams cut steps, settings and screens that add complexity without improving outcomes.
Who is Occam's Razor named after?
It is named after William of Ockham, a 14th-century English philosopher and theologian.
How does Occam's Razor apply to UX design?
Choose the simplest design that fully meets users' needs, and remove elements that do not contribute to their goals.
How do you measure Occam's Razor in a product?
Compare task success, time on task and conversion between simplified and current versions. Feature usage analytics reveal which elements can be removed with little impact.
Sources
- Spade, P. V. & Panaccio, C. William of Ockham. Stanford Encyclopedia of Philosophy. Find on Google Scholar ↗
Related laws
Product strategyTesler's Law
Every system has a certain amount of complexity that can't be removed — only moved — so the product should absorb it instead of passing it to users.
PerceptionLaw of Prägnanz
People interpret complex or ambiguous visuals in the simplest way possible, because simple forms take the least mental effort to process.
Product strategyPareto Principle
For many outcomes, roughly 80% of the effects come from about 20% of the causes — so a few features, users or issues usually matter most.
Product strategyGall's Law
A complex system that works has invariably evolved from a simple system that worked; complex systems designed from scratch rarely work.
Occam's Razor in practice
- Making moneyApp monetization strategies that don't annoy users — designed with behavioural scienceMonetize your app without wrecking retention: value-first paywalls, honest trials, rewarded ads, anchoring and decoy pricing done ethically, and what to avoid.
- Making moneySubscription vs one-time purchase: which makes more money for your app?Subscription vs one-time purchase for apps: lifetime value maths, when each wins, hybrid models, store fees and what Indian users prefer.
- Product managementPRD template: how to write a product requirements document your team will readA PRD template for product teams: problem, goals, users, solution, requirements, metrics, risks and decisions — plus a one-page version and writing tips.
- AI & vibe codingWill AI replace product managers? Which parts of the job AI takes, and which it can'tWill AI replace product managers? Which PM tasks AI already automates, the judgment work it can't do, how the role is changing, and how PMs can stay ahead.
- App marketing & ASO50 push notification examples that actually get clicked — and why they work50 push notification examples for onboarding, habits, commerce, money, social, learning and win-back — with the principle behind each one.
- Career guidesProduct discovery and validation skills employers want in 2027: customer interviews, opportunity solution trees, assumption mapping, prototypes and fake-door testsProduct discovery skills employers want in 2027: customer interviews, opportunity solution trees, assumption mapping, the four big risks and fast tests.
Certifications that test it
- Free certification · UX/UI, Design, Research & CreativeProduct Design CertificationCertifies end-to-end product design: framing problems against business goals, designing and shipping solutions with engineering, and measuring their impact.
- Free certification · UX/UI, Design, Research & CreativeDesign Systems CertificationCertifies that you can build, document, govern and scale a design system — tokens, components, documentation, adoption and design–engineering collaboration.
- Free certification · AI & Generative AIAI UX Design CertificationCertifies that you can design AI-powered products people trust — setting expectations, conversational and agent UX, handling errors and uncertainty, and responsible AI.
- Free certification · Product, Project Management & Business AnalysisProduct Manager CertificationCertifies that you can run product well — discovery, strategy and prioritization, metrics, delivery with design and engineering, and launch.
- Free certification · Product, Project Management & Business AnalysisAgile Product Owner CertificationCertifies that you can do the product owner job in agile teams — Scrum roles and events, backlog ordering and refinement, user stories and acceptance criteria, and value-focused releases.
- Free certification · Product, Project Management & Business AnalysisProduct Strategy CertificationCertifies that you can set product strategy — customer and market insight, positioning and differentiation, strategic choices and bets, and outcome roadmaps and OKRs.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.