Why My Team and I Check Span of Control Before Recommending Any New Hire

A team that feels overwhelmed usually asks for more hands, and that request often gets approved without checking a simpler, more diagnostic question first: does the manager this new person would report to actually have the attention available to manage one more person well. If the answer is no, adding headcount there doesn't relieve the pressure the team is feeling — it adds another person competing for the same already-insufficient management attention, which can leave the team no better off, and sometimes worse off, than before the hire was approved.

This check matters because a hiring decision is almost always evaluated against workload alone, and workload is only half of what determines whether a new hire actually succeeds — the other half is whether anyone has the bandwidth to properly onboard, direct, and develop that person once they arrive.

Why this question gets skipped

A hiring request is framed around workload — there's too much work, so more hands are needed. Framed that way, the request sounds complete on its own, without anyone checking whether the receiving manager has capacity to actually manage the addition well.

Hiring requests are almost always framed in terms of workload — too much to do, not enough people doing it. That framing is self-contained enough that it rarely prompts anyone to ask a separate question: whether the manager who would oversee this new hire already has more direct reports than they can genuinely support. Workload and management capacity are different constraints, and only one of them usually gets checked before a hire is approved, which means a hiring decision can look fully justified on paper while still being set up to underperform in practice.

What happens when span of control gets ignored

A new hire added under an already-overstretched manager gets less onboarding, less feedback, and less actual direction than the role needs — which can make the team's overall output worse, not better, despite the extra person.

A manager already spread too thin across existing direct reports doesn't suddenly gain bandwidth because a new hire joined — if anything, onboarding that hire properly requires bandwidth the manager didn't have to begin with. The new person often ends up under-supported, under-directed, and contributing less than their role should, which means the hire can make the team's actual output worse in the near term, despite solving the headcount number on paper, because the new person's ramp-up period drags on far longer than it would have under a manager with genuine capacity to invest in them.

A concrete picture of how this plays out

A manager already overseeing nine direct reports gets a tenth added to relieve team-wide pressure. Six months later, the new hire is still underperforming, not because of ability, but because they've received a fraction of the onboarding attention a less-stretched manager would have provided.

Picture a manager already overseeing nine direct reports, asked to take on a tenth to help relieve pressure the team has been feeling. Six months later, the new hire is still underperforming relative to what their skills would predict — not because of any deficiency in their ability, but because they've received a fraction of the structured onboarding, feedback, and direction a manager with real bandwidth would have provided. The team's pressure hasn't actually eased; it's simply been redistributed to include managing the gaps left by an under-supported new hire, on top of everything the team was already struggling with before.

What checking this first actually reveals

Sometimes the team doesn't need another person — it needs the existing manager relieved of something else, or a second manager added before the team itself grows further.

Checking span of control before approving a hire sometimes reveals that the real bottleneck isn't headcount at all — it's that the existing manager is already managing too many people, or carrying responsibilities beyond management that are crowding out the attention their team needs. In that case, the right fix might be removing something from the manager's plate, or adding management capacity itself, rather than adding another person for an already-stretched manager to oversee, which is a fundamentally different and often cheaper intervention than the hire that was originally requested.

Why this check sometimes reveals an uncomfortable truth about the manager's own workload

Running this diagnostic can surface that the manager themselves is doing work that was never really management work in the first place — which raises a harder conversation than simply approving or denying a hire.

In some cases, checking span of control surfaces that a meaningful share of the manager's own time is going toward tasks that aren't genuinely management responsibilities at all — work that got absorbed into their role informally over time, the same way any role can drift under the weight of accumulated small additions. Addressing that drift is a harder, more involved conversation than simply approving or denying a headcount request, but it's often the conversation that actually needed to happen before any hiring decision could be made well.

Why this check is worth doing before every hiring decision, not just the obvious ones

Span of control tends to degrade gradually as a team grows, which means this check matters most exactly when nobody's thinking to run it — during ordinary, routine growth, not an obvious crisis.

Span-of-control problems rarely announce themselves clearly — they build up gradually as a team adds people, each addition individually reasonable, until a manager who was fine with five direct reports is quietly struggling with eleven. Making this check a routine part of every hiring decision, rather than something reserved for obviously troubled teams, catches the problem while it's still cheap and easy to fix, long before it's had the chance to compound into the kind of entrenched, team-wide strain that's far harder to untangle later.