ع
Learn Tracks Reference Guides Saved
playbook

Compress an initiative into a two-minute exec briefing

Pull requirements, options considered, business case, current status, and risks into a one-page update a VP or steering committee can absorb in under two minutes.

advanced ~1-2 hours
when to reach for this

An executive doesn't want your working documents — they want the answer in the time it takes to read one page. Done ad hoc, an exec update is either too thin to be trusted or a 12-page deck nobody reads past slide two. This system pulls from every other BA artifact — the requirements doc, options considered, the business case, current status, and the risk register — and compresses it into a single page or short deck that survives a two-minute read and a hard question in the room. It's the traceability guardrail applied upward: every claim in the briefing still traces back to a named artifact, even though none of that detail shows on the page.

gather this first
  • Your requirements-doc (locked or current draft) and any gap-analysis or options-analysis that shaped the recommendation.
  • The business-case — costs, benefits, and the recommended option — and the swot-risk-register for current risks.
  • A one-line read on current status: on track, at risk, or blocked, and why — from whoever is closest to delivery.
  • Who's in the room and what decision (if any) you need from them — approval, funding, a scope call, or awareness only.
the workflow

  1. State the ask before anything else

    Open the folder with your source artifacts in Claude Desktop and ask in the chat — no terminal needed. Force the first line of the briefing to be the decision you need, not scene-setting. Executives read backwards from the ask.

    you ask
    Before drafting anything, tell me in one sentence: given business-case.md and the meeting context [steering committee, need budget approval for phase 2], what is the single decision or action I need from this audience? Don't draft the briefing yet.

    what you get back One explicit sentence naming the decision or action needed — the anchor the whole briefing gets built around, so nothing downstream drifts into just 'an update.'

  2. Pull the status and risk snapshot

    Get the current-state facts on the table before compressing anything, so the briefing isn't built on stale or assumed status.

    you ask
    From swot-risk-register.md and my status note [paste], summarize current status in one line (on track / at risk / blocked, and why) and list the top 3 risks by impact, each with its current mitigation or owner. Keep it to bullet fragments, not sentences.

    what you get back A one-line status call plus the three risks that actually matter, each with an owner — the raw material for the briefing's status and risk sections, already prioritized.

  3. Compress the options and the case

    Reduce the options-analysis and business-case down to the one line each that a VP needs — what was considered, what was chosen, and why it pays off — without re-litigating the whole analysis.

    you ask
    From options-analysis.md and business-case.md, give me: the options considered (one line each), the recommended option and why in one sentence, and the headline numbers (cost, benefit, payback or ROI) in one line. No caveats paragraph — just the numbers and the one-line why.

    what you get back A tight options-and-case block — what was weighed, what won, and the headline numbers — compressed to the level a two-minute read can absorb.

  4. Draft the one-page briefing

    Assemble everything into the actual page: ask first, then status, then the case, then risks, then next steps. One page, no appendix on the page itself.

    you ask
    Draft exec-briefing.md as a single page: the decision/ask at the top, current status in one line, the recommended option and headline numbers, the top 3 risks with owners, and 3 concrete next steps with dates. Under 300 words total. Write for someone reading it once, at a glance.

    what you get back A single-page draft, under 300 words, ordered ask-first — readable in under two minutes and structured so the decision is impossible to miss.

    If it doesn't fit on one page at 300 words, the problem is upstream compression, not formatting — cut content, don't shrink the font.

  5. Attach the traceable backup, off the page

    Keep the guardrail intact without cluttering the page: every number and claim in the briefing should trace to a source artifact, in an appendix or linked doc, not inline.

    you ask
    Add a short 'sources' appendix to exec-briefing.md, separate from the one-page section: for each claim on the page (status, the recommended option, each headline number, each risk), name the exact source document it came from. This appendix is for follow-up questions, not for reading upfront.

    what you get back A one-page briefing plus a clearly separated backup section that traces every claim to a named document — so a hard question in the room has a real answer behind it, without the page itself getting longer.

  6. Stress-test it as the toughest person in the room

    Before it goes out, have Claude push back the way a skeptical VP would, so the gaps surface now instead of live in the meeting.

    you ask
    Read exec-briefing.md as a skeptical VP who's seen projects like this fail before. What's the first question you'd ask, what's the weakest number on the page, and what's missing that you'd expect to see before approving this? Give me the top 3 hard questions and a one-line answer to each, ready to say out loud.

    what you get back The three hardest likely questions plus a ready answer to each — so the meeting has no surprise the briefing didn't already prepare you for.

make it your own
  • Steering committee vs. single VP: for a committee, keep the one-pager but add a short 'decision requested from each stakeholder' line per attendee, pulled from the stakeholder map, since committees often split the ask.
  • Short-deck instead of one-pager: if the forum expects slides, turn each section (ask, status, case, risks, next steps) into one slide each — same word budget, five slides instead of five sections on one page.
  • Recurring monthly briefing: save the prompts as a repeatable template and re-run against the same artifacts each month — the ask and structure stay fixed, only the numbers and status line change.
  • Bad-news briefing: when status is genuinely 'blocked,' don't soften it in the compression — lead with it in one line, and make the ask 'here's what I need to unblock this,' not a vaguer 'update.'
watch out for
  • Don't let the one-pager assert a number that doesn't trace back to a named source artifact. The whole point of the sources appendix is that a hard question in the room has a real, checkable answer behind it — never let a figure survive compression without its trail.
  • Don't bury the ask. If the decision you need isn't the first thing on the page, the exec will read it as an FYI and you won't get the approval, budget, or scope call you actually needed.
  • Don't let 'compressed' become 'optimistic.' A blocked project stays labeled blocked in the one-line status — compression is about brevity, not spin. A briefing that reads better than reality is worse than useless the first time it's checked against delivery.
  • Claude compresses and drafts; it doesn't decide what to tell leadership. A human still owns the final call on what's in scope for this audience, whether bad news is framed honestly, and who actually has authority to make the ask land.

you'll end up with A single-page (or short-deck) exec briefing, ask-first, under 300 words, that compresses the requirements, options, business case, status, and risks into a two-minute read — with every claim on the page traceable to a named source document for the follow-up questions.

Questions people ask

Why does the workflow insist on naming the decision before drafting anything?
Executives read backwards from the ask — if the decision or action you need isn't explicit and first, the briefing reads as an FYI and you don't get the approval, budget, or scope call you actually needed. Naming it first also keeps every later section honest: status, case, and risks all get filtered through 'does this matter to that decision.'
Where does the detail go if the page has to stay under 300 words?
Into a separate sources appendix, not the page itself. Every claim on the one-pager — the status line, the recommended option, each headline number, each risk — names the exact source document it came from, so a hard question in the room has a real answer without the page getting longer.
What if the honest status is bad news?
It stays bad news on the page. Compression is about brevity, not spin — a blocked project gets labeled blocked in the one-line status, and the ask becomes 'here's what I need to unblock this' rather than a softened update. A briefing that reads better than reality fails the first time it's checked against actual delivery.
How is this different from just forwarding the business-case document?
The business case is one input among several (requirements, options, risk register, current status) and it's written to be read in full. This playbook compresses all of them together into something built to survive a single two-minute read plus one or two hard questions — a different artifact for a different audience, not a shorter version of the same one.