In 1990, a Stanford PhD student named Elizabeth Newton ran one of the most elegant experiments in psychology.
She asked people to tap out well-known songs — "Happy Birthday," "The Star-Spangled Banner" — on a table. Listeners had to guess the song from the taps alone.
The tappers predicted listeners would get it right 50% of the time.
The actual success rate? 2.5%. Three out of 120.
The tappers couldn't believe how badly listeners failed. The melody was so obvious. How could anyone miss it?
That's the problem. When you know the melody, you literally cannot imagine not knowing it. The song plays in your head while you tap. But the listener only hears disconnected knocks on a table.
This is the Curse of Knowledge — and it's destroying your documentation.
The Research Is Clear (And Depressing)
The term was coined by economists Camerer, Loewenstein, and Weber in 1989 (Journal of Political Economy). Their key finding: better-informed agents are unable to ignore private information, even when it's in their interest to do so [1].
Financial incentives didn't fix it. Telling people about the bias didn't fix it. Market forces reduced it by about 50%, but never eliminated it.
Nothing currently tested reliably eliminates this bias.
In 1999, Stanford researcher Pamela Hinds tested this directly with technology. She asked cell phone salespeople, intermediate users, and total novices to predict how long it would take a new user to learn a phone [2].
- Actual novice learning time: ~30 minutes
- Expert (salesperson) prediction: less than 13 minutes
Experts underestimated difficulty by more than 2x. They were resistant to debiasing techniques.
Here's the kicker: intermediate users — people with some but not expert-level knowledge — were the most accurate predictors. Not the experts. The people who knew the most about the product were the worst at understanding what new users would struggle with.
Your Documentation Has This Problem
Every founder, every product expert, every senior developer writes documentation that skips "obvious" steps.
They skip those steps because they can't remember a time when those steps weren't obvious.
Birch and Bloom confirmed in 2007 (Psychological Science) that this isn't a maturity or intelligence issue — adults show the same curse-of-knowledge bias as children [3]. The bias operates through "fluency misattribution": information that feels easy to YOU feels like it should be obvious to EVERYONE.
A 2022 study in Memory & Cognition confirmed the bias is extraordinarily robust: awareness doesn't reduce it, financial incentives don't reduce it, and asking people to "try harder" to take the other perspective doesn't reduce it [4].
The Numbers Behind the Knowledge Gap
The organizational research is stark:
- 42% of expertise in any role is sole-sourced — only one person knows it
- 90% believe retirements cause significant knowledge loss, even WITH transfer policies
- Documents written in plain language are 47% easier to understand (Plain Language Association International)
- 83% of developers report frustration with insufficient or poorly structured documentation
- It takes up to 2 years to bring a new hire to a predecessor's efficiency level
- Turnover costs up to 213% of an employee's salary
The expert documentation paradox:
| Who Knows Most | Who Explains Best | |---|---| | The founder | A recent customer | | Senior developers | Junior devs who just learned | | Sales engineers | Recent converts |
The people best positioned to document are the worst at it.
Your Nervous System Feels This
The curse creates a feedback loop that affects everyone's stress levels.
The expert writes documentation. The documentation fails because it skips "obvious" steps. Customers can't follow it. They contact the expert. The expert gets interrupted. Each interruption triggers a cortisol response. Over time: lower HRV, worse communication, worse documentation.
Meanwhile, the customer feels anxious ("I can't figure this out"), frustrated ("there must be an answer somewhere"), and eventually defeated ("I'll just ask"). Their sympathetic nervous system activates from the same curse that activated the expert's.
Both parties are stressed by the same cognitive bias. The expert thinks "I already explained this." The customer thinks "this doesn't explain anything."
Research shows that chronic stress from interruptions suppresses HRV (allostatic load correlates r = -0.67 with total HRV) [5]. The curse of knowledge doesn't just waste time — it degrades autonomic health on both sides of the support conversation.
What Actually Breaks the Cycle
Since awareness and incentives don't work, what does?
Systems that start from confusion, not from knowledge.
- Start from customer questions, not expert knowledge. Your support tickets tell you exactly what's confusing. Your FAQ videos should answer those questions, not explain what experts think is important.
- Use intermediate users to create content. Hinds' research shows people with SOME knowledge predict novice struggles better than experts. Your most recent customer understands your next customer better than you do.
- Test with real beginners. Give your documentation to someone who's never used your product. Time them. Watch where they get stuck. Those stuck points are the curse revealing itself.
- Record video instead of writing text. Video captures context, facial expressions, and pacing that experts unconsciously omit from written docs. When you record yourself doing a task, you naturally include steps you'd skip in writing.
- Build systems, not documents. A one-time documentation effort reflects the expert's knowledge at one point. A system that continuously captures customer confusion and turns it into self-service content breaks the curse repeatedly.
The curse of knowledge isn't something you overcome through willpower. It's a structural cognitive bias confirmed across decades of research. The only reliable fix is building infrastructure that captures confusion from the customer's side and converts it into clear, tested education.
Your experts can't write good documentation. That's not a character flaw — it's how human cognition works.
Build systems that work around it.
---
Sources:
[1] [Camerer, Loewenstein & Weber (1989). The Curse of Knowledge in Economic Settings. Journal of Political Economy.](https://www.cmu.edu/dietrich/sds/docs/loewenstein/CurseknowledgeEconSet.pdf)
[2] [Hinds, P. J. (1999). The Curse of Expertise. Journal of Experimental Psychology: Applied, 5, 205-221.](https://www.researchgate.net/publication/232555027ThecurseofexpertiseTheeffectsofexpertiseanddebiasingmethodsonpredictionofnoviceperformance)
[3] [Birch, S. A. J. & Bloom, P. (2007). The Curse of Knowledge in Reasoning About False Beliefs. Psychological Science, 18, 382-386.](https://journals.sagepub.com/doi/10.1111/j.1467-9280.2007.01909.x)
[4] [The "curse of knowledge" when predicting others' knowledge. Memory & Cognition (2022).](https://pmc.ncbi.nlm.nih.gov/articles/PMC9794110/)
[5] Allostatic load and HRV correlation. PMC5637028. accessibility.link.new-tab