System Design Principles
Occam's Razor
Prefer the simplest solution that works.
In practice
Takeaways
- 1
Remove UI that does not serve a clear user need.
- 2
One primary action per screen reduces hesitation.
- 3
Complexity should earn its place with measurable value.
Origins
Occam’s Razor advises choosing the explanation — or solution — with the fewest unnecessary assumptions. In product design, that translates to fewer competing actions, cleaner flows, and less cognitive overhead.
Simplicity is a discipline of subtraction backed by evidence.
Design Applications
- Audit screens for redundant controls and duplicate paths.
- Merge overlapping settings into one clear control.
- Ship the smallest version that solves the core job.
Frequently Asked Questions
Further Reading
Related Principles
View all ›Cognitive Load & Decision Making
Choice Overload
People become overwhelmed when presented with too many options.
Learn more ›Cognitive Load & Decision Making
Cognitive Load
Mental effort required to use an interface should be minimized.
Learn more ›System Design Principles
Pareto Principle
Roughly 80% of outcomes come from 20% of causes.
Learn more ›Tools worth a look
Some links are affiliate links — see disclosure.
- Free plan
Cal.com
Scheduling without the back-and-forth
Learn more (opens in new tab) - AI dictation
Wispr Flow
Write by voice, 3× faster
Learn more (opens in new tab) - Free to start
beehiiv
Start a design newsletter
Learn more (opens in new tab) - Free plan
Granola
AI notes for research calls
Learn more (opens in new tab)