Executive Narrative: From Data to Board-Room Storyline

Narrative is the deliverable, the deck is the medium

An executive narrative is the through-line that analysis is arranged to support. It is not the presentation, and it is not the appendix. Most strategy documents fail a simple test: they contain credible work organized into chapters that mirror the consulting team's working tracks rather than chapters that mirror the decision the board has to make. The board reads the document, finds it interesting, and then asks the question the document was supposed to answer. That is the signature of a narrative that was never composed. The work was real; the arrangement was accidental.

The discipline that fixes this is a five-move structure: situation, complication, question, answer, implications. The structure is not a template that flattens rigor. It is the form that lets rigorous work land as a decision. The five moves force the author to name what changed, why it is urgent, what the board must decide, what the recommendation is, and what follows from it. Written well, the five paragraphs stand on their own before a single slide exists. The slides then illustrate the moves; they do not invent them. A board that has read a composed narrative asks sharper questions and reaches a decision in the room, because the narrative has already done the work of ordering the argument.

The five moves in sequence

Each move does one job, and the order is what produces conviction. A move that is out of sequence produces a document the board respects and does not act on. Draft the moves in order, hold each to a single paragraph, and refuse to open a slide until all five paragraphs exist.

The situation move is short, dense, and uncontested; it establishes the premise the rest builds on. The complication is the engine, the reason the situation cannot simply continue. The question is named, singular, and answerable, because multiple questions in one narrative produce multiple narratives and therefore no decision. The answer is the recommendation, and its evidence is organized in the order that produces conviction rather than the order in which the analysis happened to be performed. The implications close the narrative by making the decision concrete: cost, timing, risk, and the next decisions the answer produces.

Consider a worked case. A regional health system is deciding whether to fund an AI clinical documentation platform. Situation: documentation load is the top driver of clinician attrition, and two competing systems shipped tools last quarter. Complication: attrition is now outpacing hiring, and the clinical staffing gap will breach safe-ratio thresholds within three quarters if the trend holds. Question: should the board fund the platform at fourteen million over two years. Answer: yes, phased, with the pilot service line named and the reasoning walked from attrition cost to platform payback. Implications: fourteen million committed, first value at month five, a named regulatory review, and a follow-on scope decision at the end of the pilot. Five paragraphs, and the board can decide without asking the analysts to reconvene.

From analysis to a testable storyline

The narrative is drafted, not generated. Work the five moves as prose, test them on a fresh reader, and only then reach for slides.

The test with a fresh colleague is the whole method. It substitutes an outside reader for the author's own familiarity, which is the single largest source of narratives that make sense only to the team that built them.

• Write all five moves as prose paragraphs before opening any slide software, so the narrative is forced to stand without visual scaffolding.
• Draft the question move first in isolation, then check that the situation and complication actually lead to it and that the answer actually resolves it.
• Reorder the answer so its evidence builds toward conviction, discarding the order in which the working team happened to perform the analysis.
• Read the five paragraphs aloud to a colleague who was not in the working sessions and ask them to repeat the question and the answer back to you.
• Only after the colleague passes the test, build slides, and build one slide per move so the deck inherits the structure rather than obscuring it.

Where narratives quietly fail

• Multiple questions in one narrative. This produces multiple narratives and therefore no decision. The fix: split into separate narratives, each with one question, and sequence them so the board decides one thing at a time.
• A missing or weak complication. Without it the story has no engine and the board has no reason to act now. The fix: name the specific event or trend that makes the status quo untenable this quarter.
• An answer ordered by working track rather than by conviction. The reasoning meanders and the recommendation arrives unsupported. The fix: reorder the evidence to build toward the recommendation, then delete anything that does not serve it.
• Implications reduced to a summary slide. Cost, timing, and risk get waved at, so the decision stays abstract. The fix: state the number, the first-value date, the named risk, and the next decision explicitly.
• Composing in slides from the start. The medium drives the message and the through-line never forms. The fix: write the five paragraphs first and treat the deck as the illustration of an already-finished argument.

Before the narrative goes to the board

• Five paragraphs exist, one per move, and each is written in prose rather than as slide bullets.
• The situation is uncontested and the complication supplies genuine urgency.
• The question is singular, named, and answerable in one sentence.
• The answer's evidence is ordered for conviction and the implications state cost, timing, risk, and the next decision.
• A colleague outside the working sessions read the five paragraphs and could repeat the question and the answer without prompting.