Always identify the denominator when evaluating risk or success
When a number or story is striking, ask: "Out of how many total cases?"
Why it works
Denominator blindness is the failure to consider the base population when evaluating a frequency. Hearing about five startup successes is not diagnostic of success rates without knowing the denominator — whether it is 50 or 5,000 produces radically different inferences. The vividness of the numerator (the five success stories) suppresses the search for the denominator, which is where the base rate lives.
How to do it
- Whenever you hear a frequency or count ("five companies succeeded"), immediately ask: "Out of how many total?"
- Express the data as a rate (5/500 = 1%) rather than a count.
- Look for survivorship bias: are you only seeing the cases that were reported because they were notable?
Evidence
Numerosity neglect and denominator blindness are well documented in risk communication research and public health contexts, where presenting absolute numbers without denominators systematically misleads perceived risk. (observational)
Sources
- Gigerenzen & Edwards (2003), "Talking Sense to Patients About Risk," BMJ — denominator neglect in medical decision-making
Common mistake
Looking for the denominator only when the numerator seems alarming — the same error applies when the numerator seems reassuring ("only 10 side effects reported").
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Base-Rate Neglect: Why We Ignore the Odds
- Ask the base rate before evaluating the specific case
Before judging any individual instance, first establish how often this kind of thing happens in general.
- Use reference class forecasting for project estimates
Estimate how long similar projects have taken historically before estimating your specific project.
- Update beliefs by degrees, not wholesale
Treat new information as evidence that shifts probabilities, not as proof that changes everything.
- Deliberately invoke the outside view for important decisions
For any high-stakes prediction, force yourself to start with how things typically go, not how your situation feels.
- Practice probabilistic calibration by tracking your predictions
Assign explicit probability estimates to your predictions and track whether they come true at the right rate.
- Expect regression to the mean in extreme outcomes
Unusually good or bad performance tends to be followed by more average performance — not because of what you did.
Related concepts
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Bayesian Thinking: How to Update Beliefs Rationally
Holding beliefs as probabilities and updating them when evidence arrives
- Anchoring Bias in Negotiation and Judgment
Why the first number wins — the mechanism, and how to set and resist anchors