Why Your Explanation Makes Sense Only to You

“Use the newer version” sounds clear when you know which file was revised yesterday. Someone else sees three files, two with “final” in the name. An explanation can feel complete because you supply its missing context automatically. The listener cannot necessarily do that.

Before making your explanation longer, check what your words require the other person to already know.

Speakers don’t always know when they were clear

In experiments by Boaz Keysar and Anne Henly, speakers communicated ambiguous sentences with an intended interpretation. They predicted whether listeners would understand. Speakers overestimated their effectiveness; overhearers given the relevant context did not show the same systematic overestimation.

The task involved controlled sentence ambiguities, not every kind of workplace or family conversation. It supports a narrower point: feeling clear as the speaker is an imperfect check on whether the meaning reached someone else. It doesn’t establish that the listener is careless or that you are a poor communicator generally.

That distinction matters when a misunderstanding becomes an argument about who should have understood. You can inspect the reference that failed without deciding whose personality caused it.

Find the word that depends on private context

Consider these ordinary instructions:

• “Put it where it usually goes.”
• “Send her the updated one.”
• “Let’s move the meeting forward.”

Each may work between people who share the relevant habits. Each can also fail. What is “it”? Who is “her”? Does “forward” mean earlier or later?

Adding a reason may leave the ambiguity untouched: “Move the meeting forward because the deadline changed.” The reason helps explain the decision, but it still doesn’t name the time.

Try: “Can we meet Thursday at 2 p.m. instead of Friday at 2 p.m.?” That gives the listener a proposal they can confirm or correct.

Ask about the action, not your performance

“Was that clear?” is easy to answer politely. For something consequential, state the intended result: “I’m expecting us to use the October 8 proposal for tomorrow’s call. Is that the version you have?”

This lets the other person reveal a different file or understanding. It also makes correction mutual. Perhaps you missed the newer version they received that morning.

Our article on asking useful follow-up questions explores that attention to what the other person actually knows. Avoid turning a routine exchange into a comprehension test or asking someone to repeat everything you say.

A private rehearsal needs a listener’s perspective

Speaking an explanation aloud can help you notice an unfinished thought. It cannot, by itself, prove that someone else will understand. You still know the answer while you rehearse.

If you record a private draft in Lound, read its transcript looking specifically for unnamed people, unspecified dates, and phrases such as “the usual way.” Pick the missing detail that matters. Don’t add an autobiography to every instruction.

The same problem appears when your own notes stop making sense later. Your future self no longer has all the context you had when writing. A file name or a concrete next action often ages better than “sort that out.”

Know when to stop explaining

Once you share the necessary context, disagreement can remain. Someone may understand the proposal and not want it. More explanation cannot guarantee agreement, and treating resistance as confusion can make the conversation worse.

As the guide to overexplaining and clarity discusses, length is a poor substitute for finding the actual question. Check the referent, invite a correction, and then listen for whether the unresolved issue is meaning, feasibility, or preference.