Occam's Razor

Occam's Razor

Overview

Occam's Razor helps us pick the simplest explanation that still fits the data. When two theories explain the same phenomenon, start with the one that needs fewer assumptions.

Sticking with simple explanations saves time and energy and lowers the risk of error. Only when the simple version falls short do you add complexity.

Origin Story

William of Ockham argued we don't need to multiply entities without reason. The principle later became a pillar of the scientific method: scientists pick the simplest testable theory.

Albert Einstein captured the same spirit: everything should be made as simple as possible, but not simpler. Simplicity doesn't mean ignoring important facts.

Core Principles

1. Fewer Assumptions, Lower Risk

Every assumption has a chance of being wrong. Stack enough of them and your odds of being right drop fast. An explanation with two assumptions is stronger than one carrying five untested ones.

2. Test Simple First

When systems fail, check the basics first: unplugged cables, wrong configs, data not migrated. Don't jump straight to a big failure that's hard to prove.

3. Simplicity Still Obeys Facts

If the facts point to a complex phenomenon, don't force a simple story. Occam's Razor sets the order in which you check things; it isn't a reason to deny reality.

Brief Application Steps

1. List your hypotheses.
2. For each one, note the assumptions that have to be true.
3. Roughly score the error risk, say on a 1-5 scale.
4. Test the lowest-risk hypothesis first.
5. If the simple hypothesis fails, move up to a more complex one and write down what you learned.

Case Studies

• Digital Product Team: When traffic drops, the team first checks whether ads stopped running or campaign links broke before studying search algorithm changes.
• Car Rental Service: When bookings decline, the owner first checks fleet condition and admin response time before assuming customers switched to competitors.
• Home Maintenance: When the lights go out in one room, the resident checks fuses and switches before calling a technician to tear apart the wiring.

Practical Tips

• Get into the habit of running simple checklists before calling in expert teams.
• Write down explanations that worked before so you can revisit them when the problem recurs.
• Make Occam's Razor part of the team culture: "check simple first" before spinning up complicated theories.

Starting with the simplest solution lets us move fast, save resources, and add complexity only when we actually need it.