The Curse of Knowledge: Why Experts Are Hard to Understand

Choose a song you know well and tap its rhythm on a table.

Now ask someone else to guess the song.

As you tap, the melody will play clearly inside your head. You may feel that the answer is obvious. The listener hears only a disconnected series of taps.

In a well-known experiment, tappers expected listeners to identify the song about one time in two. The actual success rate was closer to one in forty.

This difference captures one of the most common communication problems at work. Once we know something, we find it difficult to imagine what it feels like not to know it.

This is called the curse of knowledge.

Key insight: What feels obvious to the speaker may be completely unavailable to the listener. The missing information is playing inside the speaker’s head.

Expertise can make communication harder

As people develop expertise, knowledge becomes organized into familiar patterns. They no longer need to consciously think through every basic step.

This efficiency helps experts perform their work, but it creates a communication problem. They may skip context, use unfamiliar language or assume that the listener can see connections that have taken them years to learn.

The problem appears when:

• A technology team explains a new system to employees
• Finance presents performance data to other functions
• A senior leader communicates a strategic change
• HR launches a new policy or process
• A trainer explains a familiar framework

When listeners look confused, the expert may conclude that they were not paying attention. The speaker rarely notices how much knowledge was assumed.

Clarity is the explainer’s responsibility

Far too often, we transfer the responsibility for understanding to the listener.

We think, “I explained it clearly. They simply did not understand.”

But a brilliant idea has limited value if the intended audience cannot follow it. Before communicating something complex, the explainer should ask:

• What does this audience already know?
• Which terms will be unfamiliar?
• Why should they care about the idea?
• What context is necessary?
• Which details can be removed?
• What action should follow?

Key insight: The aim of communication is not to display everything the speaker knows. It is to help the listener understand what matters.

Concrete language defeats abstraction

Abstract words can sound impressive while creating different pictures in each person’s mind.

Consider a message such as, “We need greater agility and stronger stakeholder alignment.” Employees may agree while remaining unsure about what to do.

A concrete version might say:

“Before finalizing a customer decision, speak to the two teams responsible for implementing it.”

The second version gives the idea a visible action.

Stories can also make complicated information easier to understand. A story gives the listener a person, situation and consequence. Instead of processing a definition, the brain can imagine what happened.

This is why people often remember a relevant customer story long after forgetting the slide that contained six principles.

Give people a reason

The copy-machine study provides another useful lesson about workplace communication.

In the experiment, a person attempted to move ahead in a photocopier queue using different requests. A simple request received much lower agreement than a request containing the word “because.” Surprisingly, even a weak reason increased compliance.

The result does not mean that any meaningless explanation will always persuade people. It demonstrates how strongly we look for a reason behind a request.

Compare these messages:

• “Please complete this form today.”
• “Please complete this form today because payroll needs the information before processing begins tomorrow.”

The second message helps the employee understand why the timing matters.

Replace “urgent” with a real deadline

“Please respond urgently” feels clear to the sender. It is not clear to the receiver.

Urgent could mean ten minutes, two hours or the end of the day. The word provides emotion without a shared time anchor.

A better request would say:

“Please respond by 4 PM on Thursday so I can include your input in the client presentation.”

The message provides a deadline and a reason.

Clear requests should usually answer:

• What needs to be done?
• Who needs to do it?
• By when?
• Why does it matter?

Talking more can reduce understanding

When an idea is misunderstood, our instinct is often to explain it again using more words.

But listening requires mental effort. As the speaker continues, the listener must store new information while trying to connect it with what came earlier.

One of your posts uses a simple traffic-light test:

• The first 20 seconds are generally safe.
• Between 20 and 40 seconds, the risk of losing attention increases.
• After 40 seconds, it may be time to pause.

This is not a rigid speaking rule. It is a useful reminder to check whether the other person is still following.

Silence can help. Pausing for a few seconds gives both people time to process the idea and move beyond their automatic response.

A practical clarity check

Before sending an important message or presenting an idea, ask:

• Can I explain the main point in one sentence?
• Have I used any term the audience may interpret differently?
• Is there a concrete example?
• Have I explained why the request matters?
• Is the desired action specific?
• Have I left space for questions?

The Nudgeable Actions Engine can extend communication training by helping participants practise actions such as replacing abstract language, giving a specific deadline or asking the listener to summarize what they understood.

The listener cannot hear the song playing inside your head. Good communication begins when you stop assuming that they can.