Questions we answerCapacity and workload
My team is overloaded. What should I do?
Start by finding out whether the overload is volume, design or ownership. Each has a different fix, and only one of them is more people.
Free · a few minutes · starts from “We're overloaded”
The short answer
Overload is real, but it is not always a headcount problem. It points at a hire when the extra work is durable, spread across the team and genuinely needs more hands. It points elsewhere when the load sits on one or two people, when a large share of it is administration around the work rather than the work, or when there is a date after which it eases. The useful first step is establishing which of those you have, because each one has a different and much cheaper answer.
Overload feels like one problem. It is usually two or three: work that arrives badly, work that nobody owns, and genuinely more work than hands.
The diagnostic separates them, because the answer to each is different and the cheapest ones are worth trying first.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Commitments are slipping across the team rather than in one place.
- Overtime has become how the work finishes rather than an exception.
- Nothing new can be taken on without something else being quietly dropped.
Signs it's something else
- One person is drowning while others have room.
- The load rises and falls with something you can name, and the next few months look lighter.
- The hours are full, but the outcomes are being met and nothing is being dropped.
What's usually behind it
- A process that has grown by habit and now contains steps nobody needs.
- Repetitive work sitting with skilled people.
- A sustained rise in volume that the team's shape was never designed for.
What people usually get wrong
- Treating overload as one problem with one fix.
- Asking people to prioritise without telling them what they are allowed to drop.
- Adding capacity to a flow nobody has looked at, so the new hours are absorbed by the same waste.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Take work out
Some of what the team does no longer earns its place and nobody has been given permission to stop.
Change how the work flows
The same work arrives by different routes and gets handled more than once.
Move ownership
The load is uneven and someone else in the team has room to take it.
Add capacity
The work is well shaped, clearly owned, and still does not fit in the hours available.
When doing nothing is the right call
If the peak has a visible end — a launch, a season, one large customer — then holding the line, saying so out loud and protecting people's hours afterwards is a legitimate answer. It stops being legitimate the moment nobody can say when the peak ends.
What the diagnostic asks
- Which symptom is closest: too much work, a missing skill, unclear ownership, one-person dependency or repetitive work.
- How long it has been like this and where it is heading.
- How repeatable and how well documented the work is.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
AI Agent
Delegate a defined, repeatable workflow to software inside boundaries you set, with human oversight.
Outsource
Hand a defined, ongoing scope of work to an external provider.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
What changes the answer
- Repeatable, undocumented work points at process change before anything else.
- A definable outcome that could sit outside the team opens up outsourcing.
- A durable, growing, core need with nobody close internally points at a hire.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- How do I know if my team needs more headcount?Look for a gap that is durable, growing and visible in outcomes rather than in how busy people feel. Missed commitments, work that has quietly stopped and an inability to absorb anything new are better evidence than hours.
- Repetitive admin is eating the weekWork out how much of it should exist at all before automating any of it. Some repetitive admin is a process nobody has simplified, some is a good candidate for software, and a little of it genuinely needs a person.
- Should I fix the process before hiring?Usually yes, at least far enough to know what the new person would own. It is cheap and quick, and it either removes the need or tells you exactly what to recruit for. It stops being sensible once it becomes a reason never to decide.
- Too much depends on one person. What are my options?Reduce the fragility before it becomes a crisis: write the work down, develop a second person, move adjacent work off them, or decide it is acceptable for now with a date to look again.
- How do I reduce workload without hiring?Three levers in order: stop doing some of it, change how the rest flows, and automate what is genuinely repeatable. Most teams reach for the third and skip the first two.
- My best people are doing low-value workExpensive people doing cheap work is a real and quantifiable loss. The fix is usually to move or remove the work, not to hire someone junior to absorb it.