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.
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.
Origin
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 to apply it
- 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.
How Science of Apps uses this law
1 checks in every investigation rely on Occam's Razor, for example: “Can the core task be completed in the fewest steps the domain allows, with complexity absorbed by the system?”
Get your product investigated