Back to Glossary

Occam’s Razor

Synonyms: Ockham's razor, law of parsimony, principle of simplicity, KISS principle

Do not index

Definition

Occam's razor says that when 2 solutions do the same job, pick the one with the fewest assumptions and moving parts.
In UX, every screen, field, and feature has to earn its place. It's named after 14th-century philosopher William of Ockham and shapes decisions about cognitive load and information architecture.
 

Use cases

Ignore it and the product bloats. Every extra option adds a decision for users and test time for the team.
Examples:
  • 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.
🪄
Count the decisions a user makes, along with the elements on screen. A screen with 6 choices can take longer to finish than 3 screens with 1 choice each.
 

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

Share this post

Get free UX resources

Get portfolio templates, list of job boards, UX step-by-step guides, and more.

Download for FREE
 
 

The best email 📮 for growing 🌱 designers

Honest notes about the work behind the work. Read in 2 minutes, weekly. Free forever.
 
 
     
    notion image
    Join 13,045 designers and get tactics, hacks, and tips.