Open the last exec update you sent and count the sentences an exec actually needed. My guess is three, buried in the middle, surrounded by activity. Shipped this, met with them, on track for that. The update was written to show effort, and execs can smell that in one scroll. So they skim it. Which means the one thing that mattered got skimmed too. I've written these for twenty years and read thousands more, and the bad ones all fail the same way. They're activity logs. The fix is a fixed template with a brutal budget.
The four sections above the fold
Start with the scoreboard. Five numbers at the top, each with a trend arrow and a line of context: a direction metric (the number your strategy says should move), the eval trend on your most important AI-touched surface, margin or cost per outcome, adoption of your current bet, and the top customer-signal theme. The rule that makes it work is that those five never change week to week. The moment you swap metrics you've started metric shopping, and the reader knows it. A flat or falling number with an honest one-line explanation buys more credibility than a rotating cast of green ones.
Then the three calls I made. This is the heart of it. Three decisions, 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. That turns the update from an activity report into a judgment record, and it feeds your decision log for free. An exec reads three lines and learns more about how you operate than a page of status ever would.
One thing I need. One ask, and it has to be a decision with a deadline and a default. I need a yes or no by Friday on X; if I hear nothing, I will do Y. No real ask this week? Then say no ask this week.
And what I killed or declined. One line: the request, the no, the reason. It's the least practiced section in the format and the highest-trust. Execs see endless additions. Almost nobody shows them the subtractions.
Everything else goes appendix-style, with rules. Nothing over three lines, nothing that requires action, and a standing link to the dashboard for anyone who wants raw numbers. The fold is a promise. Keep it and they read every update you send. Break it twice and they stop. An agent can draft the mechanical 80 percent of all this from your tools, but the 10-minute human pass is not optional.
So this week, take the update you're due to send and rewrite it into the format. Five numbers picked once and never changed, three calls with evidence and reversibility, one real ask with a deadline and a default, one kill line, everything else below the fold. Send it, then watch the response pattern change. Replies come sooner. People engage with the ask instead of the activity. And someone will ask about the kill line, which is often the first real conversation about tradeoffs an exec reader has had with a product team in months. Wire up the agent draft the week after. Format first, automation second, because automating a bad update just ships the badness faster.