We live in an age where sending information has become almost effortless.
I can send a message to fifty people in seconds.
I can upload a document and give an entire organization access.
I can invite twenty people into a meeting without leaving my desk.
I can post an announcement into a channel and instantly see that people have read it.
Technology has made transmission extraordinarily easy.
And yet organizations still regularly experience conversations like these:
I didn’t realise that’s what you meant.
That wasn’t my understanding.
I thought the other team was doing it.
Yes, I saw the message, but I didn’t know I was supposed to act.
This creates an interesting contradiction.
We have more communication tools than perhaps any generation before us.
But more information has not automatically produced more understanding.
Why?
Because information and meaning are not the same thing.
Sending Is Only the First Step
Imagine a leader sends this message:
This is now our highest priority. We need to move quickly.
The message appears straightforward.
But what does highest priority mean?
Should people stop the work they are currently doing?
Does quickly mean today, this week, or this month?
Who owns the next decision?
What changed that made this urgent?
What trade-offs have already been accepted?
The person sending the message may know all of this.
The people receiving it may know none of it.
That’s the difference between information and context.
The sender possesses both.
The receiver often receives only one.
The Same Message Can Produce Different Meaning
Put ten people in a room and give them the same sentence.
They won’t necessarily hear the same thing.
They interpret it through what they already know.
Their role.
Their history.
Their assumptions.
Their relationship with the sender.
Their understanding of the problem.
Their previous experiences.
This is particularly important in distributed organizations.
When we share a physical environment, a surprising amount of context travels informally.
You overhear conversations.
You see what people are working on.
You notice urgency in someone’s behaviour.
You ask a five-second follow-up question.
You encounter somebody in the corridor who adds one missing piece of information.
Distributed teams lose much of that ambient context.
Which means the signal often needs to carry more of its own meaning.
The Information Journey
I’ve found it useful to think about important organizational communication as a journey:
Information -> Context -> Understanding -> Decision -> Action -> Result
Each stage matters.
And each transition is a potential failure point.
Information
Something enters the system.
A customer problem.
A strategic priority.
A technical risk.
A decision.
A change in direction.
A production incident.
This is the raw signal.
But the signal alone isn’t enough.
Context
Why does this matter?
What happened before?
What constraints exist?
What has already been considered?
What changed?
Who is affected?
Context gives the information meaning.
Without it, people fill the gaps themselves.
And human beings are extremely good at filling gaps.
Unfortunately, we don’t always fill them with the same assumptions.
Understanding
Now the receiver needs to form a sufficiently accurate interpretation.
Notice that I said sufficiently accurate.
Perfectly identical understanding across humans is unrealistic.
But people need enough shared understanding to coordinate.
This is where leaders sometimes make a mistake.
We assume clarity is a property of the message.
It isn’t.
Clarity exists at the receiver.
A message can seem perfectly clear to the person who wrote it and remain completely ambiguous to everybody else.
Decision
Understanding should eventually enable choice.
What are we doing?
What aren’t we doing?
Who owns it?
What trade-off are we accepting?
When does this take effect?
Without a decision, communication can generate enormous amounts of discussion without creating movement.
Action
Then someone needs to do something.
This is where vague organizational language becomes expensive.
We should…
The team needs to…
Someone should look into…
Those statements sound active while leaving ownership unresolved.
Good communication makes the next action discoverable.
Result
Finally:
What changed?
Did the action work?
Did the customer problem disappear?
Did the risk reduce?
Did we learn something?
Results feed new information back into the system.
Communication becomes a loop.
The Meeting Trap
This also explains why meetings can create an illusion of alignment.
Everyone attended.
Everyone nodded.
Nobody objected.
The meeting finished on time.
Success?
Maybe.
But ask everyone separately:
What did we decide?
Why?
What happens next?
Who owns it?
If the answers differ significantly, the meeting transmitted information without creating shared meaning.
Another meeting may eventually be needed to repair the first one.
That is communication debt.
Don’t Measure Communication by Volume
Organizations often respond to communication problems by increasing communication.
More meetings.
More updates.
More channels.
More documentation.
More notifications.
But volume isn’t the same thing as quality.
If context is missing, sending the message five times doesn’t necessarily improve it.
If ownership is unclear, another meeting doesn’t automatically create ownership.
If a decision disappears after the meeting, more conversation doesn’t create persistence.
The better question is:
Where is meaning being lost?
That question changes the conversation.
Design for the Receiver
One practical change leaders can make is to stop designing important communication around what the sender wants to say.
Design it around what the receiver needs to do.
Before sending something important, ask:
- What context will they need?
- What could reasonably be misunderstood?
- What decision does this enable?
- Is ownership clear?
- Can they act without needing to find me?
- Where will this information live afterwards?
That doesn’t mean every message becomes an essay.
Sometimes a sentence is enough.
The objective is not more information.
It is sufficient meaning.
“Did We Communicate It?” Is the Wrong Finish Line
I have heard this sentence many times:
But we communicated that.
And sometimes that’s true.
The email exists.
The presentation happened.
The announcement was posted.
But organizational communication shouldn’t be measured solely by whether something left the sender.
The better test is what happened at the other end.
Did people understand?
Could they decide?
Could they act?
Did the expected result follow?
Because ultimately, communication is not a broadcasting activity.
It is part of the system through which organizations turn information into coordinated action.
So the next time something important needs to travel through your organization, don’t stop at:
Did we communicate it?
Ask the harder question:
Can the people receiving it understand it well enough to act?
That is where communication begins turning into performance.
Don’t just communicate. Design how meaning travels.