Communication as a Strategic Skill: Why Your Messages Aren’t Landing
Communication is too often treated as a support activity, something that sits alongside delivery, transformation and change management. It isn’t. It’s a strategic capability that determines whether organisational change succeeds or quietly stalls.
Communication rarely fails because people aren’t listening. It fails because organisations are poor at moving meaning, not just moving messages.
Most organisations are very good at sending messages. Far fewer are good at making sure those messages are understood, interpreted consistently, and translated into different behaviour.
This article builds on a Wellingtone Community webinar, Communication as a Strategic Skill: How to Make Messages Land where we were joined by Viktor Didenchuk from JPMorganChase. He explored why so much communication activity produces so little behaviour change, and what PMOs, change teams and leaders can do about it.
Why Does Communication Fail Even When Everyone Receives the Message?
Many leaders can point to a long list of communication activity: executive announcements, town halls, Teams or Slack messages, email campaigns, SharePoint or Confluence updates, project newsletters and governance forums. On paper, this looks like a mature communication system, because there are multiple channels, regular updates and visible evidence that information is being shared.
Yet despite all this activity, teams frequently carry on operating exactly as they did before.
The pattern is familiar: an announcement goes out, the same message is repeated through several channels, and leaders assume it has landed because people have technically received it. Weeks later, behaviour hasn’t changed, and the organisation is left wondering why the communication didn’t translate into action.
The issue isn’t a lack of communication. It’s confusing notification with understanding.
What’s the Difference Between Notification and Understanding?
One of the most useful ideas from the webinar was the distinction between being notified and genuinely understanding. The session drew on 35 in-depth research interviews with senior leaders in large organisations, which surfaced a consistent pattern: organisations are far better at proving a message was sent than at testing whether it was understood.
| Notification | Understanding | |
|---|---|---|
| What it proves | The message was sent and received; an audit trail exists. | People can explain what the message means for them. |
| What it looks like | Open rates, attendance, acknowledgement, sign-off. | Different decisions, priorities and behaviours. |
| What it satisfies | Compliance and governance requirements. | Actual operational change. |
| The risk | Mistaking transmission for impact. | Requires deliberate testing; it doesn’t happen by default. |
Most internal communication systems are optimised to prove a message was sent. Very few are designed to test whether it was understood, and that distinction matters, because organisations routinely mistake transmission for impact.
Why Does Communication Get Harder as Organisations Grow?
In smaller organisations, communication happens naturally. People speak directly to one another, context is shared, and clarification happens in real time.
As organisations grow, communication becomes layered. Messages move from the board to executive leadership, then through senior management, middle management and finally into teams. Each handover creates the potential for nuance to be lost, assumptions to creep in, or the original intent to be simplified into something less useful. With every layer, context is diluted.
Viktor demonstrating how a board decision travels down through layers of the organisation, losing context at each handover.
Most internal communication systems are optimised to prove a message was sent. Very few are designed to test whether it was understood, and that distinction matters, because organisations routinely mistake transmission for impact.
Why Does Communication Get Harder as Organisations Grow?
In smaller organisations, communication happens naturally. People speak directly to one another, context is shared, and clarification happens in real time.
As organisations grow, communication becomes layered. Messages move from the board to executive leadership, then through senior management, middle management and finally into teams. Each handover creates the potential for nuance to be lost, assumptions to creep in, or the original intent to be simplified into something less useful. With every layer, context is diluted.
| Organisation size | What typically happens |
|---|---|
| Small teams (water-cooler stage) | Communication happens naturally through direct conversation; little formal structure is needed. |
| Roughly 100–300+ employees | The “water cooler” no longer reaches everyone; formal channels, governance structures and reporting mechanisms start to appear. |
| Several thousand employees | Information overload becomes the norm, with messages competing with email, chat, meetings, dashboards and knowledge bases. |
The volume of information increases dramatically, while understanding often decreases.
Why Are Line Managers the Missing Link in Organisational Communication?
One of the strongest themes from both the presentation and the community discussion was the role of line managers.
Too often, managers act as forwarders: they pass on the deck, share the email or repeat the announcement without adding the local context their teams need. This keeps information moving, but it doesn’t necessarily help people understand how the message applies to their day-to-day work.
Effective managers do something more valuable: they translate. They help people understand what the message means for their team: what changes next week, what should stop, what should start, and where individuals need to make different choices. This translation role turns organisational messaging into practical meaning.
The community strongly agreed that line managers are often overlooked in change and communication planning, despite being closest to the people affected by change. Without supporting managers in this translation role, organisations create a gap between executive intent and operational reality.
Viktor illustrating how messages without context fail to create understanding, no matter how many times they are sent.
What Four Questions Should Every Communication Answer Before It’s Sent?
Before releasing a significant message, leaders can run it through a simple framework:
| Question | Why it matters |
|---|---|
| Who must do something differently? | Identifies the audience whose behaviour actually needs to change. |
| Who will translate the message? | Identifies the managers or leaders responsible for making it meaningful locally. |
| Where will people ask questions? | Communication without dialogue is rarely understanding. |
| How will we know it was understood? | Moves measurement beyond open rates and attendance to behavioural evidence. |
These four questions shift communication design from broadcasting information to enabling action.
What Can PMOs, Change Teams and Leaders Do to Improve Communication?
| Practical Tip | What it means in practice |
|---|---|
| Reduce communication debt | Just as organisations accumulate technical debt, they accumulate communication debt: duplicate channels, redundant messages, outdated sources and “temporary” mechanisms that quietly became permanent. Left unmanaged, this destroys any sense of a single source of truth.  |
| Design for translation | Give managers the tools to translate messages well: team discussion guides, talking points, FAQs and short “what this means for your team” summaries. Don’t just hand over the executive deck and expect understanding to follow. |
| Create dialogue, not just documents | Written communication is necessary but not sufficient, because people make sense of change through conversation. Use team briefings, ask-me-anything sessions, Q&A forums and manager-led discussions to let people test their understanding. |
| Simplify language | Project management loves acronyms and jargon. Technical language and unnecessary complexity quietly exclude the people who most need to act on the message. Communicate in plain English and optimise for understanding, not sophistication. |
What Did the Wellingtone Community Say About Communication Challenges?
| Theme | What attendees said |
|---|---|
| Communication overload | Many recognised the problem of receiving the same message through multiple channels while still not knowing what action was required. |
| Too much project language | Project management, PMO, change, governance and technology functions often develop their own language, which excludes broader audiences. |
| The critical role of managers | Participants strongly agreed that managers need better support and tools to explain change, rather than simply relay announcements. |
| The challenge of AI-generated communication | Many noted that AI often makes communication longer and more complex rather than clearer. The consensus: AI should simplify communication, not make it sound more intellectual. |
How Do You Know If Communication Has Actually Worked?
This is the question most organisations struggle to answer honestly. Open rates, attendance figures and acknowledgement clicks all measure transmission, not understanding. They tell you the message was sent, not whether it changed anything.
Three more meaningful indicators are worth building into your communication planning from the start:
- Behaviour change: Can teams demonstrate different actions following a communication? If people are still doing things the same way they were before, the message hasn’t landed.
- Quality of local explanation: Can managers clearly explain the change in their own words, without reaching for the original slides or email? If they can’t, the translation hasn’t happened.
- Decision alignment: Are decisions, priorities and planning activities reflecting the intended message across the organisation? Misaligned decisions are a reliable sign that understanding didn’t follow the announcement.
If nothing changes operationally, understanding has probably not occurred. The goal is to design communication so that these indicators can be observed, not just hope they emerge.
How Can PMOs and Leaders Build Communication Into the Way Work Gets Done?
Two areas consistently came up in the webinar as places where organisations can make practical progress without a full structural overhaul: how they support managers, and how PMOs treat communication within governance.
Supporting managers as translators
The first 90 days of any change initiative are critical. Managers who receive a briefing pack rather than just the executive deck are significantly better placed to have confident conversations with their teams. A good briefing pack explains what has changed, why it matters, the questions teams are likely to ask, and what actions are expected. Supporting activities include translation workshops, structured team discussion templates and peer learning sessions where managers share what is and isn’t working.
The objective is confidence in interpretation, not just distribution. A manager who can answer “What does this mean for our team?” without looking at a slide deck is a manager who has genuinely translated the message.
Embedding communication in PMO governance
For significant initiatives, this means more than a communication plan column in a project tracker. It means including communication impact assessments, identifying translator roles explicitly, defining behavioural outcomes, tracking understanding indicators, and reviewing communication effectiveness at stage gates alongside cost, schedule and risk.
Communication that only gets reviewed when something goes wrong is not being treated as a delivery capability. It is being treated as a cleanup activity, and the results tend to reflect that.
What Role Should AI Play in Organisational Communication?
AI came up repeatedly during the webinar, and the community’s view was nuanced. There is genuine potential, but also real risk if it is used without care.
The optimistic case is that AI copilots could become valuable translation partners: generating team-specific explainers, audience-appropriate FAQs, simplified executive summaries and change discussion guides at a scale that would otherwise be impossible. Used well, this could reduce the burden on managers and improve the consistency of local communication.
The cautionary case is that AI tends to produce more content, not better content. Longer messages, more complex language and increased volume can make the information overload problem significantly worse. The community noted that AI-generated communication often sounds more intellectual rather than clearer, which is precisely the wrong direction.
The risks of AI-amplified miscommunication are real: scaling poor messages faster, creating false confidence that something has been communicated well, and stripping out the local context that makes messages meaningful. Organisations that rely on AI to generate communication without human review and contextualisation are likely to discover this the hard way.
The principle the webinar landed on was straightforward: use AI as a sense-making tool, not a content-generation machine. Focus it on clarification and simplification, not expansion. And keep humans in the editor role, responsible for the quality and accuracy of whatever goes out.
