How alignment isn’t created in isolation. It’s built through communication and coordinated clarity.
Two team leads sat in the same thirty-minute call, listening to the same decision get made. A week later, one had told their partner the rollout was delayed a month. The other had told theirs it was delayed two weeks, contingent on a fix that was already in progress. Nobody had lied. Nobody had missed the call. They had simply heard the same sentence and built two different pictures of what it meant, and neither picture got corrected until a partner asked why the two teams were telling a different story.
I have been chewing on something all week. We talk a lot. We meet, we send updates, we document decisions, we write plans. By any honest measure we communicate constantly. And yet I keep running into moments like that one, where two people walk out of the same conversation carrying two different versions of what was decided. That should bother us. It bothers me.
Communication is not the same as understanding
Here is where I landed. We have been treating communication as the goal when it is really just the tool. The goal is shared understanding, and those two things are not the same. I can send a perfectly clear message and still not reach you. You can nod in a meeting and still leave unsure. Information moving from one person to another is not the same as two people actually seeing the work the same way.
That gap matters more on programs like this than almost anywhere else. When you are replacing many interconnected systems at once, coordinating across partners who have run their own operations for years, you are asking a lot of people to trust a picture of the future they cannot fully see yet. Alignment on work like this does not happen because someone held a meeting or published a document. It happens when people across every team and every partner genuinely understand what is being built, why it matters, and what their part in it is. It is the same understanding gap that makes the story behind a decision matter as much as the decision itself.
Three habits that close the gap
So what actually needs to change. A few things worth getting more deliberate about:
- Seek understanding before giving direction. Before handing someone a direction, you owe them the work of understanding where they are starting from. This is especially true with partners. They are not resisting for the fun of it, they are protecting something that has worked for them, and if you do not understand what that is, your direction lands as a demand instead of a shared plan. It is the same instinct behind starting from a partner’s picture of success instead of a finished plan.
- Communicate proactively instead of reactively. Most of the hardest conversations happen after something has already gone sideways. In practice this means a standing rule, not a good intention: if something changes that affects another team or partner, they hear it the same day, from you, before they have a reason to ask.
- Confirm understanding, do not just deliver a message. Ask people to say back what they heard, in their own words, before assuming a room left aligned. Call it the read-back: one sentence, in the other person’s own words, on what they think just got decided and what it means for their part of the work.
As a director, the temptation is to measure success by how much you have communicated: how many updates went out, how many meetings were held, how thorough the documentation is. None of that is the actual goal. The actual goal is whether the people doing the work and the people depending on it are seeing the same picture.
Communication is what you send. Shared understanding is what actually arrives.
The quiet warning sign
There is a tell for when the gap is opening up, and it is quieter than most people expect. It is not conflict. It is two people giving you the same answer with different confidence, or in slightly different words, when you ask them separately what happens next. Confident disagreement is easy to catch. Two calm, cooperative people who are each certain of a different thing is the actual warning sign, and it almost never shows up in the meeting itself. It shows up a few days later, in a hallway conversation or a partner’s confused email, once the gap has already turned into a real problem, often for the same quiet reasons a process gap goes unreported, or a transformation quietly stalls without anyone naming it.
Closing that gap is slow, unglamorous work. It means asking more questions than feels efficient, checking for understanding when it would be faster to assume it, and treating a moment of confusion as information instead of an inconvenience. But it is the difference between a team that is technically informed and a team that is actually aligned, and only one of those gets the work done.
More essays like this one live on the Between Mondays articles page.
Further reading: Gallup Workplace and MIT Sloan Management Review both publish extensively on team alignment and organizational communication.
Frequently asked questions
What is the difference between communication and shared understanding?
Communication is the message you send: the email, the meeting, the status update. Shared understanding is whether the people who received it actually built the same picture of what was decided. You can communicate constantly and still have a large, invisible gap between the two.
Why does the gap between communication and understanding matter more on large programs?
Large programs ask many teams and partners to trust a picture of the future they cannot fully see yet. Alignment does not come from holding a meeting or publishing a document, it comes from people across every team genuinely understanding what is being built and what their part in it is.
What is the read-back technique?
At the end of a conversation where a decision gets made, ask the other person to say back, in their own words, what they think just got decided and what it means for their part of the work. It costs about thirty seconds and catches misunderstandings before they become expensive.
What is the earliest warning sign that a team has lost shared understanding?
It is quieter than conflict. It is two people giving you the same answer with different confidence, or in slightly different words, when you ask them separately what happens next. Confident disagreement is easy to catch; two calm people each certain of a different thing is the real warning sign.
How can a leader communicate more proactively instead of reactively?
Set a standing rule rather than relying on good intentions: if something changes that affects another team or partner, they hear it the same day, from you, before they have a reason to ask. Waiting for the next status meeting to surface bad news is waiting too long.