Linda is 31, single, outspoken, and very bright. She majored in philosophy. As a student, she was deeply concerned with issues of discrimination and social justice. Which is more probable: (a) Linda is a bank teller, or (b) Linda is a bank teller AND active in the feminist movement? Roughly 85% of respondents — including statistics graduate students who know better — choose (b). They're all wrong.
The Framework
The conjunction fallacy is the violation of probability's most basic rule: the probability of two events occurring together (A AND B) can never exceed the probability of either event alone. "Bank teller AND feminist" is a subset of "bank teller" — it must be less probable, by definition. Yet the description of Linda makes "feminist bank teller" feel more probable because it matches the story better. Representativeness (how much the description resembles the category) overrides logic.
Kahneman's Chapter 15 demonstrates that the fallacy isn't just a trick question — it reveals a fundamental feature of System 1: plausibility substitutes for probability. "Linda is a feminist bank teller" is a more plausible description (it fits her profile), and System 1 conflates plausibility with probability. The conjunction feels right because the story is better, not because the math works.
Where It Comes From
Tversky and Kahneman published the Linda problem in 1983. Chapter 15 of Thinking, Fast and Slow presents it as the most dramatic demonstration of representativeness bias. The most striking aspect: even after the logical error is explained, the intuition persists. You can know that "bank teller" must be more probable and still feel that "feminist bank teller" is the better answer. This is the cognitive illusion: the Müller-Lyer lines of probability judgment.
> "When you specify a possible event in greater detail you can only lower its probability." — Thinking, Fast and Slow, Ch 15
Cross-Library Connections
Hormozi's offer stacking in $100M Offers inadvertently exploits the conjunction fallacy's positive side: adding specific, vivid details to an offer makes it feel more likely to deliver results, even though each additional element technically introduces additional uncertainty. "You'll get 1:1 coaching, a custom meal plan, AND weekly accountability calls" feels more certain than "You'll get results" — even though the simpler claim is more likely to be true.
Berger's storytelling principle in Contagious leverages the same mechanism: specific, detailed narratives feel more probable and more shareable than abstract claims, because System 1 evaluates stories by plausibility rather than probability.
The Implementation Playbook
Sales and Marketing: Specific, detailed descriptions of outcomes feel more probable to prospects even though they're objectively less probable. "You'll increase revenue by 47% within 6 months through our proprietary three-phase implementation system" feels more achievable than "Your business will improve" — even though the specific claim is far less likely to be exactly true. Use specificity to leverage the conjunction effect, but ensure the specific claims are genuinely achievable.
Risk Assessment: When evaluating scenarios, beware of detailed risk stories that feel vivid and therefore probable. A security consultant who describes a specific attack scenario ("A state-sponsored actor exploits the API vulnerability, exfiltrates customer data, and sells it on the dark web") may make that specific chain feel more likely than a simpler claim ("We'll have a security breach"). The detailed scenario is objectively less probable but feels more real.
Legal and Compliance: In litigation, specific causal narratives feel more probable to juries than simpler claims. A plaintiff who describes a detailed chain of negligence (step 1 → step 2 → step 3 → harm) may win more easily than one who simply claims "the defendant was negligent." The detailed narrative exploits the conjunction fallacy in the jury's System 1.
Decision-Making: When your team presents a plan as a sequence of specific steps that all must succeed, test each step independently. The plan feels probable because each step sounds plausible — but the conjunction of all steps succeeding is much less probable than any individual step. If Step 1 has 80% probability, Step 2 has 80%, and Step 3 has 80%, the plan's probability is only 51% — not the "about 80%" that each step's individual plausibility suggests.
Key Takeaway
The conjunction fallacy proves that human probability judgment runs on plausibility, not mathematics. Adding detail to a story makes it feel more likely — even when it mathematically cannot be. This is why specific scenarios feel more real than abstract ones, why vivid business plans feel more achievable than vague ones, and why detailed risk descriptions create more fear than statistical summaries. The correction: always remember that specificity reduces probability. The more detailed the prediction, the less likely it is to be exactly true.
Continue Exploring
[[Representativeness Heuristic]] — The mechanism that produces the conjunction fallacy: judging by resemblance rather than base rates
[[WYSIATI]] — The detail in "feminist bank teller" becomes "all there is," making the conjunction feel complete
[[Substitution Heuristic]] — Plausibility (easy to evaluate) substitutes for probability (hard to calculate)
📚 From Thinking, Fast and Slow by Daniel Kahneman — Get the book