Writing a Board Update That's Honest About Mixed Results
Most board updates lead with whichever number looks best and mention the weaker one further down, in smaller type or a subordinate clause. Boards read enough of these to notice the pattern, and once they do, the update reads as spin rather than an honest account.
Warning
Burying a weak number doesn't hide it from a board that reads these updates regularly. It just signals that the good numbers get the spotlight and the bad ones get buried, which costs more credibility than the number itself would have.
A board update that only has good news isn't more reassuring. It's just less believed.
Why leading with the good number backfires
The instinct to open with the strongest metric makes sense in isolation, but a board reading updates quarter after quarter learns to read past the opening framing for what's actually happening. Once trust in the framing erodes, every future update gets read more skeptically, including the honest ones.
Before: open with the strongest metric, mention the weaker one later, hope the framing carries the read.
After: give Claude every headline metric, good and bad, and ask for an update that presents them with equal weight and a narrative that connects them honestly.
A process for a board update with equal-weight metrics
- 1
List every headline metric, not just the strongest ones
Include the numbers moving in the wrong direction alongside the ones moving in the right one. Omitting a metric because it's weak is its own kind of framing.
- 2
Ask for metrics presented in a fixed order, not ranked by favorability
Request them in a consistent order, chronological or by category, rather than strongest-first. A fixed order signals nothing's being arranged for effect.
- 3
Ask the narrative to connect the metrics, not excuse the weak one
Request one paragraph that explains how the metrics relate to each other, not a defense of the underperforming one. A board wants to understand the story, not be talked out of noticing it.
- 4
Include one specific ask, not a vague request for support
End with something concrete the board can actually act on. A specific ask reads as command of the situation; a vague one reads as uncertainty.
“
Revenue grew 12% quarter over quarter but churn also ticked up 2 points. Turn this into a one-page board update: three headline metrics, a narrative paragraph, and one specific ask of the board.
”
Inside Claude Tutorial
Presenting mixed results with equal weight is transferable.
Giving good and bad news equal visibility, instead of arranging the order for effect, applies well beyond board updates. The app has a full lesson on it, with practice that carries over to any update where the full picture matters more than the best individual number.
When one metric explains the other
Sometimes the two metrics aren't unrelated, the churn uptick might be the direct cost of the growth push that drove revenue. Naming that connection directly is more useful to a board than presenting both numbers as separate facts.
Tip
Ask Claude directly whether the metrics you're presenting are actually connected, and if so, to make that connection explicit in the narrative instead of implying it. A board that sees the tradeoff named plainly trusts the read more than one left to infer it.
“
The churn increase happened in the same segment where we pushed the growth campaign that drove the revenue number. Rewrite the narrative paragraph to name that connection directly instead of presenting both metrics as unrelated.
”The same discipline outside the boardroom
A board isn't the only audience that notices when the bad news gets buried. A partner reviewing household finances together picks up on the same pattern, leading with the win and mentioning the overspend in passing, and it costs the same trust either way.
Tip
The process above works unchanged for a personal or family financial check-in: list every number that moved, good and bad, in a fixed order, and connect them honestly instead of defending the weak one.
“
We saved 15% more than planned this month but also had an unexpected $800 car repair. Turn this into a short update for a money conversation with my partner: both numbers with equal weight, one sentence connecting them, and no defensive framing around the repair.
”Continue reading
- Writing a Budget Variance Explanation That Doesn't Sound Defensive: the same plain-naming discipline, applied to a single line item instead of a full update.
- Adapting One Financial Report for the Board and the Team: reshaping this same update for an audience that reads differently than the board does.
- Turning a Batch of Expenses Into a Categorized Analysis: finding the driver behind a metric before it becomes a line in an update like this one.