Who Gets Blamed When the Number Falls
A falling measure needs an explanation, and the explanation available is usually the people. What that costs.
When a figure declines, somebody must account for it. Who that is determines whether the organisation learns anything.
The practical lesson in “Who Gets Blamed When the Number Falls” is to connect every number to a decision and retain the context behind it. Teams exploring fireable offenses can review more details are available here as one source of operational evidence, provided the purpose is disclosed and the interpretation is tested with the people affected.
The default attribution
The team, because the measure has their name on it.
For an independent perspective related to “Who Gets Blamed When the Number Falls”, consult the Acas workplace guidance; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
Which is frequently wrong: the cause is demand, staffing, a system change, a new work mix or a queue upstream.
But those explanations require investigation and the team is available immediately.
What blame produces
Explanations rather than investigation.
Defensive reporting, where the figures get presented in the most favourable light.
Concealment of the early signs, because an early warning is an admission.
And eventually, managed numbers, which is where the measurement stops working entirely.
The honest sequence instead
Check the denominator first, which its own note covers.
Then what else changed: demand, staffing, systems, work mix, season.
Then the process: has a queue grown, has rework risen.
Only then the team, and usually by asking rather than telling.
Four steps, and the fourth is rarely needed.
The asymmetry worth noticing
A rising figure is attributed to management action.
A falling one is attributed to the team.
That pattern is visible in most organisations and it is worth naming, because it tells people exactly how the measurement will be used.
The manager who absorbs it
Somebody senior taking the question rather than passing it down is the single most useful protection.
"I have looked into it; here is what changed" is a complete answer that costs the manager an afternoon and preserves the data's accuracy.
Passing it down costs nothing immediately and corrupts the figures permanently.
What a good response looks like
The figure fell. We looked. It was the two vacancies and the system migration. Here is the adjusted view and here is when we expect it to recover.
Specific, checkable, nobody blamed, and it took a day.
The investigation that finds a real problem
Sometimes the cause is genuinely within the team: a skill gap, a process they stopped following, a problem nobody raised.
That is a legitimate finding and should be handled as a conversation about the work.
It is also the minority case, and treating it as the default is what produces everything above.
The signal that blame is operating
Teams explaining before being asked.
Figures presented with caveats attached preemptively.
And nobody raising a problem until it is unavoidable, which is the expensive one.
What to check
When a figure last fell, what happened?
Were the first three steps taken before the fourth?
Do teams pre-emptively explain their numbers?
And would somebody raise a developing problem early?