Ockham’s Razor

Walden Systems Geeks Corner Tutorial Ockham’s Razor Rutherford NJ New Jersey NYC New York City North Bergen County

Ockham’s Razor is a problem-solving principle attributed to William of Ockham, an English Franciscan friar. The name comes from Ockham's surname plus razor, which refers to distinguishing between two hypotheses either by whittling away unnecessary assumptions or cutting apart two similar conclusions. It states that among competing hypotheses that predict equally well, the one with the fewest assumptions should be selected. This was popularized by Sherlock Holmes.

So what does this have to do with design? The answer lies in a modern interpretation of Occam’s Razor, entities must not be multiplied beyond necessity. When applied to UX design, Occam's Razor can be adopted as a guiding principle that informs our decisions and keeps us from reaching for a complex solution when a simpler one is enough.


Evaluate each and every design element based on it's necessity. We must constantly ask ourselves "What is the minimum amount of UI to effectively communicate to the user?” It's easy to make the mistake of thinking that we‘re enhancing the experience by sprinkling in delightful animations or hiding away navigation in an offscreen menu. The reality is you might be introducing unnecessary complexity that potentially can become an obstacle.

Be aggressive when editing work. Every design element and pattern should be evaluated on it's effectiveness, and edited if a simpler solution exists. If it doesn't have meaning or provide value, it should be removed. One effect way for evaluating design decisions is through our peers. Peer feedback provides an opportunity to initiate discussion and get feedback on design decisions from your peers. They force us to explain why we made specific design decisions, and in the process, strengthen our work by identifying spots that aren't as clear or effective.

Ockham’s Razor can help us in making design decisions and keep us from reaching for a complex solution when a simpler one is enough. By whittling away at complexity, our designs will have clarity and be more useful. Users will appreciate that we've eliminated obstacles and streamlined the interface, allowing them to find what they need faster and more efficiently.