Workload: spotting overload before it becomes a delay

The delay nobody saw coming

When a project slips, the post-mortem often follows the same script. A key person had too much on their plate, some tasks sat idle for days, and all the signs were there. It is just that nobody was looking at them as a whole.

Overload is hard to see from the inside. People who are swamped tend not to say so, out of pride or because they hope to catch up on the weekend, and whoever assigns tasks sees only the share they assigned. The full picture, the one that adds up everyone’s requests, is often held by nobody.

Overload shows up late because everyone looks only at their own part.

Counting tasks is not enough

The most immediate way to measure workload is to count the open tasks per person. It is a start, but it can be misleading: ten short tasks weigh less than two complex ones, and a long list may hide a sustainable load while a short one may hide an impossible week.

For a more reliable picture, attach an effort estimate to every task, even a rough one. There is no need for quarter-hour precision: it is enough to distinguish between what takes an hour, a day or several days. Added up over the week, these estimates quickly show who has room and who is already over the limit.

Time that appears on no list must be counted too, such as meetings, helping colleagues and the unexpected. Someone whose calendar is packed with meetings has fewer hours available than their task list suggests.

Reading the signals

Beyond the amount of work, some signals give early warning of a problem. The most obvious is a rise in overdue tasks: one or two are normal, but a number that grows week after week means someone can no longer keep up.

Other signals are less visible but just as useful: tasks that stay in the same status for a long time, deadlines moved several times, approval requests piling up in a single person’s inbox. Taken one by one they look like incidents; seen together they tell the story of an overload.

It pays to watch these signals regularly, for instance in a short weekly check-in, rather than waiting for the end of the month. A signal caught early calls for small adjustments; one caught late means reworking the whole plan.

Rebalance without removing ownership

Once overload has been spotted, the temptation is to move tasks from one person to another by decree. A short conversation with those involved works better: whoever is overloaded knows which tasks they can hand over without losing the thread and which still need their input.

There are three levers: reassign a task to someone with capacity, move its deadline in agreement with whoever requested it, or drop it if it is no longer essential. In every case the change should be recorded, so that whoever is waiting for the result knows whom to ask and when to expect it.

Rebalancing is not a judgment on the person. A team in which flagging overload is normal is a team in which problems surface early, while they are still easy to fix.

1. 01 Read the workloads
2. 02 Find tasks to hand over
3. 03 Talk to those involved
4. 04 Reassign or postpone
5. 05 Share the new dates

A shared view of workloads

For all this to work you need a view that shows everyone’s workload in one place, kept up to date without anyone filling it in by hand. A spreadsheet refreshed once a month always arrives after the problem.

In Task the progress dashboard shows, for every person and every team, open tasks, estimated effort and overdue tasks, with filters by project or department. Absences recorded in People are taken into account automatically, so a week of leave does not look like a week of availability. Team leads see where to step in, and anyone can reassign or postpone a task in a few clicks, leaving a record of the decision.

The result is not one more control but a better conversation: people discuss data everyone sees the same way, and workload decisions are made before they turn into delays.