Lesson 2.23 · PracticeGuide · 11 min readFree · No signup

Curse of Knowledge: experts forget what it's like not to know

Part of the Psychology of Design learning path. The cognitive biases and psychology principles behind every click, scroll, and conversion.

L2 · How people decide · Lesson 23 of 3711 min read for this one

What you'll understand by the end of this lesson

  • What the Curse of Knowledge is and why it's so hard to notice in yourself
  • Why product teams write landing pages that confuse the people they're trying to reach
  • The five-second test and what it reveals about your homepage clarity
  • How to audit your copy for knowledge gaps that your visitors can't fill

The principle in plain English

The Curse of Knowledge is a cognitive bias in which a person who knows something finds it difficult — or impossible — to imagine what it was like not to know it. They've lost access to their own ignorance.

The term was coined by economists Colin Camerer, George Loewenstein, and Martin Weber in a 1989 paper. It was popularised by Chip and Dan Heath in their book Made to Stick. The basic finding: once knowledge is in your head, it changes how you think — permanently. You can no longer accurately model how someone without that knowledge would process the same information.

In practice, this means: the people who build products write about them in ways that only make sense to people who already understand them.


A simple example

A Stanford psychology experiment asked participants to tap out the rhythm of a well-known song — Happy Birthday, say — while a listener tried to guess the song from the taps alone.

The tappers estimated the listeners would correctly identify the song 50% of the time. In reality, they got it right 2.5% of the time.

The tapper could hear the song in their head as they tapped. The listener heard only irregular clicks. The tapper couldn't imagine hearing it without the melody — so they massively overestimated how much the taps communicated.

That's the Curse of Knowledge. You know the song. Your visitor doesn't.


How product teams write confusing landing pages

When a product team writes a landing page, they know:

  • What their product does
  • Why it's better than alternatives
  • What problem it solves
  • Who the customer is
  • The terminology of their industry

The visitor knows none of this. They landed on the page five seconds ago.

The team writes: "A unified data orchestration layer for real-time customer event streaming."

The visitor reads: "?"

The team isn't being deliberately obscure. They literally cannot see the jargon any more. "Data orchestration" is the most natural description of what they built. It describes the product perfectly — to someone who already knows what it does.

The fastest fix for Curse of Knowledge in landing page copy is to describe the product to someone who has never heard of it — out loud, in a conversation. The language you use in that conversation is usually much closer to what your visitors need to read. When you write for the page, you're tempted to use formal, impressive-sounding language. When you talk, you explain.


Feature-led copy that skips the "why it matters" step

The Curse of Knowledge produces a specific copy pattern: feature-led descriptions that skip the customer benefit.

"Advanced segmentation with 200+ filters" — that's a feature. The team knows why it matters. But the visitor doesn't. What is advanced segmentation for? What does 200+ filters give me? What does this mean for my situation?

The benefit version: "Show each visitor the offer most likely to convert them — based on their location, device, visit history, and what they've already bought."

Same feature. The second version explains it to someone who doesn't already know.

The team who built the segmentation feature knows exactly what it's for. They just forgot to say it.


The five-second test

The five-second test is a quick reality check for Curse of Knowledge on a homepage or landing page.

Show the page to someone completely unfamiliar with your product for five seconds. Then take it away. Ask them:

  • What does this product or service do?
  • Who is it for?
  • What's the main thing they're being asked to do?

If they can answer those three questions clearly, the page is communicating without relying on pre-existing knowledge. If they can't — if the answer is vague, confused, or "I'm not sure" — the Curse of Knowledge is active and the page is assuming too much.

The Curse of Knowledge is nearly impossible to detect in your own writing because, by definition, you can't see what you don't know you're assuming. This is why user testing, outside reviewers, and structured five-second tests are the only reliable way to catch it. Reading your own copy more carefully won't help — you'll see what you meant to say, not what's actually there.


The value proposition test

A harder version of the five-second test: send your homepage URL to a friend who works in a completely different industry. Ask them to read only the hero section and then explain what the product does and who it's for — in their own words.

If their explanation is accurate, your value proposition is clear.

If their explanation is wrong, vague, or "I'd have to read more to understand," your hero section is cursed. The people who wrote it knew too much to see what was missing.


The CRO audit

1. Apply the five-second test to your homepage hero.

Show it to someone outside your company for five seconds. Their answers to "what does this do / who is it for" are the only feedback that matters.

2. Find three feature descriptions on your landing page. Add the "which means" step.

Take any feature claim and add: "…which means [benefit for the user]." If you can't complete that sentence clearly and quickly, the feature description is cursed — it's written for people who already know what it means.

3. Read your homepage copy as if you arrived with zero context.

Force yourself to read only the words on the page — not the words you intended. Ask for each sentence: would someone reading this for the first time understand it? Not "could they eventually figure it out" — would they understand it on first read?



Q1

A SaaS homepage hero reads: 'Real-time event-driven infrastructure for composable commerce experiences.' After a five-second test, none of the test participants could explain what the product does. What's the diagnosis?

Think about this

You've seen how knowledge creates a blind spot in communication. Now — what happens at the exact moment a user finally gets it? There's a specific instant when a product clicks into place, and the time it takes to reach that moment predicts retention better than almost anything else.