Guide
Why hiring more people didn't fix it
Hiring is the most available remedy, so it gets used for problems it cannot solve. When the constraint is not capacity, more people add coordination, onboarding and rework to a system that was already struggling — and the number you were watching gets worse before it gets better.
A pattern worth recognising
A support team doubles its headcount to bring resolution time down from two days. Three months later the median sits at 51 hours and repeat contacts are rising. Nothing was mismanaged. The constraint was never the number of hands: agents never found out which of their fixes actually stopped the customer coming back, so the same faults were re-solved every week. Twice as many people solved the same faults twice as often.
Three tests before you hire
- Are your best people fully loaded on the work that matters? If they spend a third of their week on work nobody would miss, you have capacity you haven't claimed yet.
- Does the same work come back? Rework, repeat tickets and re-opened tasks mean the loop is broken. Adding people multiplies rework.
- Did the last hire make the number move? If a previous addition changed nothing, the next one will behave the same way. That is evidence, not pessimism.
When hiring genuinely is the answer
When the work is well understood, the loop is closed, quality is stable and queues grow purely with volume, capacity is your constraint and hiring works. The point isn't to avoid hiring — it's to hire into a system that can absorb it.
Find out which case you're in
The free diagnostic scores capability, tools, coordination, follow-through and feedback separately, so capacity claims get tested rather than assumed.