When a team is buried, the reflex is to open a requisition. Sometimes that is correct. Often it is not, and the hire ends up absorbing a problem that was never about headcount.
We have filled roles for employers since 1997, and the pattern is familiar. A new person arrives, learns the workarounds, and settles into the same friction as everyone else. Six months later the team is still stretched and the hire is blamed for not making a difference.
Here is a practical way to test the need before you commit to it.
Separate volume from friction
A team can be short on hands, or it can be spending its hands on work that should not exist. The two look identical from the outside.
Ask where the hours actually go. Look for:
- Reports built by hand from several systems
- Data keyed twice because two systems do not talk
- Approvals that wait on one person's inbox
- Handoffs where nobody is sure who owns the next step
- Processes nobody has reviewed in years
If one person spends a day a week assembling a report, that is roughly 20% of a full-time role going to a task a script or a better system setup might handle. A controller will recognize this in month-end close. A plant manager will see it in paper-based production reporting. A sales leader will see it in CRM entry that reps do on Friday afternoon from memory.
The team usually knows where these are. What it lacks is the time to stop and fix them. That is a management decision, not a staffing one.
Count your single points of failure
Every company has the person everyone calls when something breaks. The 25-year veteran who knows why the line runs that way, or why a customer's invoices are coded differently.
That person is an asset. They are also a risk, and a leader who says "we would be in trouble if she left" has already described the problem.
Adding people around a key individual does not fix it. The knowledge stays in one head, and new hires either queue up behind that person or guess. Three questions help:
- Which 3 to 5 people would hurt most if they gave notice tomorrow?
- What do they know that is written down nowhere?
- Who could cover their work for two weeks today?
If the answer to the third is nobody, your next hire may be better spent on documentation and cross-training than on more capacity. In skilled trades and manufacturing, where a retiring tradesperson takes decades of know-how out the door, this is a workforce plan issue, not a side project.
Look at the work from close up and from a distance
People inside a process stop seeing it. They adapt. A fresh set of eyes, whether from a manager in another department, a newer employee or a contractor, will ask why a step exists. Many of the answers turn out to be "it always has."
It helps to pair someone who knows the work with someone who does not. The first knows what is real. The second asks what is necessary.
Clear ownership matters just as much. When it is plain who decides, who approves and who is told, teams move faster with the people they already have. When it is not, they rely on a few capable individuals to hold things together, and growth breaks that arrangement quickly.
Where AI and automation fit
Automation is part of this conversation, but it works best after the process is understood. Automating a messy workflow gives you a faster mess. Start by mapping the steps, removing the ones that add nothing, then decide what a tool should do and what a person should.
This also changes what you hire for. Instead of another person to do the manual work, you may need someone who can own the process, build the reporting, or manage the tools. That is often a contract role first, to get the fix in place, with a permanent hire to maintain it.
When the answer is still more people
Sometimes it is. If the process is sound, ownership is clear, knowledge is shared and the team is still at capacity, hire. Do it with confidence, because you will have a clear job description built around real work rather than a gap you could not explain.
A food manufacturer in the GTA we worked with made over 20 hires in 18 months across production, skilled trades and office roles. Growth was real, and those hires were needed. The ones that held up best were in roles where the work and the reporting lines were defined before the search began.
What to do next
Before your next requisition, spend an hour with the team lead and list the five tasks that eat the most time and the three people you cannot afford to lose. Decide which problems a hire solves and which need a process fix first. Then write the role around what is left.
If you want a second opinion on whether a role should be permanent, contract or a different job altogether, a Traverse recruiter can help you think it through.