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.
Why it works
Rich narratives engage the brain’s pattern-matching and story-comprehension systems, which are optimized for coherence and causal plausibility — not probability. Translating "Linda is a feminist bank teller" into "what percentage of bank tellers are feminist activists?" moves the question from the associative system to a more calibrated numerical frame. Frequency format is consistently easier for people to reason about correctly than probability format, as Gigerenzen’s research on natural frequencies demonstrates.
How to do it
- Restate the claim in frequency form: "Out of 100 people with this background, how many would have both of these properties?"
- Compare that estimate to the frequency of just one of the properties in the same group.
- If the conjunction rate is higher than either component rate, you’ve caught a fallacy.
- Use this restatement before making any decision that depends on the joint scenario being likely.
Evidence
Gigerenzen and Hoffrage (1995) showed that natural frequency formats dramatically improve probabilistic reasoning accuracy compared to probability percentages — the conjunction fallacy rate drops substantially in frequency format. (rct)
Frequency framing reduces but does not eliminate the fallacy; some individuals still commit it in frequency format, especially under time pressure.
Sources
- Gigerenzen & Hoffrage (1995), How to improve Bayesian reasoning without instruction, Psychological Review
Common mistake
Translating to frequency format but keeping the narrative framing intact ("how many people like Linda…"), which still activates representativeness — the restatement must be genuinely dry.
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.
- Audit plans for scenario inflation
Before committing to a plan that depends on multiple things going right, count the dependencies.
- 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."