If you haven’t said it clearly, it hasn’t been heard

You don’t lose alignment in projects because people don’t care.
You lose it because people are left to interpret. 

It’s one of the most common patterns I see when stepping into projects that feel “off track,” even when everything appears to be moving. 

The plans exist.
The meetings are happening.
The team is working hard. 

But when you pause and ask a simple question “What are our top priorities right now?” – you don’t get one answer, you get many. 

That’s the moment you realise this is not a delivery issue; it’s a communication gap. 

The illusion of communication

There’s a well-known quote from George Bernard Shaw:
“The single biggest problem in communication is the illusion that it has taken place.” 

In project environments, that illusion shows up everywhere. 

Leaders think they’ve been clear because they’ve said something once.
Teams think they understand because they’ve heard something familiar. 

But in between those two moments sits interpretation and interpretation is shaped by: 

• Past experience  
• Individual priorities  
• Role-based perspectives  
• Assumptions about what matters most  

So while the leader is operating from intent, the team is operating from interpretation. 

That gap is where misalignment begins. 

When silence becomes risk

What you don’t say matters just as much as what you do. 

Unspoken expectations create invisible pressure points in a project: 

• What is the real priority – speed, quality, or stakeholder satisfaction?  
• How should trade-offs be made when things get tight?  
• What does “good” look like in this context?  

If those things are not clearly communicated, the team doesn’t stop. 

They decide. Individually and often, differently. 

This is where good people, doing good work, unintentionally start pulling in different directions. 

Not because they weren’t told anything but because they weren’t told clearly enough, consistently enough, or in a way that connected the dots. 

The communication gap model 

One of the simplest ways to understand this is to break communication into four layers: 

• Intent – what I’m thinking  
• Expression – what I say  
• Interpretation – what they hear  
• Action – what they do  

Most leaders spend their time in intent, and most teams operate in action. 

But delivery is shaped by everything in between. 

Every gap between these layers introduces the potential for drift: 

• Something important isn’t said  
• Something is said but not fully understood  
• Something is understood differently by different people  
• Something is acted on in ways that don’t align  

Over time, those small gaps compound into bigger issues. 

Why this matters under pressure

This becomes even more critical when projects are under pressure. 

When time is tight, people default to what they know.
When priorities compete, people make judgement calls.
When uncertainty increases, people rely on their own interpretation. 

Without clear communication, pressure doesn’t create alignment, it exposes the lack of it. 

This is why communication is a core delivery capability. 

Communication is making thinking visible

One of the shifts I often work through with project leaders is this: communication is more than sharing updates, it is making your thinking visible. 

That means: 

• Explaining not just what the decision is, but why it matters  
• Clarifying how priorities should be balanced when trade-offs arise  
• Providing context so the team can make aligned decisions without constant escalation  

Because the reality is, you won’t be in every conversation, but your thinking can be – that is if you’ve communicated it clearly enough. 

What this looks like in practice

If this is resonating, here are five practical ways to close the communication gap: 

1. Say it clearly,don’timply it 

If something matters, say it directly.
Clarity removes guesswork. 

2. Repeat and reinforce

One conversation is not communication.
Consistency builds shared understanding. 

3. Check for understanding,not just agreement

Instead of asking, “Does that make sense?”
Ask, “What does this mean for your work?” 

4. Share your thinking, not just your decisions

Context helps people make better decisions when you’re not there. 

5. Close the loop

Ensure what was said → understood → applied.
That’s where communication becomes leadership. 

Your team is not failing you. 

They are responding to what they understand and if what they understand is different to what you intended, that is a communication opportunity. 

What have you assumed your team “just knows” …that you haven’t said?