In 1990, a Stanford graduate student named Elizabeth Newton ran an experiment so simple it sounds like a party game. She split people into two roles. Tappers picked a well-known song, something like “Happy Birthday,” and tapped the rhythm on a table with their fingers. Listeners tried to name the tune. Before each round, Newton asked the tappers to predict how often the listeners would get it right. The tappers guessed about 50 percent.

The real number was 2.5 percent. Listeners named the song correctly in roughly one out of every 40 attempts, while the tappers were sitting there convinced half the room would nail it.

That gap between 50 percent and 2.5 percent is the single best explanation I know for why your team keeps misunderstanding you. The tappers could hear the full song playing in their heads. The listeners heard a series of disconnected knocks. And once you know the song, you literally cannot un-hear it. You have lost the ability to imagine what the taps sound like to someone who does not.

Psychologists call this the curse of knowledge. The term was coined in a 1989 paper by economists Colin Camerer, George Loewenstein, and Martin Weber, and it describes a specific failure: once you know something well, you can no longer accurately model what it is like to not know it. For managers, this is not an abstract cognitive quirk. It is the reason your “obvious” instructions land as confusion, and the reason you are usually the last person in the building to realize it.

Why the people who understand the work best explain it worst

Here is the uncomfortable part. The curse of knowledge gets stronger the more expertise you have, not weaker. The engineer who built the system is the worst person to write its documentation. The finance lead who lives in the model is the worst person to explain the forecast to the sales team. And the manager who has been doing the job for fifteen years is often the worst person to onboard someone who started Monday.

You are not tapping a song. You are briefing a project, describing a priority, or explaining why the plan changed. But you are doing exactly what the tappers did: hearing the full context in your head, and assuming the other person hears it too. They do not. They hear the knocks.

I watched this play out during a system rollout years ago, back in my IT operations days. I had a technical lead who understood the migration better than anyone. When he briefed the frontline team, he used the internal project names, referenced decisions made in meetings the team had never attended, and compressed six weeks of his own thinking into a four-minute update. He walked out certain the team was aligned. Half of them came to me within the hour asking what he actually wanted them to do. He was not a bad communicator in any general sense. He was cursed by how well he knew the material.

The gap you cannot feel is the expensive one

The problem with the curse of knowledge is that it is invisible from the inside. Nobody experiences themselves as unclear. When Axios HQ surveyed leaders and employees for its 2025 State of Internal Communications report, 80 percent of leaders said their communications were clear and engaging. Only 50 percent of employees agreed. That 30-point gap is the tappers all over again, scaled up to the entire org chart. Leaders grade their own clarity from inside their own heads, where every message makes perfect sense.

The cost is not just hurt feelings in a meeting. Grammarly and the Harris Poll estimated that poor communication costs U.S. businesses up to $1.2 trillion a year, and the Society for Human Resource Management has cited analyses putting the price at roughly $420,000 per year for a company of 1,000 people. Those numbers are built from rework, missed deadlines, duplicated effort, and work that gets done wrong because the instructions only made sense to the person giving them. Every one of those failures started with someone who was sure they had been clear.

How to tell you are tapping when you think you are talking

You will not catch this by trying harder to be clear. Effort is not the missing ingredient. The tappers were trying hard, and they were tapping with real conviction. You catch it by watching for specific tells in your own behavior.

You use words like “obviously,” “just,” and “simply.” When you say “just push it to staging and it’ll be fine,” the word “just” is doing a lot of hiding. It compresses five steps you know by heart into one word the other person has to unpack.

You reference context the other person was not in the room for. Decisions, prior conversations, the reason a thing is set up the way it is. In your head it is all one connected story. To them it is a knock with no melody.

You explain the what and skip the why. You know why the priority changed, so the change feels self-explanatory. To the team, an unexplained change feels arbitrary, and arbitrary instructions get followed slowly and grudgingly if at all. This is the whole argument for leading with intent instead of instructions, which I have written about in giving your team the destination instead of the directions.

You finish a briefing and ask “does that make sense?” and take the nods as confirmation. Nods are not comprehension. Nobody wants to be the person who admits they got lost in minute two.

What I do before I explain anything that matters

Chip and Dan Heath built an entire book, Made to Stick, around beating this exact bias. They call the curse of knowledge the “archvillain” of ideas that fail to land, and their core prescription is concreteness. Abstract statements live comfortably in the expert’s head. Concrete ones survive the trip to someone else’s. Here is what that looks like in practice for a manager.

Name one real example instead of describing the category. “Make the report more customer-friendly” is abstract and will come back wrong. “Cut the three internal acronyms out of the summary and put the total refund number in the first line, the way the March report did” is concrete, and it travels. The Heaths found the same thing Newton did: stories and specifics carry across the gap that abstractions cannot.

Ask the person to tell you back what they are going to do, in their own words. Not “does that make sense,” which invites a reflexive yes, but “walk me through how you’ll start.” The moment they paraphrase, the gap becomes visible. If they reconstruct your song, you were clear. If they hand you a different tune, you just saved yourself a week of rework. I do this on anything that matters, and it has caught more misunderstandings than any other single habit.

Strip the jargon you have stopped noticing. Every team develops shorthand, and shorthand is efficient right up until it is a barrier. New people, cross-functional partners, and your own boss’s boss often do not share it. Read your message and flag any term that would need a footnote for someone outside your immediate circle.

Explain the why before the what. Thirty seconds on the reasoning behind a decision does more for execution than five minutes of detailed instructions, because a team that understands the intent can adapt when reality does not match the plan. This is also why clear direction and micromanagement are opposites, not neighbors: intent gives people room to think, while instructions without intent force them to guess.

Assume the taps, not the song. This is the mindset shift underneath all the tactics. Walk into every important explanation assuming the other person is hearing knocks, not the melody in your head. That assumption is almost always closer to the truth than the confident 50 percent your brain wants to guess.

The manager who explains well is not the smartest one

There is a myth that the clearest communicators are the ones who understand the material most deeply. The tapping study says the opposite. Deep knowledge is what builds the curse. The managers I have watched communicate best over 25 years are not the ones who know the most. They are the ones who have never quite trusted their own sense of being clear, so they check. They ask for the read-back. They lead with why. They notice when they have said “obviously” and stop to unpack it.

That habit of doubt is a skill, and like any communication skill it compounds the longer you practice it. You will not eliminate the curse of knowledge. It is baked into how expertise works, and the better you get at your job, the louder the song plays in your head. What you can build is the discipline to remember that nobody else can hear it, and to keep checking whether the taps you are sending actually add up to the tune you mean.

Your team is not slow. They are listening to knocks and doing their best to guess the song. The fix is not to tap harder. It is to hum a few bars out loud.