Conjunction Fallacy.

01Overview

The conjunction fallacy (Tversky & Kahneman) is judging a specific combination of conditions as more probable than one of its constituents alone. "Linda is a bank teller and active in the feminist movement" feels more likely than "Linda is a bank teller" — because the story fits, even though conjunctions cannot exceed their parts.

For designers, the fallacy appears whenever a detailed persona scenario outranks a simpler, more common failure mode in prioritisation. The story with hooks — power user on mobile during commute loses access during billing edge case — beats the boring truth that most churn is silent non-use. Roadmaps chase conjunctions.

02Detailed explanation

Representativeness drives the error: a good story feels like a good prediction. Product examples:

• A vivid security breach scenario (nation-state attacker exploits obscure API on leap day) gets budget over mundane credential stuffing that actually drives incidents.
• Research highlights a specific journey (creator, tablet, poor connectivity, shared device) as "the" problem — ignoring that each factor alone covers more users.
• Stakeholders fund features for "enterprise admin + compliance + legacy SSO" intersection while SMB onboarding rots.
• Risk assessments overweight cinematic failure modes in decks over base-rate failures in logs.

Every detailed scenario is a conjunction. Conjunctions multiply conditions; multiplying conditions reduces probability. The more specific the story, the less likely it is — unless you count base rates.

03Why it exists

Narrative coherence is a cheap proxy for probability. The brain prefers explanations that hang together over arithmetic that contradicts them.

Organisations reward specificity in pitches. Vague base-rate problems feel unfundable; cinematic conjunctions get slides and sprints.

04Effects on users

Users overestimate personalised risk stories — "my account will be hacked because I saw one thread" — relative to boring base rates like weak password reuse.

They choose products marketed with vivid conjunction stories ("for freelancers who travel and invoice in euros") even when a simpler offer fits.

05Effects on designers & teams

Teams fall for conjunction in planning rituals:

• Persona journey theatre. Elaborate storyboards treated as frequency evidence.
• Edge-case sprints. Engineering for rare intersections while core flows stay brittle.
• Security and compliance theatre. Scenarios that impress boards vs threats in audit logs.
• Qualitative outlier elevation. One detailed interview outweighs aggregate analytics.

06Practical takeaways

• Decompose scenarios. Ask probability of each "and" separately; multiply roughly, compare to simpler hypotheses.
• Lead prioritisation with base rates. Logs and dashboards before storyboards.
• Require frequency tags on stories. "Vivid / rare / both" labels in research repositories.
• Separate plausibility from likelihood. A story can make sense and still be uncommon.
• Fund boring fixes. Password flows and empty states often beat cinematic feature work.
• Teach stakeholders the Linda problem. Shared vocabulary reduces conjunction pitches.

07Design examples

08Ethical risks

Funding cinematic conjunctions while ignoring base-rate harm neglects users whose problems are common but undramatic — often the least privileged users.

Fear-based conjunction scenarios in security UX can push invasive surveillance features that address vivid threats, not actual risk.

Self-test: What vivid user story is driving your roadmap — and what happens if you remove one "and" at a time?

09Related biases