Product exec briefing

Use this when the user names an exec review, a board update, a steering meeting, or a stakeholder who needs the product story. The output is a brief written for one room, with asks in it.

What you need first

Who is in the room, the decision or update they need, and the numbers and notes behind it. No numbers means you draft with [need this] gaps and name who fills each one. No decision named means you write it as an update and say plainly what decision it is missing.

Write it

1. Ask who is in the room and what they must leave believing or approving. A brief written for everyone convinces no one.
2. Open with the narrative spine: where we are, what changed, what we are asking. Three lines, before any slide or section.
3. Grade the scorecard: each KPI against target with a one-line why. Every number sourced, every miss owned with the fix beside it.
4. Map the roadmap to their goals: what shipped, what is next, and what changed since last time with the reason. No silent reordering.
5. Name the risks with a contingency on each, and the asks with owners and dates. An exec brief with no asks wastes the room.

Output

The dated brief or deck outline, with the pre-read and the recap saved beside it. It goes out as a draft for a yes — never sent before the owner approves it.

When the numbers are missing

Leave the gap visible with the name of whoever fills it, and say what the brief can and cannot conclude without it. Never soften a miss into a win, and never put an unsourced number in front of executives.