Most cascade briefings are a download. Sixty slides, forty minutes of talking, ten minutes of questions that nobody wants to ask first, and then everyone goes back to their desks holding the same pack. I get called in right before this exact moment. Usually by a head of internal communications, a chief of staff or a strategy director acting for a CEO or CHRO, because a leadership briefing, a manager summit or the first divisional town hall of a strategy roadshow is already dated in the calendar, and someone senior has quietly started to worry that a download is exactly what is about to happen again. If you are trying to work out how to communicate strategy to middle managers so the story survives the moment they return to business as usual back at their desks, the honest answer starts before you enter the room, in what you decide to brief them on.
The One Hour That Decides How Your Strategy Gets Told
I have written elsewhere about why a strategy gets shorter at every layer it passes through, and the short version matters here: this is the one point in the whole exercise where a manager can still ask the executive team a real question and get a real answer. After this hour, they are on their own in a team meeting, working from whatever they were able to retain, retell and defend. Get this hour right and forty managers become forty capable narrators of the same decision. Get it wrong and you have simply moved the confusion one layer down and made it harder to see, because now it is arriving in forty slightly different versions instead of one.
You Handed Middle Managers a Message. They Needed an Argument.
The standard briefing hands managers the conclusion: here is the strategy, here are the four priorities, here is the language to use. What it leaves out is the argument that produced the conclusion. An argument is the only thing a person can rebuild from memory under pressure. A message with no reasoning behind it is a fact: you either repeat it verbatim or you drop it, and in front of a real audience most people drop it. That is not a discipline problem in the middle of the organisation. It is a design problem in the hour before. Research on strategy execution keeps landing on the same finding from a different angle: the Harvard Business Review study behind the secrets to successful strategy execution, drawing on data from more than 125,000 employees across around a thousand organisations, found that clarity about who is responsible for which decisions and actions predicted execution far more strongly than the strategy document itself. A cascade briefing is where that clarity gets built, or skipped. This, more than the slide deck, is how you actually communicate strategy to middle managers who then have to defend it.
The Good Stuff Never Makes the Slide
The material that actually matters rarely makes it onto a slide, because it is the part that sounds less confident: what the executive team considered and rejected, why this option and not the other one, what they genuinely argued about before they agreed, and what is still uncertain even now. None of that weakens the strategy. It is what makes the strategy sound like a decision rather than an announcement. A manager who has heard the argument can answer a hard question honestly. A manager who has only seen the slide can only repeat the slide, more slowly, when the hard question arrives.
Nobody Packs Permission, and It Shows
Alongside reasoning, managers need something senior leaders rarely think to give explicitly: permission. Permission to say the strategy in their own words rather than the approved phrasing. Permission to say “that part is still being worked out” instead of inventing an answer to protect the appearance of certainty. Permission to tell their own team what will now stop, not just what will start. I think senior leaders withhold this without meaning to. It rarely comes from a wish to control the message, it comes from wanting to protect it. Protecting a message by locking its wording is exactly what makes it unrecognisable a week later, once forty people have tried to recite it instead of explain it. Permission is cheap to give and almost nobody packs it.
Running a Cascade Briefing That Actually Does Something
A briefing that produces retelling looks different from a briefing that produces attendance. It runs long enough for reasoning, not just conclusions, which in practice means less time on slides and more time on the argument behind them. It puts more than one senior voice in the room, because a manager who has heard only one interpretation has only one version to retell. And it treats questions as the main event rather than the leftover ten minutes at the end, because the questions a room asks out loud are the ones every manager in it is quietly relieved someone else asked first.
This is also where I earn my place in the room, and I say that plainly rather than as a closing pitch. An external voice can ask the question a manager will not ask their own chief executive, name the trade-off nobody on the leadership team wants to state out loud, and challenge the room in a way that reads as rigour rather than politics, precisely because I am not in their reporting line. If your briefing is already dated and you are weighing whether that role needs someone from outside the building, that is the decision the keynote speaker for a strategy cascade or leadership briefing page is built to help you make.
Skip that design work, though, and the gap shows up three weeks later, in a room the executive team never sees.
The Question Nobody Prepped Her For
Picture a briefing that ends the way most of them end: slides finished on time, pack under everyone’s arm, no real time left for the questions people actually had. Three weeks later, one of those managers is standing in front of her own team when someone asks the question nobody prepared her for.
“Why did we drop the regional expansion?”
She was in the room for the announcement. She was not in the room for the reasoning, because there wasn’t time for it. The honest answer available to her is the sentence that quietly ends a strategy’s credibility in one move: “That’s what came down from above.”
Now picture the same question put to a manager who was actually briefed on the reasoning, not just the decision.
“Why did we drop the regional expansion?”
“The board decided we couldn’t fund the regional build and the platform investment in the same year without picking one, and the platform is what protects the business we already have. It wasn’t an easy call, and I know it lands hardest on two people in this room. Here’s what I can tell you about timing, and here’s the part that’s genuinely still being worked out.”
Same question, same level of seniority, same amount of information the manager was actually given the authority to share. The difference is entirely upstream, in what the briefing was willing to say out loud.
If Nothing Changes in 48 Hours, Nobody Believed You
A decision is only believed once something visibly stops, starts or changes within the first 48 hours of it being made, and that rule applies to the briefing itself, not just to the strategy at large. A cascade briefing that ends in nodding and no action has produced alignment on paper and nothing measurable. So I run it, and I would suggest any senior leader running one runs it, this way: nobody leaves the room until they have written down one specific thing that will visibly stop, start or change in their own team within 48 hours of their own team meeting.
It does not need to be large. An approval step they will now skip. A weekly metric the team stops chasing. A piece of work they will hand back rather than absorb. That single written line is what turns the briefing from information into a decision, and it is what gives the manager something concrete to say when their own team asks what has actually changed.
None of this requires a bigger deck or a longer agenda. It requires treating the hour before the cascade starts as the highest-leverage hour in the whole exercise, because it is. What leaves that room with a manager, the language, the rehearsal, the answer to Thursday’s hard question, is its own discipline. I have set it out separately in what a manager actually needs handed to them once they walk out. However you plan to communicate strategy to middle managers next quarter, this is the hour that decides whether it survives contact with their teams.
I speak to leadership teams about closing the gap between what an organisation decides and what it actually does, under the banner of Execution Intelligence™. Cascade briefings, manager summits and strategy roadshows are the rooms I’m usually in the fortnight before two hundred people have to start retelling a decision they did not make. If yours is already on the calendar and you want a second, external voice in that room asking the questions your own team won’t ask each other, get in touch about the date.
