The Exec Update Template: Five Numbers, Three Calls, One Ask

Open the last exec update you sent. Count the sentences an exec actually needed. My guess: three, buried somewhere in the middle, surrounded by activity. Shipped this, met with them, on track for that. The update was written to demonstrate effort, and execs can smell that in one scroll, which is why they skim it, which is why the one thing that mattered got skimmed too.

I have written these updates for twenty years and read thousands more. The bad ones all fail the same way: they are activity logs. The reader finishes knowing what the team did and not knowing what the author decided, what the numbers say, or what is needed from them. The update becomes a ritual both sides quietly resent.

The fix is a fixed template with a brutal budget: five numbers, three calls, one ask. Readable in 90 seconds. Everything else below the fold.

The short version

The exec update template has four sections above the fold. A scoreboard of five numbers with trend arrows, the same five every time: direction metric, eval trend, cost per outcome, adoption, and the top customer-signal theme. Three calls you made, each with the evidence and whether it is reversible. One ask, framed as a decision with a deadline and a default. And one line on what you killed or declined. An agent drafts the mechanical 80% from your tools, covered in the stakeholder update autopilot, and a 10-minute human pass adds the judgment. The format is the executive-communication layer of the skill stack compressed into one page.

What's in the template

The scoreboard

Five numbers at the top, each with a trend arrow and one line of context. The template fixes the categories: a direction metric (the number your strategy says should move), the eval trend (quality of your most important AI-touched surface), margin or cost per outcome, adoption of your current bet, and the top customer-signal theme from the period.

The rule that makes this work: the five numbers never change week to week. The moment you swap metrics, you have started metric shopping, and the reader knows it. A flat or falling number with an honest one-line explanation builds more credibility than a rotating cast of green ones.

Three calls I made

The heart of the update. Three decisions from the period, each in three lines: the decision, the evidence behind it, and the reversibility (two-way door, walked through it; one-way door, here is why). This section converts the update from an activity report into a judgment record, and it feeds your decision log for free.

A worked fragment from the artifact:

Call: Paused the integrations workstream for two weeks to put both engineers on eval coverage. Evidence: Eval score on the summary feature dropped for the second straight week while integration demand stayed flat in call themes. Reversibility: Two-way door. Integrations resume on the 18th regardless.

Three lines. An exec reads it and learns more about how you operate than from a page of status.

One thing I need

One ask, and it must be a decision, not an FYI. The template forces three parts: the decision needed, the deadline, and the default if no answer arrives. "I need a yes or no by Friday on X; if I hear nothing, I will do Y." The default clause is the unlock. It converts silence from a blocker into an answer, and it signals that you will move either way.

If you have no real ask, say "no ask this week." A fabricated ask trains readers to ignore the real ones.

What I killed or declined

One line. The request, the no, the reason. This is the least practiced and highest-trust section in the whole format. Execs see endless additions; almost nobody shows them the subtractions. It also keeps your anti-backlog honest, because every decline gets written down somewhere a senior reader saw it.

Below the fold

Everything else, appendix-style, with rules: no item over three lines, no item that requires action (actions belong above the fold), and a standing link to the dashboard for anyone who wants raw numbers. The fold is a promise to the reader. Keep it and they will read every update you ever send. Break it twice and they stop.

The agent draft and the 10-minute pass

The artifact includes the prompt block for an agent that drafts the update from your tools: numbers from analytics, decisions from your decision log, themes from call summaries. The full pipeline is in the stakeholder update autopilot.

The human pass is 10 minutes and it is not optional. Verify all five numbers against source, because one wrong number costs you a quarter of credibility. Rewrite the three calls in your own voice. And write the ask yourself, from scratch, every time. The ask is the judgment. The agent drafts everything around it.

How to use it this week

Take the update you are due to send and rewrite it into the format. Five numbers (pick them once, write them down, do not change them). Three calls with evidence and reversibility. One real ask with a deadline and a default. One kill line. Push everything else below the fold.

Send it. Then watch what happens, because the response pattern changes fast: replies arrive sooner, they engage with the ask instead of the activity, and someone will ask about the kill line, which is the first real conversation about tradeoffs most exec readers have had with a product team in months.

Wire up the agent draft the following week. The format first, the automation second. Automating a bad update just ships the badness faster.

Sources: Barbara Minto, The Pyramid Principle (answer-first structure), Bryar & Carr, Working Backwards (one-way and two-way doors), Annie Duke, Thinking in Bets (decision vs. outcome framing in the calls section).