top of page

You Know Too Much to Explain It: How the CHANGE Framework Breaks the Curse of Knowledge

6 days ago
5 min read

You explained it twice. They nodded both times. Then the work came back wrong.

Your first thought might be, They weren’t listening. Maybe. But there’s another likely explanation: you skipped four steps because they felt too obvious to say out loud.

That’s the curse of knowledge. Once you know something, it’s hard to imagine not knowing it. You hear the whole song in your head, even when the other person only gets a few taps.

Listen: Brad Young's CHANGE puts communication first among its six pillars for a reason. Knowing more than the person in front of you isn’t the problem. Failing to translate is.

Why knowledge gets in the way

In a 1990 Stanford doctoral dissertation, Elizabeth Newton studied what happens when people try to communicate a familiar song by tapping it. Tappers predicted that about half of listeners would identify the song. In fact, listeners named just 3 of 120 songs, about 2.5 percent.

The tapper hears the melody in their head. The listener hears tapping.

It’s a memorable demonstration, not a universal law: it was one task, in a doctoral dissertation, with a small sample. It doesn’t prove your coworker is blameless. It does show that your instructions can feel much more self-explanatory from the inside than they sound to someone else.

A split image showing a dense tangle of lines on the left and one simple line on the right

The problem also shows up when people have a reason to adjust their perspective. In a 1989 paper in the Journal of Political Economy, Colin Camerer, George Loewenstein, and Martin Weber found that better-informed people struggled to set aside private information when predicting what less-informed people would know, even when doing so would have benefited them. Market competition cut the bias roughly in half, but didn’t eliminate it.

That’s evidence that the bias can persist even when incentives push people to account for it, not a measurement of your team. The researchers used lab markets, student participants, and simplified assets. The useful takeaway is modest: having a reason to communicate better doesn’t automatically make you good at it.

Writing has its own version of the problem. In a 2006 paper, psychologist Daniel Oppenheimer found that writers who used needlessly long words were judged less intelligent, not more. The effect was linked to how hard the text was to process.

The caveat matters: the studies involved student participants and short writing samples, and the finding concerns needless complexity. It does not mean you should avoid every technical term. Keep a precise term when it carries meaning your audience needs. Just don’t use complexity as decoration.

What it costs at work

The cost often looks ordinary: onboarding takes three weeks longer than it should. A client chooses the competitor who explained the service more simply. Someone gets a handoff, rebuilds the work, and gets it wrong. A meeting reaches the real decision only after everyone has waded through familiar shorthand.

That’s a business problem, not just a style preference. A good decision that can’t be explained in plain language may not survive contact with the people who have to execute it. That’s one reason clear communication belongs in any serious conversation about Business Decision Making and business growth: the decision is only as good as the number of people who can act on it correctly.

The Translation Pass: four moves to make your point land

A hand draws a three-step diagram on a whiteboard, with one step circled in orange

1. Name the invisible list. Before you explain, write down three to five things you’re assuming the other person already knows. Then decide which ones need saying out loud. Maybe they don’t know who approves the request, what “ready” means, or where the latest file lives.

2. Replace one abstraction with one concrete instance. “We need better alignment” sounds reasonable, but it leaves the next step unclear. Try one of these instead:

  • “Let’s get on the same page about the launch” becomes “Let’s agree who approves the final email by Thursday.”

  • “We need to tighten up the process” becomes “Let’s decide who checks the figures before the report goes to the client.”

  • “The project is at risk” becomes “We’re waiting on the supplier’s confirmation, so the delivery date may move.”

3. Use the rebuild test. Ask the person to explain the plan back in their own words. If their version is garbled, treat that as information about your explanation, not their ability. “Does that make sense?” often earns a polite nod without telling you what they understood.

4. Compress first, expand on request. Start with one sentence. Add layers when the listener needs them. People can ask for the second layer when they’re ready for it.

Four moments to try it

Delegating at work: Instead of “Can you handle the client follow-up?” say, “Please email Maya by 2 p.m. today, ask whether the revised timeline works, and copy me on the reply.”

Explaining a product or service: If your customer isn’t in your industry, trade internal shorthand for an outcome: “This gives your team one place to review and approve each invoice before it’s paid.”

Onboarding a new hire: Don’t assume “use the standard workflow” tells them what to do. Try: “Open the shared project board, find the card marked ‘New,’ and add the customer’s deadline before assigning an owner.”

Explaining a plan or health situation to family: “I’m waiting to hear from the specialist, and I’ll share the next steps after the appointment.” With medical or financial information, plain language doesn’t mean vague language. Say the numbers and risks clearly, and ask a qualified professional to explain anything you’re unsure about.

Traps to avoid

Don’t simplify until it becomes condescending. The goal is to remove missing steps, not talk down to someone.

Don’t decide jargon is always bad. When a team shares a term and it saves time without hiding meaning, it can be useful shorthand.

Don’t assume the curse only affects other people. Expertise makes your own gaps harder to spot, too.

And watch out for the sentence “I already explained that.” It might be true. But said in frustration, it can sound like a verdict on the listener instead of a reason to try a clearer explanation.

How the CHANGE pillars support better communication

Communication is the translation itself: shaping what you know so another person can understand and use it, without assuming they share your context.

Habits matter because brevity and plain language aren’t talents you either have or don’t. They’re habits you can practice, especially when you pause to name what you’ve assumed.

Attitude changes what happens when someone doesn’t get it. Curiosity gives you a chance to find the missing step. Irritation tends to repeat the same explanation louder.

Network grows through trust and follow-through. Plain language makes you someone other people can understand, ask questions of, and actually work with.

Goals need to be shareable. If nobody else can restate what you’re trying to achieve, it’s a goal you’re carrying alone.

Education isn’t only passing on information. Teaching is a test of your own understanding: if you can explain an idea clearly, you’ve found a way to make your knowledge useful to someone else.

Six geometric pillar blocks in a row, with one bright yellow block against deep blue

Try a seven-day practice

Once a day, explain one thing you know well to someone outside your field. Give yourself sixty seconds, then ask them to teach it back in their own words. Notice the exact spot where it broke: a missing step, an unfamiliar term, or an assumption you didn’t realize you were making.

By day four, you’ll likely see a pattern in your own explanations. That’s something you can work with.

You can’t un-know what you know, but you can translate it, and translation is a learnable skill rather than a personality trait. Start with the next explanation you have to give today: name what you’re assuming, say the missing step out loud, and ask for the rebuild. Change is something you create, and the first translation is the one where you stop assuming the other person can hear the song.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page