Why Talking Less Makes People Hear You More

You're mid-sentence in a meeting, and you can see it happening. The other person's eyes have gone somewhere else. They're not listening to you anymore. They're, they're drafting their reply, quietly, in their head, while your words just sort of fall on the floor between you. And later, when the misunderstanding costs an afternoon of rework, you wonder which part of what you said failed. That's the question that actually matters, Lothar. Not whether you spoke well, but whether the listener could understand and use what you said. That idea comes straight from the CDC's plain language guidance, which defines clear communication by the audience's ability to get the message the first time they hear it. The speaker feeling clear counts for almost nothing. What gets me is how much grief this single reframe could prevent.

Think of it like handing someone a map. If the destination is buried at the bottom, they have to walk the whole thing before knowing where they're going. So put your main point first, then arrange the supporting material in whatever order helps them most. Use familiar words, and when you need a technical term, explain it instead of assuming. Prefer active voice, so it's obvious who's doing what. And keep sentences lean. CDC guidance suggests aiming for around twenty words each, one idea per sentence. Now, chunking matters too. Group related information into logical blocks with descriptive headings, because, as the CDC notes, chunking fights information overload and supports recall. Suppose you're explaining a billing error to a customer. "Your charge was wrong, here's why, here's your next step" beats five minutes of backstory every single time. That's the problem-solution-benefit pattern working: the listener knows where you're headed within the first ten seconds. State what they can actually do, not just background. A message can be brilliantly worded and still fail if nobody can find it or act on it, which is why you match format to the audience's situation and access needs.

Then there's listening, the skill nobody trains. Most of us listen to reply rather than to understand. You know the feeling. Someone's mid-story and you're holding your point like a, like a ball you're waiting to throw. Active listening means attending to their meaning instead. In practice it's small. You paraphrase their point back to them, which hands them the chance to confirm or correct your understanding. You ask open questions when you genuinely need their reasoning, their concerns, their desired outcome. And you check understanding, because silence or a nod proves nothing. I found a CDC-cited survey of emergency physicians fascinating on this. In chaotic, high-stakes rooms, the techniques a majority said they routinely used were the simple ones: plain language, and speaking slowly. Not the fancier techniques they also rated as effective, just the humble ones they could actually perform under pressure. That tells you something about where to invest your effort, Lothar.

So what about the conversations you dread? The ones where emotion runs hot. There's a hidden precondition there, and it's emotional safety, the sense that you can say something true without being attacked for it. You build it by describing observable events before interpreting motives. "The report went out with errors" is a fact. "You don't care about quality" is a conclusion wearing a fact's clothing. Separating the two prevents so much avoidable escalation. State your concern clearly and respectfully, then leave room for their perspective and for new information, because you might be wrong about part of it. Focus on the issue or the behavior, never the person's character. And when emotion spikes, pause and clarify the shared goal before trying to solve anything. Facts first, interpretations second, people always. The same discipline shapes feedback. Say something specific enough to guide a next action, not a broad label like "careless" that leaves someone wounded and no wiser.

Before you speak, try the One-Minute Map. Sixty seconds: who's the audience, what's my one point, what's the first thing they can do. That's it. It forces the structure before the words arrive. It sounds almost insultingly simple, I know. But the emergency physicians taught us that simple and slow beat clever and fast when stakes are real. The federal Plain Writing Act of 2010 even made plain language a legal duty for agencies talking to the public, on the logic that clarity is a service, not a style. Which means every confusing email you've ever sent wasn't just annoying. It was, in a small way, a failure to serve. So the next time you see those eyes drift mid-sentence, don't talk louder. Talk clearer, and listen harder. Start with the point. Say it in words they already own. And when it's your turn to listen, actually be there for it.

It's Tuesday night and you're staring at the ceiling, rehearsing tomorrow's confrontation. You've run it several times, and each version ends badly. What nobody tells you about that ceiling‑staring is that it's already a conversation, just one you're having with yourself. And the polite version of these talks, the one where you say everything is fine and hope it resolves itself, that version has a cost too. It just doesn't send you an invoice. The authors of *Difficult Conversations* describe three threads tangled together in hard talks, and I hadn't separated them before: what happened, the feelings, and what it means for who you are. That last one is why a deadline dispute can feel like your competence is on trial. So before anything else, write down what you actually hope to resolve, and what you still need to learn. Two minutes, Lothar. That's the whole preparation.

Consider a project manager whose team kept missing deadlines. Her initial move was the obvious one, the one any reasonable person would try. She marched in and said, I need you to fix this. When that failed, she tried the softer wrong answer, let's all just work harder. Both escalated the tension, and here's why. Both treated people as the problem instead of the missed handoffs, and both talked purely about tasks while ignoring that her developers felt their competence was being questioned. Ignoring emotions doesn't make them leave the room, it just makes them negotiate on your behalf, badly. If someone's sense of skill or respect feels threatened, they defend the threat, not the deadline. What gets me is that Maya wasn't wrong to be frustrated. She was just aiming it at a person instead of a pattern.

So what clicked for Maya? One distinction: position versus interest. A position is what someone says they want. An interest is the reason underneath it. Suppose your colleague demands a two‑week delay. That's the position. Ask, why does that matter to you, and you might learn their interest is avoiding a repeat of a client disaster from last year. Now you're solving the real problem. Which is why the Harvard negotiators behind this approach say to treat the issue as a shared problem, not the person as the problem. You're on the same side of the table, facing the issue together. And there's a second separation: what happened, versus what you assume they intended. The report went out late is an observable fact. They didn't care is a guess dressed as one. Ask about their intention instead of announcing your theory. Open with something neutral, like, we seem to see this deadline differently, can we compare what each of us understood? That single sentence turns an ambush into an inquiry.

Now the listening half, because this is where most tough talks die. Summarize their view and invite corrections before presenting your own. Something like, “So what I hear is, tell me where I got that wrong.” A fair summary checks your understanding and hands them a chance to correct you, which they usually take. And notice, acknowledging a concern is not agreeing with it. You can say, that deadline pressure is real for you, and still disagree about the fix. Ask open questions to surface what's underneath. What matters most to you about this? What would a workable outcome look like? There's research backing this, and it surprised me. In three negotiation studies, Adam Galinsky and colleagues found that perspective‑taking, actively working out the other side's thinking, helped negotiators find agreements and create value. Empathy alone, just feeling warm toward them, did not.

Two more pieces before the close. When emotions flare, make room for them rather than jumping to solutions, because a dismissed feeling becomes the entire agenda. And when a problem keeps recurring, look for each side's contribution to the pattern instead of assigning blame, which, honestly, rarely fixes anything twice. Then brainstorm several possible solutions before choosing one, since generating options can reveal a fix that addresses both people's interests instead of forcing a choice between two demands.

So back to Maya, because her story doesn't end with a tidy bow. When she started opening meetings with a shared goal, the project succeeding on time, and summarizing her team's view before her own, the shift was immediate, people stopped bracing for attack and started problem‑solving with her. The defensive silence lifted, ideas appeared, real ones. But whether it holds, that's still an open question, a live disagreement she and her team renegotiate each sprint. That's the honest position. Make agreements concrete: who does what, by when. And if a talk goes unproductive, pause it and agree when you'll return, not as a threat. Before your own tough conversation, rehearse it once with questions instead of speeches, and practice on low‑stakes disagreements. The talk you're dreading may not end in a win. It can end in a partnership, which is better.