/ Library/ Not Enough Meaning/ Neglect of Probability
Connect Bias № 128 · Last updated 6 June 2026

Neglect of Probability.

"We react to the story of risk, not the odds — so probability vanishes from decisions."

01Overview

Neglect of probability is making decisions as if likelihood barely matters — a vivid rare outcome gets full weight, or a likely harm is ignored because it is boring. Probability leaves the room; emotion stays.

Designers see neglect in security theatre, consent walls, and growth bets. Users enable permissions after scare stories; teams ship features with low-probability upside and high-probability support debt without doing the maths. Zero-risk bias is the sibling demand to eliminate small risks entirely while neglecting larger probable ones.

02Detailed explanation

Probability neglect warps product trade-offs:

  • Fraud UX adds friction for all users to stop rare abuse — probable daily friction neglected.
  • Marketing cites breach horror stories; users ignore higher-probability mundane harms.
  • Roadmaps chase lottery-upside features over incremental reliability wins.
  • Insurance-style modals for impossible events slow core tasks.

Appeal to probability fallacy is the mirror error — treating possible as probable. Neglect is the broader failure to weight odds at all.

03Why it exists

Probability is abstract; outcomes are visceral. The brain prioritises images of harm or reward.

Legal and PR incentives push elimination of vivid rare risks — probability neglected in favour of headline avoidance.

The short version

What is the actual likelihood — and is your UI sized to the odds or to the headline?

04Effects on users

Users make permission and purchase decisions on worst-case stories — or skip precautions for likely risks that lack drama.

They suffer cumulative probable annoyance — slow flows, nag screens — while teams celebrate stopping improbable catastrophes.

05Effects on designers & teams

Teams design for headlines, not distributions:

  • Security theatre. Friction proportional to fear, not fraud rates.
  • Compliance modals. Rare legal scenarios block common paths.
  • Growth bets on virality. Neglect base rates of sharing behaviour.
  • Support cost blindness. High-probability confusion untreated.

06Practical takeaways

  • Quantify before friction. Expected value of risk vs cost of UX tax.
  • Tier interventions by likelihood. Rare risks: lightweight guardrails; common risks: robust design.
  • Communicate odds honestly. When stakes are high, show probability context.
  • Prioritise probable pain. Fix top support drivers before exotic edge cases.
  • Pair possiblity with base rates. Could happen ≠ will happen.
  • Review zero-risk demands. Are you eliminating tiny risk while ignoring big probable harm?

07Design examples

Security

Modal for everyone

A 0.01% account takeover scenario triggers step-up auth on every login. Daily success rates drop 4% — probable friction neglected for vivid rare risk.

Marketing

Breach billboard

Campaign stresses catastrophic hack. Users ignore phishing education — higher probability, lower drama. Neglect shapes misprioritised education.

Growth

Viral lottery

Roadmap bets on referral loop with 2% share rate industry-wide. Team assumes breakout. Probable mediocre outcome neglected; reliability work starved.

Consent

Exotic legal scare

Users wade through warnings about unlikely regulatory scenarios. Common data resale buried. Probability neglect in copy hierarchy.

08Ethical risks

Neglecting probable harms while fighting vivid rare ones wastes user time and can increase real aggregate harm.

Exploiting probability neglect — selling improbable upside, hiding likely downsides — is manipulative finance and growth practice.

Self-test: Which UX friction exists for a risk whose probability you have never measured?

10Suggested reading

Browse recommended reading →