A practical guide to diagnosing shallow change communications strategy — and rebuilding it with clarity.
Most organizations don’t fail because their teams lack skill. They fail because their teams lack sense-making.
Work slows down, decisions bottleneck, and change efforts stall — not because people aren’t capable, but because what’s being called “strategy” is really just a list of tasks wearing a strategy costume.
The uncomfortable truth: if your team can’t explain why they’re doing the work, you don’t have a strategy. You have instructions.
This article walks through the five most common signs that a change communications strategy isn’t actually a strategy — and how to rebuild each one with clarity, defensibility, and real portability.
Sign 1 — Your strategy fails the “explain the why” test
A real strategy passes one simple test: if you left the room, could your team explain why the work matters?
Not the deliverables. Not the timeline. Not the talking points. The why.
If the answer sounds like “let me check” or “we were told to focus on this,” the strategy isn’t clear — it’s fragile. And fragile strategies produce fragile execution: teams that can deliver the plan when you’re in the room and lose direction the moment you’re not.
This is the most common failure mode in change communications strategy. The plan exists. The rationale doesn’t — at least not in a form that anyone besides the person who built it can articulate. The strategy is locked inside one person’s head and only accessible through proximity to that person.
The test is simple: ask your team to articulate the strategy in one sentence. If it takes a paragraph, a slide, or a reference to the deck, it’s not strategy yet. Strategy that requires narration to make sense is dependency, not direction. And dependency doesn’t scale.
The fix: Write the why explicitly — not as a background section in a strategy document, but as the first sentence of the strategy itself. Before any deliverable, any channel, any timeline: here is the problem this communication strategy is solving, and here is why solving it matters now. If you can’t write that sentence, the strategy isn’t ready to be executed.
Sign 2 — Your plan is full of directives, not strategy
Here’s how to spot the difference. Someone asks: “Why are we focusing on manager cascades instead of sending an all-staff email?”
And the answer is:
“Because that’s how we’ve always done it.” “Leadership prefers this approach.” “That’s the direction we were given.”
None of these are strategic reasons. They’re preferences dressed in authority. And when preferences masquerade as strategy, two things happen. First, the plan can’t survive scrutiny — because it has no logic to defend, only authority to invoke. Second, the team can’t make good decisions in the gaps, because they have no rationale to work from, only instructions to follow.
A real strategy is rooted in logic that travels through the organization, holds up under questioning, and survives without the original author narrating it. It sounds like: “We’re prioritizing manager cascades because employees trust information from their direct supervisor significantly more than messages from corporate channels — so if we want behavior change, we need to activate the voices people actually listen to.” That’s defensible. That’s strategic. That’s something a team member can repeat to a skeptical stakeholder without having to call you first.
The fix: For every major strategic choice in your plan, write the “because” explicitly. Channel selection, audience sequencing, message cadence, measurement approach — each one should have a documented rationale that any team member can articulate without checking with you. If the rationale doesn’t exist or doesn’t hold up, the choice isn’t strategic yet.
Sign 3 — Your strategy can’t travel without you
This is the real test of strategic integrity: if your strategy falls apart once it leaves your mouth, you don’t have a strategy.
A strong communications strategy is clear enough to explain, compelling enough to defend, and consistent enough to travel without the person who built it. When it requires its author to personally walk stakeholders through it, two things are true simultaneously: the strategy isn’t clear, and the organization is now dependent on one person for something that should be systemically understood.
This is what I think of as the portability problem. A strategy that requires your presence isn’t scalable — because your presence is finite and the organization’s communication needs are not. Every leader who can’t explain the strategy in their own words becomes a gap in the cascade. Every manager who needs to call you for clarification before communicating to their team is a sign that the strategy hasn’t actually been distributed — it’s been hoarded. (For how narrative drift develops from this portability failure, read From Noise to Narrative.)
The fix: Test portability deliberately. Share the strategy with someone who wasn’t involved in building it and ask them to explain it back. Ask them to explain the most important strategic choice it makes and why. If they can do that accurately without prompting, the strategy is portable. If they can’t, it needs to be simplified until they can.
Sign 4 — You can’t defend it with evidence
A defensible communications strategy sounds like this: “We’re focusing on manager cascades because employees trust information from their direct supervisor significantly more than messages from corporate channels. Research consistently supports this. If we want behavioral change, we need to activate the voices people actually listen to — not add more volume to the channels they’ve already learned to tune out.”
That is data-backed, purpose-driven, outcome-aligned, and defensible. It will survive a challenge from a senior leader who prefers a different approach. It will survive a budget conversation. It will survive a skeptical project sponsor who thinks email is sufficient.
If your justification doesn’t hold up under that kind of scrutiny — if it relies on preference, precedent, or authority rather than evidence and logic — you’re not defending a strategy. You’re defending a habit. And habits don’t earn trust from the leaders who need to believe in your communication plan to resource it properly.
This connects directly to the clarity gap. Leaders who can’t articulate the strategic logic behind their communication choices are almost certainly operating inside an underdeveloped strategy — one where decisions were made but the reasoning was never captured in a form that could be tested or challenged. (For more on the clarity gap, read The Clarity Gap.)
The fix: For every major strategic choice, find the evidence. Not necessarily academic research — sometimes the evidence is organizational data, past program results, or direct employee feedback. The evidence doesn’t have to be perfect. It has to be better than “this is what leadership wants.” Write it down. Make it part of the strategy document itself, not a separate justification you produce when challenged.
Sign 5 — Your team isn’t showing autonomy
When a communications strategy is genuinely clear, something specific happens: the team stops escalating and starts deciding.
They make better decisions in real time because they understand the direction, not just the deliverables. They defend the work to stakeholders because they can articulate the logic without calling you first. They show alignment rather than compliance — and the difference is visible. Compliance is doing the thing because you were told to. Alignment is doing the thing because you understand why it matters and have internalized the direction well enough to adapt it to new situations.
Clarity makes teams autonomous. Ambiguity makes them dependent. When a team needs its leader in every significant meeting to translate the strategy, that’s not a team working from a strategy — it’s a team working from a person. The strategy hasn’t been distributed. It’s been hoarded.
This is one of the most reliable diagnostic signals available: watch what the team does when you’re not in the room. Do they make decisions that are consistent with the strategic logic? Do they explain the work in ways that sound like the strategy — or in ways that sound like their own interpretation of it? Consistency without your presence is the clearest indicator that the strategy has actually landed. (For how to build communication that produces this kind of autonomous alignment, read How to Create Communication That Actually Changes Behavior.)
The fix: Test autonomy directly. Before a significant communication goes out that you didn’t personally draft, ask the team member who drafted it to explain the strategic logic behind the choices they made — channel, timing, tone, structure. Their explanation tells you whether the strategy is in their head or just in the document. If it’s only in the document, the strategy needs to be taught, not just shared.
How to rebuild a strategy that actually holds
Diagnosing that your strategy is hollow is the beginning, not the end. Here is how to rebuild it with the clarity, defensibility, and portability that genuine strategy requires.
Document the why before the what. Start every strategy document with the problem being solved, the logic behind the approach, and the definition of success — before any deliverable, channel, or timeline appears. People can align to logic. They cannot align to mystery.
Cascade context, not slides. Most strategy cascades fail because leaders share artifacts rather than understanding. Your job when cascading a communications strategy is to explain how you think, why decisions were made, and what logic holds the plan together. The slides are a reference. The reasoning is the strategy. (For the structural approach, read The Clarity Framework™.)
Repeat until you’re tired of hearing yourself. People don’t hear strategy the first time. Or the second. Or the third. Communication doesn’t land when you say it — it lands when they start saying it. Repetition isn’t redundancy. It’s the mechanism by which strategy becomes shared understanding rather than documented intent.
Ask for the echo, not the nod. Nodding means they received it. Echoing means they understood it. Ask: “Can you explain this back to me in your own words?” If they can’t — if they reach for the document rather than their own language — the strategy isn’t clear yet. Simplify and repeat until the echo is consistent and fluent.
Make it portable before you cascade it. Test the strategy on someone outside the team before it goes out. If they can explain the strategic logic without prompting, it’s ready. If they can’t, it needs work. A strategy that requires your presence isn’t a strategy — it’s a briefing. And briefings don’t scale.
What this looks like in practice
I worked with a communications team who believed they had a solid change communications strategy for a major ERP implementation. They had a detailed plan — channel matrix, message calendar, leader cascade schedule, FAQ document.
When I asked the team to explain why they had chosen the manager cascade approach over direct all-staff communication, three people gave three different answers. None of them referenced the same logic. One said it was what leadership requested. One said it was how they’d always approached rollouts. One gave a genuine strategic rationale about manager trust levels — but wasn’t sure if that was the actual reason or just her own interpretation.
The plan was detailed. The strategy wasn’t there.
We spent two hours rebuilding the rationale — not the plan itself, which was largely sound, but the documented logic behind every major choice. We wrote the why for each decision. We tested it with two people outside the team. Within a week, every team member could articulate the strategy in their own words and defend the key choices under questioning.
The plan hadn’t changed. The strategy finally existed.
Final thought
The question that changes everything is simple:
Could your team explain the why — without you in the room?
If not, you don’t have a strategy. You have instructions. And instructions stop working the moment the person who gave them isn’t available to repeat them.
Strategy that travels. Strategy that survives scrutiny. Strategy that produces autonomous, aligned teams who can make good decisions in the gaps.
That’s the difference between a task list with a strategy label and something that actually holds.
FAQs: Change communications strategy
If it’s organized around deliverables rather than direction — emails to send, sessions to hold, decks to produce — it’s a task list. A real strategy is organized around the logic of why those deliverables were chosen: what problem each one solves, what audience it serves, and what behavioral or understanding outcome it’s designed to produce. The test: if the deliverables stayed the same but the rationale disappeared, would the team know what decisions to make in the gaps? If not, there’s no strategy.
The team can’t explain the why without consulting a document or the person who built the plan. Strategic choices are justified by preference or precedent rather than evidence and logic. The strategy requires the author to personally cascade it because it doesn’t travel independently. The plan can’t be defended under scrutiny from a skeptical stakeholder. And the team isn’t making autonomous decisions — they escalate everything because they’re working from instructions, not direction.
Because organizations mistake planning for strategy. A detailed communication plan — channels, timelines, message calendars — is not the same as a communications strategy. Strategy is the documented logic that explains why those channels, that timing, and those messages were chosen. Without the logic, the plan produces compliance rather than alignment — and compliance stops working the moment execution hits a situation the plan didn’t anticipate.
Alignment means people nodded — they received the strategy and agreed not to contradict it. Echo means they understood it — they can explain it in their own words, defend the key choices, and apply the logic to new situations without asking for guidance. Alignment can be performed. Echo can’t. Testing for echo rather than alignment is the most reliable way to know whether a strategy has actually landed.
When leaders can’t articulate the strategic logic behind their communication choices, the team operates inside the clarity gap — the distance between what the strategy intends and what the team understands. Decisions get made from habit or preference rather than logic. The strategy fragments as it cascades. And the communications function loses credibility with senior stakeholders who can’t see the strategic thinking behind the work.
The Clarity Framework provides the structural backbone that turns a communication plan into a genuine strategy. The diagnose principle identifies where the strategic logic is missing. The define principle builds the core narrative that every strategic choice should serve. The design principle creates the rhythm and structure that makes strategy portable. The deliver principle ensures the strategy is communicated in a way that produces echo rather than just alignment. And the measure principle tests whether the strategy is actually working — not by counting outputs but by assessing whether understanding and autonomous action are increasing.
If your organization is navigating change and you’re not sure why communication isn’t landing, that’s often where the work begins.
I’m Ana Magana, a change communications and change management consultant based in Calgary, Alberta. I help organizations build communication strategies that actually hold.
Work with me →
Read: How to Build a Change Communications Strategy That Actually Works | The Clarity Gap: Why Leaders Think They’re Being Clear | The 7 Change Management Mistakes That Derail Initiatives