Skip to content

Over-Communicate, and Tailor the Message

Written vs Verbal, Sync vs Async showed you how to pick the right channel for a message. This closing page of the part answers a different question: how many times do you send that message, and does it arrive the same for everyone? The honest answers are: far more times than you think, and no.

This is the page where communication stops being about a single well-crafted message and becomes about the long, patient work of making something stick across a whole group of people. Two ideas do most of that work: over-communicate — say the important things again and again — and tailor — reshape the same core point for whoever is receiving it. Together they are how a direction in your head becomes a direction the whole team actually shares.

The principle: a message sent is not a message received

Section titled “The principle: a message sent is not a message received”

The mistake underneath almost every communication failure is quiet and reasonable-sounding: I said it, so they know it. You announced the priority in Monday’s meeting. You wrote the plan in the doc. As far as your memory is concerned, the information has been delivered — filed, done, understood.

But delivery and reception are two different events, and the gap between them is enormous. People miss messages (they were out, distracted, or the message was buried under forty others). People forget messages (a thing said once in March is gone by April). And people misinterpret messages (they heard your words through their own assumptions and arrived somewhere you never intended). You did your part perfectly and the message still didn’t land — because landing was never in your control.

So the first-principles reframe is this: your job is not to send the message once; it’s to make sure it has actually arrived. And since you can rarely verify that directly across a whole group, the practical proxy is repetition. You say it enough times, in enough ways, that the odds of it landing approach certainty.

Why it feels repetitive to you and fresh to them

Section titled “Why it feels repetitive to you and fresh to them”

Here is the trap that stops most managers from over-communicating: by the time you say something the third time, you are sick of it. You’ve thought about this priority for weeks. You said it in the all-hands, wrote it in the plan, mentioned it in three one-on-ones. Saying it again feels condescending, like you’re treating grown adults as if they can’t listen.

But you are measuring repetition from your seat, where you’ve encountered the message dozens of times. Your team encounters it far less often, scattered among everything else competing for their attention. What is the tenth time for you may genuinely be the first time it lands for a given person — the first time they weren’t distracted, weren’t buried, actually connected the words to their own work.

The rule that follows: repeat the things that matter most until you’re tired of hearing yourself, and then keep going a little longer. The discomfort you feel is not a signal you’re overdoing it. It’s a signal you’ve finally said it enough times that you have absorbed it — which is roughly the point where the group is starting to.

What to repeat: direction, priorities, and the ‘why’

Section titled “What to repeat: direction, priorities, and the ‘why’”

Over-communicating does not mean repeating everything. Most information is one-time and disposable — a meeting time, a link, a small fact. Repeating those just creates noise. What deserves repetition is the small set of things that orient people’s daily choices:

  • Direction — where the team is going and what “good” looks like when it arrives.
  • Priorities — what matters most right now, especially what to do when two good things conflict (ship fast or polish; volume or care).
  • The ‘why’ — the reason behind the direction, so people can make good calls in situations you never anticipated.

These are the things people quietly drift from. Not out of defiance — drift is the natural state. Without repetition, the day-to-day pressure of small decisions slowly pulls everyone back toward their own local priorities. Repeating the direction, priorities, and why is how you counter that drift. You’re not informing people; you’re re-orienting them, over and over, like nudging a boat back on course.

What to over-communicate (repeat, over time, across channels):
• Direction "here's where we're headed"
• Priorities "here's what wins when things conflict"
• The 'why' "here's the reason, so you can decide without me"
What NOT to repeat (say once, cleanly):
• One-off facts, times, links, small logistics

The mechanics matter too: repeat across channels and across time. Say it in the team meeting, then write it in the weekly update, then reinforce it in a one-on-one, then point back to it when a relevant decision comes up. Each channel reaches people the others missed, and each pass over time fights the forgetting.

Tailoring: the same message, reshaped for the listener

Section titled “Tailoring: the same message, reshaped for the listener”

The second half of the skill is that the same core message should not sound the same to everyone. Different audiences need a different frame, a different level of detail, and a different answer to “why should I care?” — even when the underlying fact is identical.

Take one real message: “We’re delaying the launch by two weeks to fix a data problem.” Watch how it should change shape depending on who’s listening.

Core fact: launch delayed two weeks to fix a data problem.
To an ENGINEER:
"The customer records have duplicate entries from the old import.
We need two weeks to de-dupe and add a validation check so it
doesn't recur. Here's the ticket."
→ frame: the technical cause + what to do. High detail. Their job.
To an EXECUTIVE:
"We're pushing launch two weeks. There's a data-quality issue that
would show customers wrong information — shipping it would cost us
trust and support load. Two weeks fixes it properly."
→ frame: business impact + risk + cost. Low detail. Their decision.
To a CUSTOMER:
"We're taking a little extra time to make sure your information is
accurate before launch. New date is the 24th — thanks for your
patience."
→ frame: what it means for them + reassurance. Minimal detail.

Same fact, three messages. The engineer needs the cause and the task. The executive needs the impact and the trade-off, not the technical mechanics. The customer needs to know what it means for them and to feel taken care of — they neither want nor need the words “duplicate entries.” Tailoring is not spin or telling people different things; the truth is constant. You’re changing the frame and the detail so the one truth actually lands for each listener.

Repeat what matters — without becoming noise

Section titled “Repeat what matters — without becoming noise”

Over-communication has an opposite failure, and it’s just as real: flooding people until nothing gets through. If you repeat everything — every update, every thought, every minor change, all at high volume across every channel — you train people to tune you out. When the genuinely important message finally comes, it arrives in the same undifferentiated stream as the noise, and drowns.

So the two ideas of this page live in tension, and holding that tension is the actual skill:

  • Over-communicate the few things that matter — direction, priorities, the why — deliberately and repeatedly.
  • Ruthlessly reduce everything else — say small things once, cleanly, and let them go.

The signal-to-noise ratio is what protects your important messages. Every low-value message you don’t send makes your high-value repeated ones stand out more. Over-communication is not about volume; it’s about redundancy on the things that count. A leader who repeats three things all quarter is heard. A leader who repeats three hundred is background hum.

Pick the single most important thing your team should know right now — one direction, priority, or “why.” This week, deliver it deliberately through at least three channels (say it in a meeting, write it in an update, reinforce it in a one-on-one), and each time include the reason, not just the instruction. Then take one specific message you’ll send this week and write it two ways for two different audiences before you send it — notice what context you’d have left out that only lives in your own head.

  1. What’s the one message you most want your team to have internalized — and how many times, honestly, have you actually said it out loud to them?
  2. When you feel that “I’ve already said this” reluctance, whose experience are you measuring the repetition from — yours, or the person hearing it for maybe the first time?
  3. Think of a recent message that didn’t land. Was it missed, forgotten, or misinterpreted — and what would have caught that failure?
  4. Pick something you explained recently. What context, jargon, or stakes did you assume the listener shared that they probably didn’t?
  5. Where might you be over-communicating the wrong things — flooding people with noise that drowns out the few messages that actually matter?
Show reflections
  1. Most people are surprised by how few times they’ve genuinely stated their top message — often once or twice, long ago. If the number feels low, that’s your answer: it hasn’t been over-communicated, it’s barely been communicated.
  2. The reluctance almost always comes from your seat, where you’ve encountered the message many times. Reframing it from the listener’s seat — where it’s rare and easily missed — is what gives you permission to repeat it without feeling condescending.
  3. Naming the failure mode (missed / forgotten / misinterpreted) points to the fix: missed needs another channel, forgotten needs repetition over time, misinterpreted needs clearer framing and explicit context.
  4. This is the curse of knowledge in action. The useful move is to name the specific thing you skipped — a term, a piece of background, why it matters — and see it as invisible to them unless made explicit.
  5. Good answers catch the tension: over-communication only works if it’s rationed to what matters. If everything is repeated loudly, look for the low-value messages you could send once, or not at all, to make room for the important ones.