The Conversation About Too Much Work

Someone has taken a risk in telling you. What happens next determines whether anyone tells you anything again.

The responses that cause harm

"We are all busy." True and it ends the conversation permanently.

Immediate problem-solving before understanding, which frequently produces advice the person has already tried.

Time management suggestions, which locate the problem in their competence.

"Let me know if it gets worse," which places the burden of a second disclosure on them.

Visible panic, which makes them responsible for managing your reaction.

Nothing. Listening, agreeing it is difficult, and then not following up, which is the most common failure.

The response that helps

Listen first and fully. Do not solve while they are still describing.

Get specific. What is taking the time, what is the volume, what has been dropped, how long has this been the case.

Distinguish volume from other causes. Overload frequently turns out to be unclear priorities, an unresolved dependency, or one broken process — all more fixable than headcount.

Name what you can and cannot do, immediately and honestly.

Do one thing quickly, even a small one, because the first visible action determines whether they believe the rest.

Set a specific follow-up date and keep it.

What is usually available

More than managers expect.

Reprioritise. Explicitly decide what does not get done, and communicate that decision upward so the person is not left defending it.

Remove something, properly, not by deferring it.

Change a deadline.

Redistribute within the team, carefully, so it does not simply move the problem.

Fix a dependency that is generating waiting and rework.

Reduce their meeting load, which is frequently the fastest available relief.

Give explicit permission to do something to a lower standard, which people will not do without being told.

When you cannot reduce it

Sometimes the honest answer is that the load is what it is for now.

Say so plainly, with the reason.

Say how long. An endpoint makes a hard period survivable; an open-ended one does not.

Say what happens after, and then deliver it.

Escalate it anyway, and tell the person you have. Even where it changes nothing immediately, they need to know the problem is not being absorbed silently.

Reduce something else you control, even if small.

Do not promise a change you cannot deliver. A broken commitment here is worse than an honest refusal.

Escalating upward

With arithmetic, not adjectives. Demonstrated throughput against committed volume.

With the options, so the decision is a choice between named alternatives rather than a complaint.

With the consequence stated: what will not get done, or what the attrition risk is.

In writing, so the decision is recorded and does not have to be relitigated in three months.

The follow-up

The single most important part, and the one most often dropped.

Come back to it in two weeks. Ask specifically whether the change helped. Adjust.

A manager who follows up once establishes that raising a problem produces attention. That reputation is what causes the next problem to surface early rather than at the resignation.

The follow-up two weeks later

The part most often dropped and the part that determines whether anyone raises anything again.

Diarise it at the time, in the conversation, so the person sees it happen.

Ask specifically whether the change helped, not whether things are better generally.

Ask what else has emerged, since relieving one pressure frequently reveals another.

Report what you escalated and what came back, including where the answer was no.

Adjust, rather than treating the first intervention as complete.

A manager who follows up once establishes a reputation that causes the next problem to surface early. A manager who does not has taught their team that disclosure produces sympathy and nothing else.

Escalating in writing

A verbal escalation that produces no change has to be relitigated. A written one does not.

State the arithmetic: demonstrated throughput against committed volume.

State what will not be delivered if nothing changes.

State the options and ask for a decision between them.

State the consequence you are managing: overtime, quality, or attrition risk.

Send it, briefly, and keep it.

This is not a defensive act. It is how a repeated decision becomes an explicit one, and explicit decisions get revisited where implicit ones persist for years.