cognitive biasteachingexpertiselearning design

The Curse of Knowledge: Why Experts Make Terrible Teachers

V. Zhao V. Zhao
/ / 4 min read

The Curse of Knowledge: Why Experts Make Terrible Teachers

3D illustration of a scale balancing truth and fake news concept against a blue background. Photo by Hartono Creative Studio on Pexels.

Have you ever watched a brilliant programmer explain their code to a junior developer, only to see confusion spread across the newcomer's face? The expert rattles off assumptions about data structures, references design patterns without explanation, and skips over what they consider "obvious" steps. Meanwhile, the learner drowns in unstated context.

This isn't a character flaw. It's the curse of knowledge—a cognitive bias that makes it nearly impossible to remember what it was like before you understood something deeply.

What Makes the Curse So Powerful

Once you master a domain, your brain reorganizes information into efficient chunks. A chess grandmaster sees patterns where beginners see individual pieces. A mathematician recognizes theorem applications that students miss entirely. This chunking process is what enables expertise, but it also erases the memory of not knowing.

Psychologist Elizabeth Newton demonstrated this beautifully in her "tapping" experiment. She asked people to tap out familiar songs with their fingers while others tried to guess the tune. The tappers predicted listeners would identify 50% of songs correctly. The actual success rate? Just 2.5%. The tappers couldn't unhear the melody in their heads, even though they were only producing rhythmic taps.

Experts face the same challenge when teaching. They can't unhear their internal knowledge symphony.

The Expert's Teaching Traps

graph TD
    A[Expert Knowledge] --> B{Teaching Attempt}
    B --> C[Assumes Background Knowledge]
    B --> D[Skips "Obvious" Steps]
    B --> E[Uses Advanced Vocabulary]
    C --> F[Student Confusion]
    D --> F
    E --> F
    F --> G[Learning Breakdown]

When experts teach, they typically fall into three traps:

The Assumption Trap: They assume students share their foundational knowledge. A database expert might casually mention "normalization" without explaining what it means or why it matters.

The Compression Trap: Years of practice have compressed complex processes into single mental operations. What once took deliberate thought now happens automatically—and that automatic processing becomes invisible to the expert.

The Vocabulary Trap: Domain-specific language becomes second nature. Terms that once required careful explanation now feel as basic as saying "chair" or "window."

Breaking Free From the Curse

Recognizing the curse is the first step. Actually overcoming it requires deliberate strategies:

Map the journey backward. Start with where students are, not where you want them to end up. Before explaining recursion, ask: what do they already know about functions? About loops? What mental models can you build upon?

Expose your thinking process. Narrate the internal monologue that expertise has made silent. Instead of jumping to the solution, walk through the reasoning steps that led you there.

Find the gaps in "obvious" knowledge. What seems self-evident to you might be a massive conceptual leap for learners. Test your assumptions by asking students to explain concepts back to you in their own words.

Use beginner vocabulary deliberately. Reserve technical terms for after you've built understanding with plain language. Don't say "let's implement polymorphism"—say "let's make different objects respond to the same command in their own way."

The Beginner's Mind Advantage

The most effective technical educators often aren't the deepest experts—they're people who recently made the learning journey themselves. They remember the confusion, the false starts, the moments when concepts finally clicked.

This suggests a counterintuitive strategy: rotate your teaching responsibilities. Let someone who learned React last year teach it to newcomers, while the React expert focuses on advanced optimization techniques.

Some organizations have discovered this accidentally. When senior engineers are too busy to onboard new hires, mid-level developers step in—and often do a better job explaining the basics.

Your Next Teaching Opportunity

The next time you need to explain something you know well, try this experiment: before you start, write down five things a beginner might find confusing about your explanation. Then address each one explicitly.

You might discover that your expertise, while deep, has created blind spots you never knew existed. The curse of knowledge is real—but awareness of it is the first step toward becoming the teacher your past self needed.

Get Grok Guide in your inbox

New posts delivered directly. No spam.

No spam. Unsubscribe anytime.

Related Reading