Section 1
The plan has to be arguable
A financial model is a conclusion. The reasoning that produced it usually lives in a few heads and never gets written down. When the reasoning is not visible, disagreement shows up later as slow execution rather than open debate, because the people who doubt the plan have nothing specific to challenge. A planning narrative makes the reasoning inspectable: this is what we believe about the market, this is why we think the constraint is here and not there, this is what has to be true for the number to happen, and this is what we would expect to see by month three if we are right. Written that way, the plan can be attacked on its assumptions, which is the only useful kind of attack. Execution then becomes a change programme, and [How to Lead Organizational Change Through Storytelling](/blog/how-to-lead-organizational-change-through-storytelling) picks up from there.
Section 2
What you are not doing belongs in the story
Plans get diluted at the edges. A team hears the priorities, agrees, and then keeps doing everything it was already doing, because nothing was explicitly stopped. The result is a strategy on paper and a portfolio of habits in practice. Naming the declines is the discipline. Which segment are we no longer chasing, which product line stops getting engineering time, which channel gets no budget this year. These sentences are uncomfortable in a planning session, which is a sign that they carry information. A strategy nobody in the room finds slightly painful is usually a budget with ambitions attached.
Section 3
Assumptions written as testable claims
Convert each core belief into a claim with an observable outcome and a date. If we are right about mid-market demand, pipeline from that segment should double by the end of Q2. This turns the plan into a set of tests rather than a set of promises, which makes revision a normal act rather than an admission of failure. Long-horizon commitments need the same treatment, as [The Role of Storytelling in Sustainability Initiatives](/blog/the-role-of-storytelling-in-sustainability-initiatives) illustrates.
Section 4
Running the process without theatre
Replace the opening presentation with a written narrative of six to eight pages, circulated in advance and read in the room. Reading time is cheaper than presentation time, and prose exposes weak reasoning that bullet points hide. The discussion then starts at the assumptions rather than at slide design. Assign each major assumption an owner and a review date. At the quarterly check, the question is not whether the initiative is on track but whether the belief underneath it still holds. Plans usually fail because a premise quietly stopped being true in month two and nobody had the standing to say so.
Section 5
Common distortions in planning narratives
The first is narrative fitted to a pre-decided answer, where the story exists to justify a choice already made for other reasons. The tell is a plan with no rejected alternative. The second is the confident forecast built on a single unexamined input, usually a conversion rate carried forward from a period that no longer resembles the current one. The third is a plan whose story cannot be told to the people executing it, because the real reasoning is political. That plan will be executed at half speed by people guessing at the actual priorities. Anchoring the reasoning to measured inputs helps, and [The Role of Data in Effective AI Automation](/blog/the-role-of-data-in-effective-ai-automation) is a useful companion on where those inputs come from.