Occam’s Razor
Synonyms: Ockham's razor, law of parsimony, principle of simplicity, KISS principle
Definition
Use cases
- The 14-field signup: Sales wants job title and phone number "for later." Signups drop, and nobody uses the data.
- The overthought diagnosis: Checkout drop-off spikes the week a coupon field ships. The team spends 2 weeks testing prices and trust badges before anyone checks the new field.
- The settings graveyard: Every stakeholder request becomes a toggle. 40 toggles later, users can't find the 1 they need.
How it's used in practice
- Run a removal test: For each element, ask "what breaks if this goes?" If nothing breaks, cut it.
- Check boring causes first: When a metric drops, look for a broken button or slow API before building a big theory.
- Hide, then delete: Move rare options behind progressive disclosure. After 30 days, remove what nobody touched.
- Ask for evidence: New feature requests need a user problem and data attached.
- Test simple vs. current: Run the stripped-down version against the existing one in a quick usability test.
Challenges & limitations
- Cutting too deep: Remove the export button power users rely on and they leave. Some complexity can't be removed, so decide whether the system or the user carries it.
- "Simplest" is subjective: A flow your team finds obvious can still confuse first-time users.
- Simple can look weak: Don Norman notes that buyers often pick the product with more features, even when it's harder to use.
Related laws & principles:
- Hick's Law — Best for deciding how many choices to show at once
- Tesler's Law — Best for deciding how much complexity the system absorbs for users
Free resources
- Designing With Occam's Razor — Yablonski on judging every element by whether it's needed
- Don Norman: Simplicity Is Not the Answer — the counterargument: simplicity and usability are different things
- UX Collective: How Steve Jobs Followed the Law of Parsimony at Apple — product examples from Apple
