Stand at the front of a leadership briefing and ask the room a simple question: what happens to this strategy the moment it leaves the building? Most executive teams haven’t thought about it, because the room they’re standing in feels like the finish line. It isn’t. It’s the start of forty separate retellings, and you won’t be in any of those rooms to hear how they go. Helping managers carry the strategic narrative into that first retelling is the actual work that starts once the briefing ends.
This is the actual problem I get called in to solve, at a strategy cascade, a manager summit, a divisional town hall, or the first round of a leadership briefing: helping managers carry the strategic narrative once it’s out of your hands and into theirs. The fuller argument for why a strategy cascade is a fidelity problem, not a distribution problem sits on its own page. This piece is narrower. If you’re the CEO, the CHRO, the chief of staff or the head of internal communications standing in that room, here’s the plain version of what I want you to take away. Protect the decision. Hand every manager permission and practice to carry it their own way. Skip either one, and they will default to reading the deck, even if nobody told them to.
The Retelling You Never Get to Hear
Nobody designed for what happens after the briefing ends. You handed out a pack, and a pack is not a plan for what a manager does when a real question lands on them in their own team meeting, three weeks later, with no executive in the room to back them up. What they do in that moment is improvise, using whatever they were actually given permission to say. Most of the time, that’s nothing, so they read the slide again, more slowly.
Multiply that single meeting by every manager who was in your briefing, and you get forty separate versions of the strategy, each shaped by whatever that particular manager happened to retain, believe, and feel safe repeating. None of those versions get checked against the original. Nobody from the executive team sits in the back of a regional manager’s Tuesday morning meeting to correct the record. Whatever gets said in that room becomes the strategy, as far as that team is concerned, whether or not it matches the deck.
This is why so much energy poured into the cascade itself quietly evaporates a few weeks later. The keynote lands, the pack is polished, the Q&A goes well, and everyone in the room nods. Then the real test happens somewhere leadership will never see it, in a room leadership will never enter, and the story that survives is whatever version each manager was equipped to tell. Solving that problem, not writing a better deck, is what helping managers carry the strategic narrative actually requires.
Consistency Is Not Sameness
This is the assumption that quietly wrecks most cascades: that consistency means giving everyone the same words. Give forty managers, forty branch leads, forty team leaders the identical script and you haven’t made the message consistent. You’ve made forty people sound like they’re reading. Their teams notice in the first sentence. What they hear isn’t the strategy. What they hear is that leadership doesn’t trust this person to say it in their own words.
Picture the version most cascades produce: a manager standing at the front of her own meeting, reciting four bullet points from memory, pausing in the same places the slide deck paused, using phrases that clearly aren’t hers. Her team has sat through enough of these to recognise the cadence within a sentence. They don’t hear a leader interpreting a strategy. They hear someone reading it back to them.
Sameness protects the words. Consistency protects the decision underneath them. Confuse the two and you’ll spend your enablement budget locking down the wrong layer, the layer nobody actually needed protecting, while the layer that mattered, the trade-off, the numbers, the boundary of what’s still undecided, gets left to chance because nobody thought to write it down.
Protect the Decision, Not the Sentence
Consistency should live in the decision, not in the sentence carrying it. Three things have to hold, no matter who’s speaking or how they say it: the trade-off, meaning what the organisation has decided not to do and why; any commitment already made publicly; and any number already quoted to the board or the market. Protect those three, in writing, and everything else, the opening line, the example, the tone, the order the points come in, is safe to leave to the person standing in front of their own team. A manager who sounds like herself gets heard. A manager who sounds like a memo gets tolerated, and a team can tell the difference inside one sentence.
Skip drawing that line explicitly, and managers guess, in both directions. Some soften a trade-off that was never meant to be softened, because nobody told them it was non-negotiable. Others recite the phrasing on a point that was always meant to be theirs to interpret, because nobody told them they were allowed to say it differently. Either mistake costs you something, and both are avoidable with three sentences of clarity written down before the briefing, not improvised afterwards.
I have written separately about the structure a strategic narrative needs to survive being retold, and this piece assumes that structure already exists. The question here is what you actually hand the person retelling it.
Why Do Managers Default to the Script, Even When Nobody Told Them To?
Not laziness. Risk. If the only feedback a manager has ever received about carrying a message is stick to the deck, the rational move is to stick to it word for word and hope nobody asks a hard question. They aren’t protecting your strategy. They’re protecting themselves, and your strategy is what pays for it. Most leadership toolkits are built to stop a manager saying the wrong thing, and in doing that, they strip out the one thing that makes a message land: sounding like it came from someone who actually thought about it.
Think about the asymmetry a manager is actually weighing. Deviate from the deck and get it right, and nobody notices, because that’s simply what a good manager is supposed to do. Deviate from the deck and get it wrong, misstate a number, promise something that wasn’t approved, and it becomes a story people tell about that manager for years. Given that asymmetry, sticking to the script isn’t a failure of nerve. It’s the only rational move available to someone who has never been told the boundaries within which they’re free to move.
Most toolkits respond to this risk with more control, not less: longer FAQs, more approved phrasing, stricter guidance on what can and can’t be said. Every one of those additions makes sense in isolation, and together they make the deck longer and the manager more likely to read it verbatim, because now there’s even more to get precisely right and even less room to sound like a person who thought about it themselves. None of that is what helping managers carry the strategic narrative into a real room actually takes.
Managers Don’t Need a Better Script
Two things, and neither costs you a line item. The first is permission, written down, not implied. Explicit permission to say I don’t know yet without it reading as failure. Explicit permission to say here’s the part I’m still working out, out loud, in front of their own team. Managers don’t lack the confidence to say these things. They lack the authorisation, and confidence without authorisation looks exactly like caution, which is why it always comes out sounding like the deck.
In practice, this means putting sentences into a manager’s hands that most leadership teams would never think to write down: you are allowed to say this differently than the deck. You are allowed to tell your team what you’re still figuring out. You are allowed to answer a hard question honestly, even if the honest answer is I don’t know yet. None of these sentences cost anything to grant. Almost nobody grants them anyway, because nobody thinks to ask whether managers already believe they’re allowed.
A manager with excellent instincts and no explicit permission will still default to the script, because instinct without authorisation reads, to that manager, as risk rather than judgement. Give the same manager permission in writing, and the instinct she already had becomes something she’s allowed to use. The strategy doesn’t get better content that week. It gets a person willing to actually say it.
How Do You Rehearse the Question a Manager Is Dreading?
The second thing is rehearsal, and almost no toolkit includes it. Not a briefing where the messages get read aloud once. An actual run, in a small room, where a manager says the hardest sentence out loud, takes a real follow-up question, and gets it wrong once so they get it right on the day. That dreaded sentence is rarely about the strategy itself. It’s usually some version of does this mean my team gets smaller, and a manager who has said the honest answer out loud once, to a colleague rather than a direct report, says it steadily when it actually counts.
Run this properly and it looks unremarkable from the outside: a small group, a colleague playing the role of a sceptical direct report, and one specific hard question asked out loud, the same one that keeps that manager awake before the cascade. The manager answers it badly the first time, because everyone does the first time. Then they answer it again, and the second answer is almost always dramatically better than anything a written FAQ could have prepared them for.
What changes isn’t the content of the answer. It’s the manager’s relationship to the question. A question rehearsed once, out loud, in a low-stakes room, stops being a threat and becomes something merely difficult, which is a completely different feeling to walk into a real meeting with. This is the second half of what actually makes a strategy survivable: not just permission to say the honest thing, but practice saying it before the room that matters most is watching.
Give Every Manager One Thing They Can Change This Week
This is where I bring in The First 48 Hours, the test I use everywhere in my work: a decision is only believed once something visibly stops, starts or changes within 48 hours of it being made. Applied here, every manager should leave your cascade with one specific thing they’re pre-authorised to change in their own team, no approval needed, inside 48 hours of their own next meeting. It can be small. A template they’re allowed to drop. A status update that stops going up the chain. A customer commitment they can now make without escalating it. Small is often better, because a manager pointing at something real that changed is retelling evidence. A manager still waiting on approval is telling their team, without meaning to, that the strategy hasn’t actually reached them either.
Resist the temptation to make this change impressive. A dramatic, visible initiative sounds better in a briefing, but it usually needs sign-off from three other people before a manager can actually act on it, which means the 48 hours pass, nothing visibly moves, and the lesson the team learns is the opposite of the one you intended. A small change a manager can make alone, this week, without asking permission, teaches the lesson a big one can’t: that something about this strategy is already real.
Multiply that one small, visible change across forty managers and you get forty teams that each experienced something shifting in the same week the strategy was announced, not months later when the first quarterly review finally shows movement. That is what makes a cascade feel true rather than aspirational, and it costs nothing beyond deciding, in advance, what each manager is allowed to touch.
One Pack, Two Managers, Two Very Different Rooms
I’ve watched this play out with two managers who were handed the identical pack, in the same briefing, on the same afternoon. The first read the approved language close to verbatim, because deviating felt risky and nobody had told her otherwise. Her team sat quietly, nodded in the right places, and asked nothing. That silence got read afterwards as alignment. It wasn’t. It was a team that had correctly worked out they were being read to, and decided the meeting wasn’t the place to find out more.
The second manager opened differently. Here’s what I think this means for us, and here’s the part I’m still working out. His team asked questions for twenty minutes, some of them hard, and he didn’t have every answer, and said so. By the end of that meeting, one of those two teams actually understood the strategy. It wasn’t the quiet one. Same pack. Same messages. Same afternoon. The only difference was that one manager had been given permission and the rehearsal to use it, and the other had been handed a script and told to protect it.
Nobody planned for one of those managers to succeed and the other to struggle. The organisation handed them identical material and left the outcome to chance, the same way most organisations do. The difference between those two rooms wasn’t the strategy, and it wasn’t the manager. It was entirely what each of them had been given permission and practice to do with what they were handed.
How Helping Managers Carry the Strategic Narrative Actually Works
None of this needs a new system or a bigger budget. It’s a design decision, made before the cascade, not an afterthought bolted on after: write down what can’t move and say so explicitly, put permission in writing, rehearse the sentence everyone’s dreading, and pre-authorise one small, real change per manager. Done this way, the toolkit is usually shorter than the one it replaces, because it only has to protect what genuinely can’t move. This is what helping managers carry the strategic narrative actually looks like once you build for it on purpose: not a longer script, but a shorter one, backed by explicit permission and practice.
This isn’t a new observation about how organisations actually work. MIT Sloan Management Review’s research on culture change makes a related point about values: they only take hold once midlevel leaders translate them into their own team’s patterns, rather than repeating them word for word. The same is true of a strategy, and you can read that research at Building Culture From the Middle Out.
If you already have a leadership briefing, a manager summit or a strategy rollout on the calendar, and you’re still deciding what your managers will actually be given to carry into that first team meeting, settle it now, not the week before. Helping managers carry the strategic narrative into that room isn’t a nice-to-have bolted onto the cascade. It’s the whole reason the cascade exists. See how this fits into a keynote or working session on the page on bringing me in for a strategy cascade or leadership briefing, or go straight to check availability.
