01Overview
Egocentric bias is the tendency to rely too heavily on one's own perspective when judging what others know, believe, or care about. It is related to but broader than the curse of knowledge: not only do we forget what it was like not to know — we assume our vantage point is more widely shared than evidence supports.
For designers, egocentric bias is the quiet assumption behind "users will obviously…" statements in critiques, onboarding copy written from insider mental models, and research synthesis that treats the team's experience as representative. The product was built from the inside; egocentric bias makes the inside feel universal.
02Detailed explanation
Egocentric bias appears whenever internal perspective substitutes for user evidence:
- Navigation labels that make sense in org charts but not to first-time visitors who lack your category map.
- Feature prioritisation driven by what the team finds interesting rather than what jobs users hire the product to do.
- Empty states and error messages that reference internal system names users have never seen.
- Research debriefs where observers project their own reactions onto participants without checking.
Egocentric bias compounds with homogeneity: teams that look and live alike share more than they realise — and underestimate how different everyone else is. The bias is not arrogance; it is the default setting of a mind that only ever inhabits one skull.
03Why it exists
First-person experience is the most vivid data available. The brain treats what is salient to self as more common than base rates justify — a fast heuristic that fails at scale.
Product work rewards confident internal narrative. Roadmaps, decks, and critiques favour coherent stories from people in the room. Egocentric bias makes those stories feel like market truth.
When you say "users will get this," ask which users — and whether any evidence exists beyond your own comprehension.
04Effects on users
Users do not share your org chart, your jargon, or your assumption that everyone has been paying attention since beta. They encounter the product mid-journey, distracted, with goals that never appeared in your brief.
They also bring their own egocentric bias: assuming the product was built for people exactly like them, misreading personal preference as universal design quality.
05Effects on designers & teams
Teams institutionalise egocentric bias through familiar habits:
- Dogfooding as proxy for research. If it works for us in the office, it works — ignoring connectivity, literacy, and context gaps.
- Expert review replacing user exposure. Seniors substitute pattern libraries and taste for evidence from people unlike the team.
- Copy written from feature specs. Microcopy names internal objects because writers see the architecture daily.
- Personas as mirrors. Personas that resemble the team get detailed journeys; others stay cardboard.
6Introspective view
Look inward. Teams over-weight their own perspective and knowledge when imagining users.
From an introspective perspective, ask how Egocentric Bias may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.
Themes that fit the deck
During synthesis, Egocentric Bias nudges teams toward a tidy narrative — quotes that support the emerging story rise to the top; outliers stay in the spreadsheet. Teams over-weight their own perspective and knowledge when imagining users.
Segments you already believe in
Persona work on Egocentric Bias can quietly recycle existing assumptions — vivid archetypes feel true because they match who the team already designs for. Teams over-weight their own perspective and knowledge when imagining users.
What you hear first sticks
In early interviews about Egocentric 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 over-weight their own perspective and knowledge when imagining users.
Questions you set out to answer
Discovery framed around Egocentric Bias can narrow what you go looking for before the first interview ships. Teams over-weight their own perspective and knowledge when imagining users.
07Practical takeaways
- Test with people who don't know what you know. Recruit for ignorance of your domain, not just demographics.
- Run the five-second and first-click tests. Egocentric bias dies quickly when outsiders cannot parse your UI cold.
- Separate internal clarity from user clarity. What is obvious in Figma with annotations is not obvious in production.
- Log "obvious to us" claims. Flag assumptions in critiques; require evidence before they ship.
- Diversify research and team input. Dissimilar perspectives surface egocentric gaps faster.
- Write copy for arrival, not tenure. Assume users meet each screen for the first time.
08Design examples
Obvious to us
A fintech app labels a tab "Ledger." Internal testing shows 94% task success. External participants ask what a ledger is. Egocentric naming met team vocabulary, not user language.
The feature we wanted
A collaboration tool ships advanced commenting because the team craved it. Usage data shows 70% of accounts never open comments. The roadmap reflected internal hunger, not observed behaviour.
Error 4023
An error references an internal service codename. Support tickets ask "what is Prism?" Users cannot self-recover because the message was written for engineers.
They'll figure it out
Observers note participant hesitation and attribute it to "not trying hard enough" — the same flow confused three prior sessions. Egocentric bias reframed user struggle as user fault.
09Ethical risks
Products designed from egocentric perspective systematically exclude people unlike the team — often those with less privilege, literacy, or platform fluency who cannot compensate for insider assumptions.
When egocentric bias drives accessibility and localisation deferral, exclusion is framed as focus — "our core user" — rather than acknowledged as perspective failure.
Self-test: What in your current design would fail if nobody in the room had ever seen your product before?
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.