/ Library/ Not Enough Meaning/ Optimism Bias
Connect Bias № 123 · Last updated 22 May 2026

Optimism Bias.

"We systematically overestimate positive outcomes and underestimate risks to ourselves."

01Overview

Optimism bias is the well-documented tendency to overestimate the likelihood of positive future events and underestimate the likelihood of negative ones — specifically for ourselves. We believe we are less likely than average to get divorced, develop cancer, or be in a car accident. We believe we are more likely than average to live longer, succeed at our projects, and enjoy our purchases.

For designers, this bias shapes how users interpret onboarding promises, estimate the effort required to learn a product, assess privacy risks, and evaluate the true cost of subscriptions. It also pervades product teams themselves — optimism bias is a core driver of the planning fallacy, missed deadlines, and undercooked risk assessments.

02Detailed explanation

Tali Sharot's neuroimaging research shows that the brain's frontal cortex actively updates beliefs more readily in response to good news than bad. Weinstein's classic 1980 studies showed that 90% of participants rated themselves as less likely than average to experience a range of negative life events — a mathematical impossibility that reveals the systematic nature of the bias.

  • The "above-average" effect: most people believe they are above-average drivers, above-average parents, and above-average at their jobs — despite this being statistically impossible.
  • Optimism bias is particularly strong for events perceived as controllable — "it won't happen to me because I'm careful" — and weaker for events perceived as random, like lottery wins.
  • The bias is cross-cultural and robust across domains — it appears in health, finance, relationships, and professional performance estimates alike.
  • Optimism bias interacts with planning: when estimating how long a project will take, we imagine our project going well (the inside view) rather than consulting base rates for similar projects (the outside view).

03Why it exists

A degree of optimism is adaptive — unrealistically negative expectations lead to depression and paralysis; unrealistically positive ones fuel motivation, risk-taking, and persistence. Sharot argues that optimism bias is a feature of the human predictive brain, which evolved to model positive futures in order to motivate pursuit of them. The cost is systematic underestimation of real risks.

The short version

We fill the gaps in an uncertain future with the story that works out best for us. This is motivating and generally adaptive — and it means users will consistently underestimate costs, risks, and effort while overestimating the benefits your product will deliver.

04Effects on users

  • Users who sign up for a product expecting it to take "ten minutes to set up" and encounter an hour-long onboarding process experience disproportionate frustration — not because the setup is long in absolute terms, but because the gap between expectation and reality feels like a breach.
  • Subscription sign-ups are driven by optimistic estimates of how much the user will use the product. Most subscription churns are the correction of optimism: the user used it less than they expected, and the ongoing cost no longer seems justified.
  • Privacy risk disclosures are systematically under-weighted: users believe data breaches, identity theft, and tracking harms will affect other people more than themselves, making detailed consent flows feel irrelevant rather than important.
  • Users vastly underestimate how long learning curves will be, leading to early abandonment when the product doesn't become intuitive as quickly as they imagined.

05Effects on designers & teams

  • Roadmap planning: feature estimates are almost always optimistic — not because teams are dishonest, but because each team member imagines their own work going well. The accumulated optimism of a whole team produces sprint plans that are structurally overloaded.
  • Launch confidence: product teams are optimistic about adoption rates, time-to-value for users, and the completeness of their QA — even when historical data from their own previous launches suggests lower success rates.
  • User research: designers who are excited about a new feature are optimistic interpreters of ambiguous user research signals — hearing enthusiasm where mild interest was expressed, and certainty where qualification was offered.
  • Risk assessment: security reviews, accessibility audits, and performance budgets are treated as lower priority because the team is optimistic that problems won't surface in production — despite base rates suggesting otherwise.

6Introspective view

Look inward. Teams systematically overestimate positive outcomes and underestimate risk to their own plans.

From an introspective perspective, ask how Optimism Bias may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

Planning

The first estimate in the room

Sprint planning around Optimism Bias is vulnerable to whichever number is spoken first — story points, dates, or effort — because later estimates adjust from that anchor rather than from zero. Teams systematically overestimate positive outcomes and underestimate risk to their own plans.

Prioritisation

What the roadmap protects

Roadmap conversations about Optimism Bias often overweight what is already shipping and underweight what is merely possible. Teams systematically overestimate positive outcomes and underestimate risk to their own plans.

Strategy

The brief you inherited

Strategy work on Optimism Bias often starts from a problem statement someone else wrote — and that opening frame limits which solutions feel in scope. Teams systematically overestimate positive outcomes and underestimate risk to their own plans.

User Interviews

What you hear first sticks

In early interviews about Optimism Bias, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Teams systematically overestimate positive outcomes and underestimate risk to their own plans.

7Extrospective view

Look outward. Optimistic projections (savings, progress) can motivate users but mislead if presented as certain.

From an extrospective perspective, Optimism Bias is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.

Progress

How far along it feels

Progress bars and step counts change behaviour through Optimism Bias — users treat sunk steps as a reason to continue, or misread how much work remains. Optimistic projections (savings, progress) can motivate users but mislead if presented as certain.

Microcopy

Words that set the frame

Button labels, helper text, and error messages carry Optimism Bias in miniature — a single verb choice can reframe the same action as gain, loss, risk, or relief. Optimistic projections (savings, progress) can motivate users but mislead if presented as certain.

Engagement

Hooks that bring people back

Engagement mechanics tied to Optimism Bias — streaks, badges, unfinished counts — make returning feel more valuable than skipping, sometimes beyond what the content alone justifies. Optimistic projections (savings, progress) can motivate users but mislead if presented as certain.

Onboarding

Learning the product

New users experience Optimism Bias through onboarding — early wins, skipped steps, and promised time-to-value become the template for whether the product feels easy or misleading. Optimistic projections (savings, progress) can motivate users but mislead if presented as certain.

08Practical takeaways

  • Set realistic onboarding expectations upfront: tell users how long setup actually takes. Optimism bias means they'll still underestimate — but reducing the gap reduces the expectation failure and associated churn.
  • Use the "outside view" for project estimates: ask how long similar projects actually took — not how long this one should take. Historical base rates consistently outperform inside-view estimates.
  • Make risk concrete and personal: generic privacy risk descriptions ("your data may be used") are easily discounted through optimism. Specific, personalised framings ("this means companies can track everywhere you go") are harder to dismiss.
  • Design for the gap between expectation and reality: the moment users realise a product is harder than they expected is a high-churn risk moment. Acknowledge the learning curve explicitly — "most users are fluent within a week" — rather than pretending it doesn't exist.
  • Run pre-mortems on product launches: before shipping, explicitly imagine the launch failing and work backwards. This counteracts team-wide optimism bias with a structured pessimism exercise.

09Design examples

Onboarding

Setup time expectations

"Get started in 5 minutes" is an onboarding promise optimism bias makes extremely dangerous. Users who expect 5 minutes will feel deceived at 15 — even if 15 minutes is genuinely fast for the complexity involved. Accurate time estimates calibrate expectations and reduce abandonment driven by perceived broken promises.

Subscriptions

The optimistic sign-up

A user signs up for an annual subscription expecting to use the product daily. They use it twice. At renewal, the subscription cost feels wildly out of proportion to actual usage — despite being identical to what they agreed to. The problem isn't the price; it's the gap between optimistic sign-up intent and realistic behaviour.

Privacy

The dismissed risk disclosure

A privacy policy explains that user data may be shared with third-party partners. The user, optimistic that this won't affect them personally, clicks through without reading. Optimism bias, not laziness, is the primary driver — the risk genuinely doesn't feel applicable to the individual, even when it is.

Roadmaps

The optimistic sprint

A sprint is planned with 12 story points per developer, based on each developer's estimate of their own best-case week. The team's collective optimism produces a sprint that is 40% overloaded before the first standup. Historical velocity data — consistently ignored — would have produced a realistic plan.

10Ethical risks

Optimism bias can be exploited by presenting inflated benefit claims that users' own optimism confirms and amplifies — "you'll save 5 hours a week," "get results in 30 days," "most users see improvement immediately." These claims leverage the user's existing tendency to imagine best-case futures, producing consent and purchase decisions based on unrealistically positive expectations.

Marketing to optimism is not inherently unethical — but there is a line between realistic positive framing and deliberately feeding a bias to extract a decision the user wouldn't make with accurate expectations.

10Suggested reading