Calibrating Workload Honestly

Everyone feels busy. The difference between busy and over capacity has to be demonstrated, and the demonstration is straightforward arithmetic that few teams do.

Establishing real capacity

Start from contracted hours, not from what people work.

Subtract leave, at full entitlement, not at the rate currently taken.

Subtract public holidays and expected absence, using your own historical rate.

Subtract non-delivery time: meetings, administration, training, one-to-ones, recruitment. In most knowledge roles this is a substantial fraction and is routinely counted as zero.

Subtract a variation allowance. A team planned at full capacity has no ability to absorb the unexpected, which arrives weekly.

The remainder is deliverable capacity, and it is usually far below the headline figure the organisation plans with.

Establishing demand

Count the committed work, with realistic estimates rather than optimistic ones.

Count the recurring work, which is frequently invisible because it is nobody's project.

Count the unplanned work from historical rate. If a third of last year was unplanned, a third of next year will be.

Count the support load on other teams.

Include the work that is not being done, which is the queue, and which is the clearest evidence that demand exceeds capacity.

The gap

Present it as a figure, not as a feeling. "We have capacity for roughly X and committed work of roughly Y."

Show the working, so that the assumptions can be challenged rather than the conclusion.

Show what has absorbed the gap to date: overtime, deferred work, quality, or the queue.

Show the trend, which is usually more persuasive than the level.

The four options

Present these together, because a problem stated without options invites a request to try harder.

Reduce scope. Do fewer things.

Add capacity. Hire, contract, or borrow.

Extend timelines.

Accept the consequences knowingly: the current quality, the current attrition, the current overtime.

All four are legitimate. What is not legitimate is choosing the fourth by default while claiming the situation is temporary.

Where estimates are unreliable

Common objection, and it has an answer.

Use historical throughput rather than estimates. What did this team actually complete in the last six months? That is the capacity, whatever the plan says.

Compare committed volume against historical throughput. The comparison needs no estimation at all and is difficult to argue with.

Track the queue length over time. A queue that grows is proof of a gap regardless of any individual estimate.

The conversation to avoid

A wellbeing framing for what is a resourcing question. "The team is stressed" invites a wellbeing response. "We are committed to 140 percent of demonstrated throughput" invites a resourcing decision.

Use the wellbeing consequence as supporting evidence, not as the argument. The argument is arithmetic, and arithmetic is harder to answer with a mindfulness workshop.

Using throughput instead of estimates

The objection to workload arithmetic is usually that estimates are unreliable. Throughput sidesteps it entirely.

Count what the team actually completed over the last two or three quarters.

That is the capacity, whatever anyone estimated.

Compare it against committed volume for the coming period.

If commitment exceeds demonstrated throughput, the gap is the finding, and no estimating debate is required.

Track the queue length alongside it. A queue that grows steadily is proof of a structural gap regardless of any individual estimate.

Present both as a chart over time. Two lines diverging is an argument that survives contact with people who dispute estimates, because it contains none.

Making the queue visible

A growing queue is the least arguable evidence of a capacity gap.

Count the work that has been accepted and not started.

Track it weekly, as a single number.

Chart it over six months.

A flat queue means capacity matches demand. A growing one means it does not, and no estimating debate changes that.

Show the chart rather than describing the situation. It is the one artefact in this field that reliably ends the discussion about whether the team is simply not working hard enough.