Workload That Never Comes Down

The most common single cause, and the one most often described as temporary for years at a time.

How permanent overload establishes itself

A gap opens — a departure, a growth period, a project.

The team absorbs it, because they are competent and it is temporary.

The absorption becomes the baseline. The new volume is now normal and the headcount case is harder to make, because the work is getting done.

Nobody decided this. It emerged from a series of reasonable short-term responses.

Why full utilisation fails

No capacity for the unexpected, and the unexpected is routine.

No recovery between peaks, which is what distinguishes demanding work from harmful work.

Quality degrades invisibly before it degrades visibly.

Improvement stops. Nobody has time to fix the thing that generates the extra work.

Absence becomes catastrophic, so people come to work ill, which spreads the problem.

A system planned at full utilisation has no ability to recover from disturbance, which is a general property of systems rather than an observation about people.

Measuring it honestly

Hours worked against contracted, which most organisations do not know.

Whether leave is taken, in full, and whether it is interrupted.

Whether the team can absorb one absence without escalation.

How much of the work is unplanned versus scheduled.

How long a piece of work waits before someone can start it.

The last two matter most and are almost never tracked.

Putting slack back

Stop something. The only reliable route, and the one that requires a decision at a level above the team.

Reduce scope rather than quality. Doing fewer things properly is sustainable; doing everything badly is not, and it is what happens by default.

Add capacity, where the case can be made — and the case is made with the turnover cost, not with a wellbeing argument.

Attack the source. A recurring interruption, a manual process, a system that generates rework. Fixing one of these is worth more than any amount of prioritisation advice.

Protect a proportion of time as unallocated. Teams that plan to a fraction below capacity absorb variation; teams planned to full capacity escalate.

The conversation to have

Frequently the honest answer is that the work exceeds the team and always will unless something changes.

Present the arithmetic. Volume, capacity, the gap, and what has been absorbed to date.

Offer the options rather than the complaint: reduce scope, add capacity, extend timelines, or accept the current quality and attrition. All four are legitimate decisions and someone should make one explicitly.

Record the decision. A choice made knowingly is manageable. A choice made by default, repeatedly, is how teams end up here.

What not to do

Prioritisation training for a team whose problem is volume rather than sequencing.

Time management advice.

Asking people to work smarter, which they have already tried.

Celebrating the heroics. Public praise for the person who worked the weekend sets the expectation and tells everyone else what is required.

Distinguishing volume from friction

Not all overload is volume, and the remedies differ entirely.

Volume: genuinely more work than hours. Requires scope reduction or capacity.

Friction: the work is achievable and the path to doing it is obstructed — waiting on approvals, chasing dependencies, rework caused by unclear requirements, tools that fail.

Fragmentation: enough total hours, none of them contiguous.

Ambiguity: effort spent working out what is wanted rather than doing it.

Ask the team to categorise a week's frustrations into these four. The distribution is frequently surprising, and friction and ambiguity are usually a larger share than anyone expects.

Friction is cheaper to fix than volume and produces faster relief, which makes it a good first move even where volume is also a genuine problem.

The temporary that is not

A phrase worth tracking, because it marks the transition from a hard period to a design.

"It is just until the new person starts."

"Once this project lands."

"After the busy season."

Note when each was first said. Where the same sentence has been repeated for more than two quarters, the situation is not temporary and calling it temporary is preventing anyone from addressing it.

Naming that in a meeting is uncomfortable and effective. It converts an assumption into a decision someone has to make.