A five-part format for any executive communication, written or verbal: Headline, Context, Findings, Recommendation, Ask — in that order. Answer-first, because executives need the conclusion before the journey.
▸ Try the interactive toolThe Executive Briefing Structure is a five-part format for any executive communication — written or verbal, a five-minute Slack message or a forty-five-minute board presentation. The five parts are Headline, Context, Findings, Recommendation, and Ask, in that order. The order is the point: it's answer-first, leading with the conclusion before the supporting journey.
The structure operationalises everything about how executives think (Tool 08). The Headline delivers the answer immediately — the one-sentence conclusion. Context gives just enough background to orient. Findings present the key evidence (not all of it). Recommendation states what you think should happen. Ask makes the specific decision or support you need explicit. The discipline is that an executive should be able to stop after the Headline and still know the essential point — the answer-first order respects their time and matches the frame, whereas a peer-style build-up to a conclusion at the end fails.
1. Headline — the answer in one sentence · 2. Context — just enough to orient · 3. Findings — the key evidence · 4. Recommendation — what should happen · 5. Ask — the specific decision/support needed. Answer-first.
The natural way to communicate — build context, present evidence, arrive at a conclusion — puts the answer last, exactly where a time-starved executive will never reach it.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Conclusion last | The exec runs out of patience before the answer. Lead with it. | Headline-first delivers the answer immediately. |
| No clear ask | The exec doesn't know what's wanted of them. | The explicit Ask makes the needed decision clear. |
| All the findings | Drowning the key evidence in completeness. | Findings present only the key evidence, not all of it. |
| No recommendation | Presenting findings without a view abdicates the PM's job. | The Recommendation states what you think should happen. |
State the single most important conclusion in one sentence, first. The executive should know the essential point even if they read nothing else.
Orient them with the minimum background needed — they're context-switching, so don't assume memory, but don't over-explain either.
Show the evidence that matters most, not everything you have. Curation is respect for their time; a data dump buries the point.
Say what you think should happen. Presenting findings without a recommendation makes the executive do your thinking — your judgement is part of what they need.
End with the specific decision, approval, or support you need. Vague endings waste the meeting; a clear ask is what turns a briefing into a decision.
A PM needed an executive decision and structured the request the natural way: background first, then the evidence, building carefully toward the recommendation at the end. The time-starved executive, halfway through the context, still didn't know what was being asked of them or why it mattered — and the meeting drifted without reaching the decision.
Restructured with the briefing format, it worked. The Headline delivered the answer and the stakes in one sentence; brief Context oriented; the key Findings (not all of them) supported it; a clear Recommendation stated the PM's view; and an explicit Ask named the exact decision needed. The executive grasped the essential point in the first sentence and could engage with the decision immediately — the answer-first order matched how they actually process information.
The deliverable is any executive communication structured Headline → Context → Findings → Recommendation → Ask — answer-first, with a clear ask.
| Part | Delivers | Discipline |
|---|---|---|
| Headline | The answer, one sentence | Lead with it |
| Context | Just enough to orient | Minimal, no assumed memory |
| Findings | The key evidence | Curated, not all of it |
| Recommendation | Your view | Don't abdicate judgement |
| Ask | The specific decision needed | Explicit, not vague |
The briefing structure is the executable form of 'how executives think' — it forces answer-first, outcome-focused, tightly-curated communication with a clear ask, which is precisely the frame executives operate in.
The answer-first order is the heart of it, and it runs against every instinct. We're trained to build an argument — context, evidence, then conclusion — which works for an audience with time and shared context. Executives have neither, so the conclusion-last structure puts the most important thing exactly where a time-starved, context-switching leader will never reach it. Inverting the order so the Headline carries the answer means the executive grasps the essential point immediately and can choose how much further to engage. The other disciplines compound this: curated findings (not all of them) respect their time, an explicit recommendation supplies the judgement they're paying for, and a clear ask turns the briefing into a decision rather than an FYI. Master this format and you become the PM whose updates executives actually absorb and act on.
A time-starved exec won't reach it. Lead with the Headline.
Vague endings waste the meeting. State the specific decision needed.
Curation is respect for their time. Present only the key evidence.
Findings without a view make them do your thinking. State your recommendation.
The structure embodies the frame from Tool 08.
The roadmap presentation (Tool 10) is built on this format.
Answer-first echoes SCR's resolution-forward approach (Module 5, Tool 26).
Executive updates in the cadence (Tool 06) follow this structure.
AI is well-suited to the executive briefing — it's good at compression and answer-first restructuring.
The judgment that stays yours: AI can shape the format, but the recommendation and the judgment behind it are yours — and an executive can tell when a briefing is fluent but empty. Use it to package your thinking answer-first, not to manufacture a view you don't hold.
Take something you'd need to tell an executive. Write it the natural way (context → evidence → conclusion), then flip it into the five-part format with the Headline first and a clear Ask last.
Read just the Headline — does it convey the essential point on its own?
If the Headline alone tells the executive what they most need to know — and the natural version buried that under build-up — you've felt why answer-first is the whole discipline of executive communication.