Occam's Razor

Core idea

Prefer the explanation with the fewest moving parts

Named after the medieval logician William of Ockham, Occam's razor states that a plurality is not to be posited without necessity — when two explanations account for the same evidence equally well, the simpler one is more likely to be true. The razor is not a guarantee. It is a tiebreaker and a mindset: if your account requires ten things to all be true at once, and a competing account requires three, the three-thing account starts with a structural advantage.

The math behind the preference

The reason simpler explanations are more often right is mechanical. Suppose two theories each fit the data, but one chains together three assumptions and the other chains together thirty. If each assumption is 99 percent likely to be correct, the three-step theory has roughly a 97 percent chance of being right end-to-end, while the thirty-step theory has only about 74 percent. The more conjunctions you add, the more chances you give the chain to break. Simpler theories are robust to uncertainty in a way that elaborate ones are not.

Why it matters

Complex narratives feel deep but cost more to be wrong

Our minds love rich, intricate explanations — corporate conspiracies, secret motives, multi-step causal stories. They feel satisfying because they explain everything. But explaining everything is itself a warning sign: a theory that can fit any outcome cannot be tested against any. The simpler theory is easier to falsify, which is the same as saying it is easier to learn from. When you build a habit of asking "what is the least it could be?" you spend less energy chasing phantoms and more energy on the explanations you can actually verify.

Without the razor, decisions multiply needlessly

Time, attention, money, and team focus are finite. If every problem invites you to chase down its most elaborate possible cause, you exhaust yourself before solving the real one. Occam's razor is therefore not just a logic principle — it is a triage tool for limited bandwidth. Start with the simplest explanation. Test it. Move to the more complex one only if the simple one fails.

Key takeaways

Mental model

Copy sourceZoom

Practical application

The razor takes about five seconds to apply once you build the habit. The hard part is remembering to apply it before you have spent an hour chasing the elaborate explanation.

Example

A "mysterious" outage that wasn't

The on-call engineer wakes at 3 a.m. The dashboard is red. Latency on the payments service has spiked from 80ms to 4 seconds. The first hypothesis from the channel: a coordinated DDoS attack. Someone else floats a database deadlock from the new schema migration. A third suggests an upstream payment processor outage. Two engineers start drafting an incident report. A fourth opens a thread about whether to escalate to the CEO.

The senior engineer joining the call asks one question: "When did this start, and what shipped just before that?"

A deploy went out at 2:58 a.m. The first three hypotheses each required a complicated chain of events to be true at once — a coordinated attack timed to a Tuesday, a deadlock on a query that had been running for months, a third-party outage with no other signal. The simple hypothesis required only one thing to be true: the deploy broke something. The on-call engineer rolls back the deploy. Latency returns to 80ms within ninety seconds.

The post-mortem the next morning identifies a missing index in the migration. The complex theories were eliminated not by investigation but by not pursuing them first. The razor cost ninety seconds of judgement and saved an hour of detective work — at three in the morning, when an hour of detective work would also have cost the team a day of follow-up exhaustion.

Related lessons