Why board updates underperform
The two most common failure modes:
- Buried bad news. The TL;DR mentions the wins; the issues appear on slide 14. The board spends the meeting redoing the diagnosis — usually wrong, because they have less context than you do.
- Performative depth. Forty slides of charts that aren't load-bearing. The board reads the first six and skims the rest.
The template above solves both by forcing the lead with the full picture (good and bad) and capping the body at six sections.
How sophisticated boards read it
The first sentence sets expectations for the rest of the document. The numbers section verifies them. The "what's working" and "what's broken" sections are where the conversation happens. Decisions/asks is where the board adds value. Everything else is appendix.
The decision-to-asks ratio
A useful test: count the lines in section 5. A board update with zero specific asks is a status report — fine, but the board can't help. Aim for two to four asks per update. They can be small ("intro to X candidate") or large ("approval to deviate from plan on Y"). Either way, give the board something to do.
The diagnostic standard
When something is broken, the diagnostic in section 4 should answer two questions: (a) why is this happening, with evidence; and (b) what's the leading indicator that tells us we've fixed it. "Margin is down" is not a diagnostic. "Margin is down 380 bps; 220 bps of that traces to Klaviyo flow X which we paused Tuesday; the leading indicator is week-over-week true ROAS on remaining flows, currently 2.1× target 2.5×" is a diagnostic.
Get the template
Ships as a Google Doc with placeholder text for each section. Adapt the numbers section to your business model (SaaS vs D2C metrics differ — see the metrics list).