Start with movement, not inventory
A report that repeats every metric is a slower dashboard. Begin with the changes: what rose, what fell, what broke a threshold, and what stayed unexpectedly flat. The reader should know in the first few lines where attention belongs.
Comparisons need a useful baseline. Last week may be right for support volume; the same period last year may be right for seasonality. The reporting routine should name the comparison so the reader never has to guess.
Connect the number to the event
The explanation usually lives in another tool: a release in GitHub, a campaign change in an ads account, a cluster of tickets in Zendesk, or a decision captured in a meeting. Pulling those sources together is the real work of reporting.
Every explanation should remain inspectable. Link the source, distinguish evidence from interpretation, and say when the cause is not yet known.
End with decisions
A strong report closes with a small number of choices, owners, or follow-ups. If there is no decision to make, say that too. The point is to remove uncertainty, not manufacture urgency.
When the structure works, schedule it. A routine can gather the same inputs, apply the same comparisons, and post to the same channel while a person keeps ownership of the decisions.
One line to keep
“A recurring report earns its place when it shortens the next decision.”
Published August 14, 2026
Back to the blog