Audit plans for scenario inflation
Before committing to a plan that depends on multiple things going right, count the dependencies.
Why it works
Plans are coherent stories, and the conjunction fallacy inflates the apparent probability of compound plans: "we will recruit effectively AND launch on time AND customers will respond." Each "and" is a multiplication of probabilities; a plan with five 80%-likely steps has only a 33% chance of complete success even if each step is quite likely individually. Auditing for hidden conjunctions turns an appealing narrative into an honest probability landscape and often motivates simplifying the plan.
How to do it
- List every assumption your plan depends on succeeding.
- Assign a rough probability to each assumption independently.
- Multiply the probabilities (or simply count the number of "and" dependencies) to get a rough joint probability.
- Identify which assumption, if wrong, is most damaging, and address that first.
Evidence
The multiplication rule for independent events is mathematically established; its application to planning underestimates risk in a way consistent with the planning fallacy and conjunction fallacy literatures. (mechanistic)
Real plan steps are rarely truly independent, and dependencies can cut both ways; this audit is a corrective heuristic, not a precise probability calculation.
Common mistake
Counting only the explicit assumptions and missing the implicit ones — most plans depend on more conditions than they name, so the audit should actively search for unstated dependencies.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Conjunction Fallacy — When "More Details" Feels More Likely
- Test each component probability separately
Before judging a joint claim, estimate each element on its own, then check whether the conjunction is lower.
- Anchor on base rates before adding details
Start with how common the outcome is in the relevant population, then update — don’t start with the story.
- Strip the narrative and restate as a bare frequency claim
Translate the vivid scenario into a dry statistical question to see if it still feels probable.
- Consult an outside observer to counteract narrative pull
Describe the scenario to someone who doesn’t share your narrative context and listen to their probability estimate.
- Explicitly distinguish coherence from probability
A story can be internally consistent and still be rare — learn to separate "makes sense" from "likely."
- Red-team joint scenarios before betting on them
Before acting on a conjunction ("X will happen AND Y will follow"), assign a skeptic to attack the "and."