The Conversation a Good Report Produces
The test of a capacity report is the quality of the discussion it starts. Four questions a good one produces and four a bad one does.
A report can be judged by the conversation it causes. For capacity reporting the difference is clear: a bad report produces questions about the number and a good one produces questions about the work.
The practical lesson in “The Conversation a Good Report Produces” is that a convenient number should open a question rather than end one. A team considering open the relevant product explanation for mouse jiggler detection can add consistent time and project context, with transparent settings, limited access and a documented review process around every material interpretation.
Four of each, as a test.
As a separate benchmark for “The Conversation a Good Report Produces”, see Cloudflare zero-trust overview. External guidance is most useful when it prompts a specific check rather than replacing case-by-case judgement.
The four bad questions
Why is this below target. Why is your team lower than theirs. What are you doing to improve it. Can you commit to a figure next quarter.
- Why is this below target?
- Why is your team lower than theirs?
- What are you doing to improve it?
- Can you commit to a figure next quarter?
Each is about the number. None has an answer that changes anything, and all four are answerable by reclassification.
The four good questions
Bench time doubled in one team this month — what happened. Supervision hours fell by a third — is review still happening. Yield on this account has fallen for three quarters — when was it last repriced. We are holding capacity for work we expect in June — is that still expected.
Each names a specific movement and asks about a cause.
What makes the difference
Composition and movement rather than level and threshold. A report that shows what changed and what it is made of produces questions about causes.
A report showing a level against a target produces questions about the gap.
Who can answer
The good questions are mostly answerable by the people in the room, and mostly about allocation, pricing or scheduling.
The bad questions are directed at people who do not control the inputs, which is why the answers are unsatisfying and the conversation repeats monthly.
The sentence that does the work
One line of narrative per month naming the largest movement and its cause. Written by whoever produces the report.
It takes five minutes, it is the only part most readers will read, and it is what turns a table into a discussion.
Why the narrative has to be specific
"Utilisation improved" produces nothing. "Chargeable hours rose 140, almost all from one team moving off the bench onto the new engagement" produces a follow-up.
Specificity is what makes a movement checkable, and checkable claims are the ones that get discussed.
What to do when nothing moved
Say so. A month with no significant movement is information and the narrative should say that in one line.
Reports that always find something notable teach readers to discount the narrative.
The meeting structure that follows
Fifteen minutes: the movement line, two or three questions, one or two actions with owners.
Capacity discussions that run an hour are usually arguing about definitions, which is a sign that rule four from the previous note is not being followed.
The participants
Whoever allocates work, whoever owns the pipeline, and whoever can reprice. Those three can act on everything the report shows.
A capacity meeting without the allocator is a review of consequences with nobody present who caused them.
The actions that typically come out
Reallocate somebody off the bench. Chase a client for blocked input. Reprice an account. Restore a training commitment. Adjust the committed capacity assumption.
All small, all specific, all traceable to a line in the report.
The annual test
Name three decisions from the last year that went differently because of this report. If there are none, the report is habit.
That is the same test the earlier note applies to the measure itself, applied to the reporting rather than the number.
Why the bad questions feel more rigorous
Because they are precise. A gap against a threshold is an exact quantity, and exactness reads as rigour.
The good questions are untidy: they name a movement, assume a cause, and invite an explanation that may turn out to be wrong.
That untidiness is what makes them productive. A question with a known correct answer produces a report; a question with an unknown answer produces a finding.
The report nobody asks about
The commonest failure is neither good nor bad questions but silence. A page that produces no questions is not being read.
The diagnosis is usually that it contains levels without movements, or movements without causes, so there is nothing for a reader to engage with.
Adding the narrative line is the cheapest repair and it works within a month. Where it does not, the report has no audience and should be stopped, which is a legitimate outcome and almost never reached because stopping a report requires somebody to decide it was never needed.
The three people who should be there
Whoever allocates work, whoever owns the pipeline, whoever can reprice.
Between them they can act on every finding a capacity page can produce: bench time, blocked work, overcommitment, a drifting account, a protected category that fell.
A meeting without all three reviews consequences with nobody present who caused them, which is why so many capacity discussions end in a request for somebody else to look into it.
What this amounts to
A measure worth keeping produces questions somebody in the room can answer, about work somebody in the room can change. That is the whole standard, and most utilisation reporting fails it in the first question.