Draft the QBR Narrative Before You Touch a Single Slide

Workflow area: Delivery & Reporting · Tier: Core · Hands-on time: ~35 minutes

The instinct under deadline is to open the slide tool and start arranging. That produces decks that are lists, not arguments — and exec audiences punish lists. The durable craft is narrative-first: decide the one-sentence story, arrange evidence in service of it, and only then make slides, which become cheap once the narrative exists (and near-automatic with Gamma or Copilot-class deck tools). AI accelerates every stage — but it will also confidently include a metric you gave it from memory, wrong, and that single unsourced number is what the room remembers when it snaps.

When to use — and when not to

• Use it for QBRs, board updates, and budget asksany artifact where a skeptical senior audience will interrupt with questions and remember your worst answer.
• Use it when your material is a pile, not a storytwelve metrics, six projects, three asks; narrative drafting is precisely the pile-to-argument conversion.
• Use the question-anticipation pass even with a finished deckit is the highest-value 15 minutes of exec prep in this playbook, independent of everything else.
• Skip it for material you haven't verified yetnarrative built on unchecked numbers hardens errors into story; run the source-tracing before the arc, not after.
• Skip fully AI-generated decks sent unrevieweddeck tools produce plausible-looking slides with generic claims; every slide that survives carries your judgment or it doesn't ship.
• Skip pasting board-sensitive material into unapproved toolspre-announcement financials, M&A context, and headcount plans are the highest-tier confidential data you touch; enterprise tenant only, minimum necessary detail.

The recipe

1. 1.

   Assemble the raw material with sources attached. Metrics with links to their dashboards, project statuses from pb-09's corrected reports, costs from finance's numbers (not your memory of them). One line per fact: claim, number, source, date. This inventory is tedious and it is the foundation — every downstream step inherits its accuracy.

2. 2.

   Draft the narrative arc.

   Copy

   Help me draft the narrative for a [QBR / board update] to
   [AUDIENCE — e.g. "CEO, CFO, and two board members; 20 minutes
   plus questions"]. My goal: [ONE SENTENCE — e.g. "credibility on
   delivery plus approval for two platform hires"].
   
   FACT INVENTORY (claim | number | source | date):
   [PASTE INVENTORY]
   
   Produce:
   1. THE STORY IN ONE SENTENCE — the single thing the room
      should believe when I sit down.
   2. NARRATIVE ARC — 4-6 beats (situation → progress → honest
      friction → what's next → the ask), each beat with: its
      message in one line, and which inventory facts support it.
   3. ORPHANS — facts I supplied that support no beat (candidates
      to cut), and beats that lack facts (gaps I must fill or
      claims I must drop).
   4. THE HONEST-FRICTION BEAT — do not skip it: the thing that
      went worse than planned, stated plainly with its lesson.
      Exec audiences trust decks that contain one true problem.
   
   Rules: use only inventory facts. Flag any beat where the story
   wants a claim the facts don't support — do not bridge the gap
   with language.
   

3. 3.

   Run the interrogation pass. In the same chat:

   Copy

   Now act as the toughest audience in that room. Generate the 10
   questions most likely to be asked, ranked by damage potential.
   Include: the CFO question about cost per unit of output, the
   "why not half the budget" question, the question that connects
   my friction beat to my ask, and at least one question about a
   number's provenance. For each: what a weak answer sounds like,
   and bullet points for a strong answer using only my inventory.
   Mark any question my inventory cannot answer — those are my
   prep homework, not improv material.
   

   Good output looks like:

   Copy

   Q3 (CFO): "Cloud spend rose 18% while traffic rose 6% — why?"
   WEAK: "We're looking into it."
   STRONG: — 11 of the 18 points are the migration's double-run
   cost, ends next quarter (source: FinOps report, June) — 
   remaining 7 tracked against the efficiency target set in Q1.
   Q7: UNANSWERABLE FROM INVENTORY — "What's the revenue impact
   of the reliability work?" → get the number or pre-concede it.
   

4. 4.

   Trace every number before slides exist. Walk the arc's facts one by one back to their sources — the dashboard, the finance export, the report. Numbers repeated from memory, "roughly" numbers that hardened into exact ones, and stale figures with fresher versions available are the three standard failures. Fix them now: a wrong number found in a doc costs a minute; found by the CFO, it costs the meeting.

5. 5.

   Only now, make slides. Feed the verified arc to your deck tool (Gamma, Copilot, or a designer) beat by beat — one beat per slide, the beat's message as the slide title written as a sentence ("Migration is done and under budget", never "Migration Update"). Rehearse once against the interrogation list, out loud, with the unanswerable questions' answers now in hand.

Make it yours

• Startup founder to board: compress to five slides but keep all four passes — the interrogation pass matters most, because board questions to founders are predictable in category and devastating when unprepped.
• GCC or services leader to global HQ/client: add a beat for value-demonstration in HQ's terms (cost, throughput, quality trend vs. contract), and run the interrogation pass twice — once as HQ finance, once as the client sponsor, because they attack different beats.
• Recurring QBRs: keep a running fact inventory updated monthly instead of rebuilding quarterly, and open each QBR's arc with deltas against what you told them last time — audiences trust leaders whose story is continuous, and the model can diff your last narrative against the new inventory in one prompt.

Quality check

• Every number traces to a live sourcethe claim-number-source-date inventory is the audit trail; any figure in the deck missing from it is unverified by definition.
• The friction beat surviveddecks polished to flawlessness read as spin to anyone senior; verify the one true problem is still there, stated plainly.
• Orphan facts got cut, not squeezed ina fact without a beat is clutter that dilutes the argument; the model flagged them so you'd delete them.
• The unanswerable questions got answered or pre-concededwalking in with known gaps unaddressed converts them from homework into ambush.
• The story is yoursread the one-sentence story aloud; if it's a claim you wouldn't stake your credibility on without the AI's fluency wrapped around it, rewrite it until it is.