1. What executives actually want
The single biggest mistake engineering leaders make in exec communication is answering the question they were trained to answer as engineers: what did we do? Executives, most of the time, don't care what you did. They care what they need to decide, and whether they can trust your judgement on the things they aren't going to look at closely.
An exec update is not a report card. It is a decision-quality signal — a compact answer to three questions: what changed since last time, what should I be worried about, and what do you need from me?
2. One page. Always one page.
Length is a tell. A three-page update signals you don't know what matters. A one-page update signals you made choices. Executives read on their phone between meetings. If your update requires a laptop and a coffee, it will not be read.
A working template, in this order:
- TL;DR (2–3 lines). The headline. If they read nothing else, this is what they know.
- Wins. What shipped, what moved, with the outcome — not the activity.
- Misses. What slipped, why, what's changed as a result. Own it in plain language.
- Bets in flight. What we're working on, with a confidence signal (on track, at risk, off track) and a one-line "why".
- Risks. Specific, near-term, actionable. Not "hiring is hard."
- Asks. The decisions or unblocks you need. If none, say none.
3. Metrics that travel up well
Not every metric belongs in an exec update. Story points don't. Sprint burndown doesn't. What travels well:
- The outcome metric the work is meant to move (revenue, activation, latency, incident count).
- Delivery predictability over time — the trend, not the snapshot.
- Reliability numbers, with a threshold and a direction.
- Hiring: offers out, offers accepted, time-to-fill for open roles.
Same numbers, every week, in the same order. Consistency is what makes a trend legible. A cleverer format each week is a leader who's still figuring out what matters.
Executives are pattern-matchers. If they can compare this week to last week to last month at a glance, you have given them information. If they can't, you have given them a document.
4. Flag risk early, specifically
Vague risk sounds like panic. Specific risk sounds like ownership. Compare:
Vague: "There is a risk we might not hit the launch date."
Specific: "Payments integration is 60% likely to slip by two weeks because the third-party sandbox is unstable. Options: (1) launch with card-only and add wallets in v1.1, (2) hold the date. Recommend (1). Confirm by Friday."
The specific version gives the executive a decision to make and a recommendation to approve. The vague version gives them anxiety and a meeting to schedule.
5. Never surprise your exec in public
If there is bad news, they hear it from you first, in writing, before the wider forum. A senior leader being surprised in a room full of peers is the fastest way to burn trust in a working relationship. This is a rule, not a preference.
A useful phrase: "Wanted to flag this to you before Thursday's review." Send it early. Follow up. Confirm they've seen it.
If you find yourself softening bad news in the update because you don't want to worry the exec, you are not managing up. You are managing your own discomfort — and building a bill that comes due later.
6. If it needs a meeting to explain, rewrite it
The test of an exec update is: could a busy executive read it once, on their phone, and know what to do? If the answer is "well, they'd need to ask me a few questions," the update is not done. Rewrite it. The rewrite is your work; making them extract it from a meeting is theirs, and they should not have to do it.
7. Final takeaway
Great exec communication is not about polish or vocabulary. It is about respecting the executive's most scarce resource — attention — and packaging your reality in a form that lets them act on it in ninety seconds. Do that consistently, and you become a leader they trust with bigger scope. Don't, and you become a leader they micromanage.