Why are teams always overloaded?
20 November 2026Governance, Team
In many organisations, teams are at—or have already exceeded—their limits. Overtime is piling up, deadlines are slipping, priorities are shifting, and everyone feels like they’re running in place without really making any progress.
We then look for explanations in terms of personal organisation, motivation, or tools. Sometimes with good reason. But often, the problem is simpler: no one has added up everything we ask of people.
A burden that goes unnoticed
Everyone spends part of their time on processes—that is, the routine tasks that keep the organisation running: handling requests, approving documents, preparing reports, responding to customers, participating in committees, and welcoming new employees.
This work rarely appears in any plan. Yet it comes up every week and often takes priority over everything else.
In practice, I often see the following situations:
- One person is given several processes without anyone checking to see if they have the time to handle them.
- A process takes significantly longer than expected due to exceptions, follow-ups, or successive validations.
Projects come in on top of that
Projects, on the other hand, are visible. We decide on them, plan them, and assign people to lead them. But each one is usually decided on its own, for its own reasons.
Taken one by one, they make sense. But when combined and added on top of the processes, they often exceed what people can actually handle.
This phenomenon is well known in queueing theory: the closer a system gets to its full capacity, the longer the wait times become—and this happens at a rate that is far more than proportional. A nearly full highway still moves. When it’s full, it comes to a standstill.
In other words, a team that’s 100% busy isn’t more efficient. It simply gets bogged down more often.
And what gives way first is what has no visible deadline: scoping, quality, improvement, and time for reflection. Then, eventually, the people themselves.
Make the load visible
The first step is straightforward. It involves laying out processes and projects side by side, person by person. A rough estimate is sufficient. The goal isn’t precision, but rather to get the big picture.
From there, several possibilities open up:
- Simplify or redistribute certain processes—that’s often where the missing time lies.
- Start with the time actually available for projects, once the processes are covered.
- Prioritise processes and projects as part of a single vision, rather than separately.
- Explicitly decide: reassign, continue, postpone, or stop.
Of course, this overview isn’t set in stone. The process should be repeated regularly.
A matter of direction
A project manager can optimise their project. They cannot decide that another project will have to wait, nor that a process will be streamlined. Those decisions are up to management.
When they aren’t made explicitly, they get made anyway, by default, as urgent matters arise. And rarely in favour of what matters most.
Saying no to a project isn’t really a sign of a lack of ambition. It’s about giving those we keep a real chance.
Manage your teams’ workload
We work with management teams to put processes and projects side by side and make informed decisions.