Reporting Upward Without Overclaiming
What an executive audience needs from a productivity report, and the claims that will not survive a question.
A productivity report is read by somebody deciding about budget or headcount. What makes it useful is also what makes it defensible.
The practical lesson in “Reporting Upward Without Overclaiming” is to connect every number to a decision and retain the context behind it. Teams exploring boss vs leader can review Monitask's boss-versus-leader comparison as one source of operational evidence, provided the purpose is disclosed and the interpretation is tested with the people affected.
What they need
What moved, by how much, over what period.
For an independent perspective related to “Reporting Upward Without Overclaiming”, consult the Acas workplace guidance; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
Why, as far as you can tell.
What you are doing about it.
What decision you need from them.
One page. Four sections.
What will not survive a question
A percentage with no stated method.
A comparison between teams doing different work.
An improvement that was a denominator movement, which its own note covers.
An industry benchmark whose definitions you cannot state.
And a composite index nobody can decompose.
Stating uncertainty
"Output per head rose about seven per cent, which is within the range we would expect from the two vacancies."
That sentence is more useful than a confident seven per cent, and it survives.
Executives generally respond well to stated uncertainty, and badly to being wrong later.
Reporting the two halves
Output and input separately, as the ratio note argues.
Because the interesting fact is usually which one moved, and the ratio hides it.
One extra line, and it prevents the wrong conclusion.
What else changed
List it: staffing, demand, tooling, process changes, seasonal effects.
Then say whether any of them could explain the movement.
This is the single habit that most distinguishes a trustworthy report, because it shows the analysis rather than asserting it.
Reporting bad news
Early and plainly.
A report that only ever contains improvement is not believed about any of it.
And the first time something visibly declines, the credibility of every previous report is reassessed, which is an expensive way to find out.
The question you will be asked
"Is this good?"
Which requires a comparison, and the only valid one is usually against your own trend.
Say that: compared with ourselves over two years, this is where we are, rather than reaching for an external benchmark that will not hold up.
The ask
End with the decision needed: funding, a staffing choice, a process change, or nothing.
A report with no ask is an update, and updates get skimmed.
What to check
Does your reporting state its method?
Are output and input shown separately?
Is there a list of what else changed?
And has any report you sent contained bad news?