Strategic Narrative
Writing that does strategic work. The standard is simple: a new hire reading it on a Tuesday morning understands why it matters and how they connect to it.
A strategic narrative contains exactly what templates strip out. An explicit choice: a bet a competitor could not honestly copy, checkable with the Opposite Test. The crux: the named pivotal challenge, because a strategy that will not say what is hard is hiding something or missing something. What we are NOT doing: the trade-off that proves a choice was made, and the sentence most strategy documents cannot bring themselves to write. And enough context to travel: the reasoning, not just the conclusions.
Why narrative beats format
The cascade is an integrated argument, and arguments require prose. Compressing strategy into cards and bullet lists deletes the logic while keeping the labels, which is the mechanism behind most Strategy Impostors: the labels survive the compression, the argument does not, and six months later nobody can reconstruct why the labels were chosen. The classic demonstration is Operation CRUSH, which mobilised Intel as a memo, an argument people could carry, where a goal card would have produced compliance at best.
The last mile of strategy
Narrative is also the last mile of the management systems: people can only make daily decisions aligned to a strategy they can actually reconstruct in their heads. If the argument does not travel, the strategy stays in the room where it was written, and the organisation runs on whatever signal reaches it instead, usually the bonus plan. Recall, not agreement, is the test: ask someone two levels down to explain the strategy and listen for the argument, not the slogan.
How this connects to OKRs
Narrative is what makes alignment-without-cascading work in our methodology: teams that can reconstruct the strategy set their own OKRs without approval chains, which is the entire mechanism of autonomy at scale. It is also why every Objective here carries a written narrative and every Key Result an explanation of the belief behind it. The writing is not documentation of the thinking. It is the thinking, made portable.
One line to keep: The narrative is not documentation of the thinking; it is the thinking, made portable.
Our synthesis of Roger Martin’s published work, sources credited. Read the originals: they’re excellent.
Why prose instead of slides for strategy? +
Because the cascade is an integrated argument, and arguments need prose. Cards and bullets keep the labels and delete the logic, which is exactly how a strategy becomes uncopyable to its own teams six months later.
How does narrative enable alignment without cascading? +
Teams that can reconstruct the strategy in their own words can set their own OKRs without approval chains. The test is recall, not agreement: ask someone two levels down to explain the strategy and listen for the argument, not the slogan.
Reading about method is not the same as running it. We install this system and build the capability that stays.
Turn strategy into executed strategy →