Your Team Heard the Same Message. They Didn't Hear the Same Thing

Giving everyone the same information doesn’t create shared understanding.

People interpret information through different roles, experiences, expectations, incentives, concerns, and levels of access to the bigger picture.

Telling your team that the company’s focus next quarter is accelerating pipeline velocity doesn’t guarantee they understand what that means in the same way you do, or even in the same way as one another.

If leaders want to create and maintain alignment, they can’t just communicate the message. They need to make the relevant organizational context visible, and then check what people actually understood.

Everyone attended the same meeting

Let’s take a hypothetical announcement made during a typical company meeting.

The CEO announces that the company is shifting focus toward larger enterprise customers. He sees a path toward more sustainable revenue.

But Sales hears larger contracts, longer deal cycles, potential missed quotas, and fewer commission checks.

Marketing wonders whether the existing pipeline and messaging still matter and whether current campaigns need to be paused.

Customer Success anticipates more complicated implementations and additional support needs across multiple stakeholders.

Product worries that several roadmap commitments may no longer be relevant.

Engineering worries that large clients will come with large, ad hoc requests that require patchy code to be delivered quickly.

And an employee who survived the last restructuring wonders whether “strategic shift” means another round of layoffs.

Everyone heard the same announcement. But it didn’t mean the same thing to each of them.

It reminds me of the time my uncle told someone, “I can’t hear your English.” He could hear every word, he just wasn’t picking up what they were putting down. The language was shared. The meaning wasn’t.

The message is only one part of the communication

The announcement itself is the information, or the content, entering the conversation. Ok, so “we’re shifting our focus toward enterprise customers.” But there’s a bunch of organizational context surrounding that statement that hasn’t been communicated yet, like:

• What prompted the change

• What outcome leadership expects it to produce

• What evidence supports it

• What needs to change now

• What isn’t changing

• How current priorities will be affected

• How different folks will be affected

• What different teams will be responsible for

• What resources or support will be available

• What remains unknown

• What people should do differently as a result

When leaders communicate the information without enough of this context, people fill in the missing pieces themselves. Not because they’re being difficult or negative. Because that’s what human beings do.

We make sense of new information using the context we already carry

That’s the second kind of context operating here - personal context.

Each person receives the announcement through their own role, history, experiences, incentives, expectations, fears, and access to information. So they start asking questions and reaching conclusions like:

• Are our quotas going to change?

• Will our current campaigns be measured against the same targets? D

• oes the existing product roadmap still matter?

• Are we expected to support enterprise clients without more people or resources?

• Will the work we’ve already completed be abandoned?

• Is another restructuring coming?

• Does leadership actually know what it’s doing?

• This sucks, another change in only three months

• What a toxic workplace that doesn’t support its people’s well-being

• I probably have to work weekends just to keep up

None of those questions or conclusions were included in the announcement. People created them by combining information they received with the context they already carried.

So there are two kinds of context operating at the same time: the organizational context leaders need to make visible and the personal context people use to understand what they’ve been told.

You need to account for both.

Leaders can’t control every interpretation

A leader’s job isn’t to force everyone to interpret an announcement or new information identically. It’s to do your best to ensure shared understanding.

And shared understanding doesn’t mean everyone reaches the same conclusion or has the same reaction. It means people understand the decision, the intended outcome, what is known and unknown, and what it requires of them - even if they feel different about it.

The goal is to make enough of the organizational context visible so that people can form informed interpretations, ask useful questions, and coordinate their actions.

So if you’re the CEO announcing a shift toward enterprise customers, you first need to determine what your leadership team needs to understand. Make sure you also communicate why the change is happening, what outcome you’re trying to produce, what evidence informed the decision, and which other priorities will be affected.

You may not have all the answers yet, and that’s ok. Articulating what remains unknown is also part of providing context. The feedback loop helps uncover consequences and implications that leadership may not be able to see from the top.

Each leader then needs to figure out what the context means for their function and what their teams need to know.

But this can’t operate like a one-way game of telephone where information travels down and everyone is expected to act.

Questions, concerns, consequences, and missing information also need to travel back up. The people closest to the work may see risks and implications the leadership team never considered. I’ve witnessed this to be true many times throughout my career.

Shared understanding requires a feedback loop.

Don’t ask, “Does that make sense?”

After communicating something new and its surrounding context, please don’t end with, “Does that make sense?” or “Everyone good?” or “Does everyone understand?”

Aside from a few rolled eyes and annoyed sighs, those questions usually produce silence or nodding.

If you want to genuinely find out what people actually understood, ask clarifying questions like:

• What are your thoughts or main takeaways?

• What do you need to know to do your work?

• What questions or concerns does this raise?

• What needs to change or stay the same as a result?

• What information do you still need before you take action?

Of course, asking better questions doesn’t guarantee honest or immediate answers. People may not feel comfortable disagreeing publicly, especially when the person making the announcement has more power. They may also need time to process what they’ve heard before they even know what they think. You may need to create opportunities for questions and concerns to surface through smaller meetings, one-on-ones, anonymous channels, or follow-up conversations.

What people share will help you see what they heard, what they assumed, where the gaps are, and legitimate consequences you may not have considered.

This way, you can correct inaccurate assumptions, clarify what remains uncertain, find out what additional information people need, and discover if the decision itself may require more thought.

Communication isn’t complete when a leader finishes talking.

It’s complete when the people responsible for taking action understand enough to actually move forward.

Your team may have heard the same words, but don’t assume they walked away with the same message. Provide context, understand context, then clarify, reset, and communicate accordingly.