Ask one person on the shop floor what the organisation is doing this year, and you’ll get an honest answer: they’ll tell you what they remember, not what was said. Ask the next person, and you’ll get a different honest answer. Neither of them is wrong. The strategy simply never arrived as something a person could hold onto. If you are a CEO, a CHRO, a chief of staff, a strategy director or the head of internal communications with a leadership briefing, a manager summit, a strategy roadshow or a run of divisional town halls in the diary, turning strategy into a story employees understand is the actual job in front of you. What you want in these moments isn’t a communications plan or a slide deck. What you really need in this moment is a story that survives being told by someone who did not write it.
I have written elsewhere about the layers a strategy passes through and where it thins out on the way down (see Strategy Cascade: How to Get the Story to Arrive Intact). This piece is narrower: it is about authorship, how you build the story in the first place so it has a shape worth cascading at all.
Most Strategy Narratives Are Lists Wearing a Story’s Clothes
Almost every corporate strategy narrative I am handed before a keynote has the same skeleton. A purpose statement at the top, four pillars in the middle, a dozen initiatives underneath each one, and a set of values at the bottom that would fit almost any organisation in almost any industry. It is comprehensive. It is also not a story, and the difference matters more than most leadership teams assume.
A list is a set of items with no relationship between them beyond membership of the same slide. A story is a sequence in which each part exists because of the part before it. Robert McKee, writing in Harvard Business Review, made the case plainly: facts persuade the rational mind, but a story creates an experience an audience actually retains and repeats. A pillar deck asks people to remember four unrelated things. A story asks them to remember one thing that happens to have four moments in it. Only one of those survives being told twice.
Why a List Cannot Survive Being Retold
A person retelling a list drops items, and which items they drop depends on what they personally understood or found memorable, not on what the executive team intended to be load-bearing. A list gives a retelling nothing to check itself against. Nothing feels obviously missing, because nothing in a list depends on anything else.
The version of this I see most often happens in a corridor, and it goes like this. A capable senior manager, someone who has read every slide twice, is asked on the way out of a briefing what the strategy actually is. She names the four pillars, in the order they appear on the slide, correctly.
Then she pauses and says what she actually thinks: “Basically, we are trying to do more with the same.” That second sentence, the one nobody wrote or rehearsed with her, is the one her team hears on Monday. It is not her fault. The narrative gave her four things to memorise and nothing to believe, so under the mild pressure of a real question she reaches past the pillars for the truth underneath them. Every manager will do this. The only question is whether the true version you have given them to reach for is the right one.
Five Beats, Not Four Pillars: The Strategic Narrative That Travels
The structure I use, and the only one I have found that reliably survives translation, has five beats. What changed in the world that made the old approach stop working. What it costs the organisation if nothing changes in response. What we have decided to do about it. What we have decided to stop doing, in order to afford it. And what is different this week, specifically, with a name attached to it.
Each beat exists because of the one before it. Take any beat out, and the next one stops making sense, which is exactly the property a list does not have. It is also a structure a manager can hold in their head well enough to retell in their own words, because it is a sequence of consequences rather than a shelf of categories.
The Beat Everyone Removes: What We Have Decided to Stop
The fourth beat is the one that disappears first, almost every time, and for an understandable reason. Naming what the organisation will stop doing means naming a trade-off, and a trade-off is the hardest part of a strategy to defend out loud to people you manage, because someone in the room has usually been quietly proud of the thing now being stopped. It is far easier to let the story read as pure addition: more markets, more products, more capability, nothing subtracted. That version is comforting and it is not a strategy. A strategy is a decision about what the organisation will not do, and if the story never says so, it is not carrying the actual decision, only the parts of it that felt safe to circulate.
I try to be generous about why this beat goes missing. Executives cut it to protect people, not to hide the trade-off. But the protection has a cost, paid by every manager downstream who has no honest answer when someone asks what their team should stop doing to make room for the new priority.
Why the Story Has to End This Week, Not Next Year
This is where I bring in the mechanism I use everywhere in my work: The First 48 Hours. A decision is only believed once something visibly stops, starts or changes within 48 hours of it being made. Applied to comprehension rather than belief, the same rule tells you how to end a strategic narrative. A story that closes on an aspiration or a three-year target is not a story. It is a forecast, and audiences discount forecasts heavily, because a forecast asks for trust with nothing offered in return right now.
So the fifth beat, what is different this week, is structural, not decorative. It needs an owner and a specific, checkable detail: a budget line reallocated on Friday, a hiring brief rewritten, a project paused with a name against the decision. This is what turns a listener’s reaction from “interesting” into “real”, and it is also the most retellable material in the whole narrative. People forget forecasts. They remember and repeat things that are true this week, because they can check them.
The Story Needs One Owner Who Can Say It Unscripted
Not the communications team alone, and I say this as a warm correction, not a criticism of communications professionals, who are usually left to rescue a narrative that arrived too late and too thin. The story has to be owned by the executive who owns the trade-off in beat four. If that person cannot say the whole five-beat version out loud, unscripted, the narrative is not finished, no matter how polished the deck looks. A story someone else wrote for you is a story you cannot defend under a real question, and a real question is exactly what a manager will get in their own team meeting.
The Three-Sentence Test Before You Cascade Anything
Before any of this goes near a briefing room, I ask a leadership team to run a small test. Have someone who was not in the room retell the strategy in three sentences, from memory, an hour later. Listen for the stop beat. If it survived, the narrative is doing its job. If it evaporated and what came back was purely additive, you have a list dressed as a story, and the corridor will find the gap for you later, in front of an audience you do not control. It is a cheap test, and far less expensive than finding the gap five layers down after the roadshow has run. What a manager is then given to carry that story in their own words is its own discipline, covered separately in Helping Managers Carry the Strategic Narrative.
Fixing the Story Before the Room Fills Up
If you already have a leadership briefing, a manager summit or a strategy roadshow booked in, the narrative is the one piece of the cascade that has to be right before any logistics matter. Everything downstream – the pack, the rehearsal, the Q & A – is a multiplier on whatever the story already is. I work with leadership teams in the weeks before that date to pressure-test the five beats and rebuild the ending so it lands this week rather than in three years, and the executive who owns the trade-off usually finds it easier to say out loud with someone from outside the reporting line asking the questions. This is what turning strategy into a story employees understand actually requires: one owner, one ending that lands this week, and a trade-off nobody was allowed to soften. If that is useful before your own room fills up, start a conversation about the date.
