Why Headcount Is the Default Answer

There’s nothing irrational about reaching for headcount first.  It’s the lever every owner understands intuitively, more work, more hands, more output.  It’s also the lever that’s easiest to justify to a board, a bank, or a partner, a hiring plan is a concrete, countable thing that visibly signals the business is taking growth seriously.

Process redesign and role restructuring don’t offer the same visibility.  Nobody can point to a redesigned approval workflow in a board pack the way they can point to three new starters.  That asymmetry, one option is easy to show, the other is easy to skip, is exactly why headcount gets reached for first even when it isn’t the thing that’s actually broken.

There’s a second reason worth naming, one that has less to do with visibility and more to do with comfort.  Hiring feels like decisive action, the kind of clear, forward-moving decision that feels good to make.  Sitting down to map out exactly where a process breaks down, and having the sometimes uncomfortable conversation about why a particular senior person has become the bottleneck, is slower and often more personally awkward.  It can feel like criticism, even when it’s framed carefully, because it inevitably points at how things have been run, not just at an abstract gap in the org chart.  Hiring sidesteps that discomfort entirely.  It adds something new rather than examining something that already exists, which is precisely why it’s so often preferred, even when it isn’t the more effective choice.

Hiring treats the symptom, not always the cause

A business that’s genuinely under-resourced does need more people, that’s real and it happens.  But a lot of what looks like an under-resourcing problem is actually a bottleneck problem, work queuing behind a single approval step, decisions that all have to route through one person, a process built for half the current volume and never revisited.  Adding headcount to a business with those bottlenecks still intact doesn’t remove the bottleneck.  It just adds more people waiting behind it.

This is the same idea covered from the structural side in you’ve set the budget, do you have the structure to deliver it, capacity lives in process and decision rights as much as it lives in people.  This piece picks up where that one left off, once you know the structure needs work, what does that actually mean for the hiring decision sitting in front of you right now.

It’s worth being precise about the distinction between the two kinds of problem, because they look similar from the outside but call for very different responses.  Genuine under-resourcing looks like this, the team is working at a sustainable pace, decisions move at a reasonable speed, and the constraint is simply that there aren’t enough hours in the day to handle the current volume of well-functioning work.  A bottleneck problem looks different, work is queuing not because there’s too much of it in absolute terms, but because it’s all funnelling through one narrow point, a single approver, a single system, a single person’s calendar, regardless of how much total capacity the rest of the team has.  The first genuinely needs more people.  The second needs the funnel widened, and more people poured into a narrow funnel just queue for longer, together.

How This Plays Out in Practice

Picture a business that approved a 25% revenue target for the new year and, in the same budget cycle, signed off on three new hires to help deliver it, two in operations, one in customer service.  On paper, headcount scaled roughly in line with the growth target.  It looked like sound planning.

Six months in, the picture was less encouraging.  The new operations hires had been absorbed into the same scheduling bottleneck the existing team had always fought, because nothing about how work got prioritised or approved had changed, there were just more people now waiting on the same one senior person to make the calls that kept things moving.  The new customer service hire spent much of their first months being trained informally by already-stretched senior staff, since no documented onboarding process existed, which meant the hire that was meant to relieve pressure temporarily added to it instead.

The net capacity gain was smaller than the headcount growth

Three new salaries, full onboarding costs, management time diverted to training and supervision, and at the end of it, the business’s actual output capacity had grown by meaningfully less than the 25% the hiring plan implied it would.  The bottleneck that had always constrained throughput was still there, just now with more people queued behind it and a bigger wage bill attached to the queue.

It’s worth being specific about where that gap actually showed up.  The two new operations hires spent a noticeable share of their week waiting for sign-off on decisions that only one person in the business was authorised to make, exactly the same wait the existing team had always experienced, just now spread across more people.  Management time that should have gone toward the next quarter’s planning instead went into supervising and unblocking three new starters who, through no fault of their own, had joined a structure that was never going to let their extra hours convert cleanly into extra output.

None of the three hires were bad decisions in isolation, each was a capable person doing reasonable work.  The decision that was wrong was assuming headcount alone would convert into capacity, without first checking whether the structure around those people could actually put their extra hours to productive use.

There’s a detail worth adding that surfaced only once the business stepped back and looked properly, one of the two new operations hires had, entirely on their own initiative, started keeping a private note of every time they’d been blocked waiting on approval.  Over four months, the tally ran to well over a hundred instances, the vast majority for decisions that, on review, could easily have been made by the operations lead without ever reaching the senior approver’s desk.  That informal tally ended up being one of the more useful pieces of evidence in diagnosing what had actually gone wrong, a reminder that the people closest to the bottleneck often know exactly where it sits long before it shows up in any formal review.

The Compounding Cost of Hiring Ahead of Structure

This isn’t a one-off mistake that costs a fixed amount and then goes away.  It compounds, and it compounds faster than most owners expect.

More people in a structure that wasn’t fixed first means more coordination overhead, every additional person is another set of handoffs, another person needing context, another voice in decisions that were already routing too slowly.  It means more onboarding drag, because if documentation and process were thin before, they’re now being stretched across more people who all need the same missing information.  And it means the same one or two senior people who were already the bottleneck are now managing more direct reports on top of still being the bottleneck, which pulls their attention further from the judgement calls only they can make.

The cost curve doesn’t stay flat

Hiring one person into a broken structure is inefficient.  Hiring three compounds that inefficiency, because now there are three times as many people whose output is constrained by the same unfixed bottleneck, and three times as much coordination and onboarding load sitting on top of it.  The businesses that keep hiring their way through growth without ever fixing the underlying structure tend to find their cost per unit of actual output rising, not falling, even as headcount climbs, which is precisely the opposite of what scale is supposed to deliver.

This shows up most clearly at the next budget cycle.  A business that hired ahead of structure last year often walks into this year’s planning with a bigger wage bill, a similar bottleneck, and a renewed instinct to hire again to close the gap, because hiring is still the visible, easy-to-justify lever it always was.  Without someone stepping back to name the actual constraint, that cycle repeats, and each pass through it gets more expensive than the last.

This is why the timing of the question matters so much.  Asked before the hiring plan is approved, it’s a genuinely useful check that can change the whole shape of the plan.  Asked a year later, once three hires are already on the books and the bottleneck is still there, it’s a much more expensive and disruptive problem to unwind.

Unwinding it later is genuinely harder than most owners expect, and it’s worth naming why.  Reversing a hiring decision, even a clearly mistaken one, carries real human and reputational cost that simply redesigning a process upfront never would have.  Nobody wants to have the conversation about restructuring a role six months after someone joined expecting it to be permanent.  So businesses that hire ahead of structure often don’t unwind the mistake at all, they simply carry the extra cost indefinitely, layering the next round of hiring on top of the same unresolved bottleneck the following year, and the year after that.  The compounding cost isn’t hypothetical, it’s the default trajectory unless something specifically interrupts it.

It’s worth adding one more observation from the scenario above, because it changes how the fix is usually approached once the pattern is recognised.  Once the business finally did map out where decisions were actually getting stuck, the fix wasn’t a fourth hire, or a fifth.  It was a genuinely small change, moving three specific categories of decision that had always defaulted to the senior approver down to the operations lead, with clear written boundaries around what fell inside and outside that authority.  Within weeks, the same three hires who’d felt underused for months were operating at close to the capacity the original plan had assumed all along.  The people were never the problem.  The routing was.