/ Library/ Need to Act Fast/ Lake Wobegon Effect
Decide Bias № 092 · Last updated 6 June 2026

Lake Wobegon Effect.

"In our data, everyone is above average — which means the scale is lying, not the people."

01Overview

The Lake Wobegon effect — named for Garrison Keillor's fictional town where all children are above average — describes systematic inflation of self and peer ratings above statistical possibility. Entire cohorts report superior performance; distributions cluster impossibly high.

For designers, Lake Wobegon appears in normalised performance reviews, survey items where everyone selects "advanced," NPS segments where all internal teams claim customer-centricity, and research recruitment that screens out anyone who admits struggle. The map says everyone is exceptional; the territory says otherwise.

02Detailed explanation

Lake Wobegon corrupts measurement when incentives favour high scores:

  • Self-assessed UX maturity models where every squad selects level four of five.
  • Peer design critiques scoring "communication" — all above median by social contract.
  • Vendor and tool satisfaction surveys with ceiling clustering — nothing below eight of ten.
  • Hiring rubrics where interviewers rate candidates above historical calibration.

The effect is organisational illusory superiority at scale. Without forced ranking or external benchmarks, instruments become polite fiction — useless for prioritisation, dangerous for strategy.

03Why it exists

Rating systems without stakes become courtesy. Social desirability and harmony push scores up; honesty is punished.

Survivorship and selection effects remove low performers from the sample — remaining population genuinely looks strong while denominator shrinks.

The short version

If your survey shows nobody is below average, fix the survey — not the strategy.

04Effects on users

Users rate satisfaction high in-session while behaviour shows struggle — Lake Wobegon in micro-feedback widgets.

They participate in platforms where everyone displays optimised profiles — comparative misery follows from impossible norms.

05Effects on designers & teams

Teams build Lake Wobegon into ops:

  • Uncalibrated maturity assessments. Everyone "advanced" — no investment case.
  • Review inflation. Managers avoid low scores; data loses discrimination.
  • Ceiling-heavy UX metrics. CSAT after happy paths only — Wobegon by sampling.
  • Benchmark decks without base rates. Cherry-picked wins imply universal excellence.

6Introspective view

Look inward. Groups over-report performance above the statistical norm ('all above average').

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

Retrospectives

The story of the sprint

Retros on Lake Wobegon Effect tend to rehearse the narrative that is easiest to tell — usually the one that matches how people already feel about the work. Groups over-report performance above the statistical norm ('all above average').

Surveys

Question order shapes answers

A survey built to study Lake Wobegon Effect often primes respondents before the key item: lead with a vivid scenario and later ratings drift toward that frame. Groups over-report performance above the statistical norm ('all above average').

Measurement

Metrics that flatter the release

Iteration reviews for Lake Wobegon Effect gravitate toward dashboards that make the recent release look successful, while quieter indicators of harm stay uncharted. Groups over-report performance above the statistical norm ('all above average').

User Interviews

What you hear first sticks

In early interviews about Lake Wobegon Effect, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Groups over-report performance above the statistical norm ('all above average').

07Practical takeaways

  • Calibrate instruments externally. Audits, benchmarks, behavioural validation.
  • Force distribution or absolute bars. Where appropriate — not hollow quotas.
  • Sample failure paths. Metrics from struggle, not only success moments.
  • Separate perception from performance. Self-report plus task outcomes.
  • Reward honest low scores. Culture fix for survey inflation.
  • Watch for impossible clusters. Statistical smell test on all internal surveys.

08Design examples

Ops

All teams mature

Annual UX maturity survey: 92% rate above level three. External audit finds basic accessibility gaps in most products. Lake Wobegon blocked budget until third-party shame.

Reviews

Everyone exceeds

Performance system allows no below-average rating without HR path. Analytics on ratings useless; promotions feel arbitrary — inflation ate signal.

Micro-surveys

Five stars after failure

Post-task CSAT shown only after completion — struggling users abandon; respondents rate high. Lake Wobegon sampling bias in product metrics.

Hiring

Amazing pipeline

Interviewers rate 80% of candidates above historical hire bar. Hires underperform — Wobegon in rubric softened discrimination.

09Ethical risks

Performance systems that forbid honest low scores hide exclusion and burnout — victims cannot name problems in inflated data.

User-facing comparisons on Lake Wobegon norms — "you beat 90%" — manufacture inadequacy when benchmarks are fake.

Self-test: Which internal metric shows universal excellence — and what independent test would contradict it?

10Suggested reading