Questions we answer Hiring and headcount

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.

Start from this question

Free · a few minutes · starts from “I think we need another person”

The short answer

The signals worth trusting are durability and consequence: the pressure has lasted months rather than weeks, it is growing, work is being turned down or delayed because there is nobody to give it to, and you can describe what a new person would own. The signals worth distrusting are busyness, long hours and a full calendar — those are equally consistent with a process problem, a delegation problem or a peak that will pass.

Every team feels busy. Busy is weak evidence, because work expands to fill the week and people are poor judges of their own load. What tells you more is whether commitments are being missed, whether work that used to get done has quietly stopped, and whether the team can still take anything new on.

The second half of the question is durability. A gap that has lasted a quarter and is still widening is a different thing from one that appeared last month with a launch. Headcount is a permanent answer, so it wants a problem that is going to still be there.

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 being missed, and the pattern is capacity rather than one person or one step.
Work that used to happen — maintenance, follow-ups, improvement — has quietly stopped.
Nothing new can be taken on without something else slipping, and you can name what slips.
The load has been rising for months and the direction has not changed.

Signs it's something else

People are busy, but the outcomes are being met and nothing is being dropped.
The load spikes and falls with something you can point at, and the coming months look lighter.
A good part of the week goes on rework, chasing and copying between systems.
One person is overloaded while others have room, which is a distribution problem.

What's usually behind it

A rise in volume that crept up gradually enough that nobody noticed the shape had stopped fitting.
Work that has been silently dropped, which looks like coping until somebody asks for it.
Overtime that has become normal, which hides the gap rather than closing it.
A missing skill being covered by whoever is nearest, at the cost of their own work.

What people usually get wrong

Using how busy people say they are as the measure, when everybody is busy and nobody is idle.
Waiting for somebody to resign before treating the load as real.
Adding a person to a team whose work is undefined, and expecting them to define it.
Counting hours rather than what is not getting done, which measures effort instead of capacity.

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.

Recruit
The gap is durable, growing and central, and somebody is ready to own the new person's work.
Redistribute
The load is uneven and there is room elsewhere in the team.
Reduce the work
Some of what the team does no longer earns its place, and nobody has been given permission to stop.
Outside help for a stretch
The load is real but you cannot yet say whether it is permanent.
Automate the repetitive part
A recognisable share of the week is the same steps in the same order.

When doing nothing is the right call

If the load is real but new, the honest answer may be to watch for one more cycle. Decide now what you would expect to see if it is permanent — the same slippage in the same places, with no seasonal explanation — and put the review date in the diary.

What the diagnostic asks

What a new person would mainly add: capacity, a missing skill, or both.
How long this has been the case and whether it is growing.
Who owns the work today, how repeatable it is and how much is written down.
Whether a permanent hire is fundable, and how soon this needs sorting.

“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.

Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Outsource
Hand a defined, ongoing scope of work to an external provider.
AI Agent
Delegate a defined, repeatable workflow to software inside boundaries you set, with human oversight.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.

What changes the answer

A gap that is visible in missed outcomes rather than in effort is much stronger evidence.
A load that rises and falls with something nameable points away from a permanent role.
Uneven load across the team points at distribution before headcount.

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.