"We need two more people": the headcount plan nobody wrote

A business approved nine hires over fourteen months, each one individually reasonable. Each came from a manager under genuine pressure, each was argued on the basis of current workload, and each was approved after a short conversation about budget.

At the end of it, somebody drew the organisation chart. There were now four people doing broadly similar coordination work in three different teams, none of them senior enough to make a decision, and a gap at the level above that everyone had been working around for a year. Nobody had decided this. It was the sum of nine sensible decisions taken one at a time.

What request-by-request hiring optimises for

Approving headcount on request rewards a specific thing: the ability of a manager to make a case at the moment of maximum pain. That correlates with how overloaded a team is this quarter. It does not correlate with where the business most needs capability next year.

It also has a predictable bias toward the junior end. A manager who is drowning asks for help with the volume of work, and help with volume is a junior hire. The role that would actually fix the problem — someone senior enough to take decisions off the manager's desk — costs more, takes longer to fill, and is harder to justify against this month's backlog. So it never gets requested, and the same manager is back in two quarters.

The four questions before any hire

1. 1

   What capability is missing, in plain words?

   Not "we need a person" but "nobody can close a month-end without the finance manager, and she is the only one who can". Written this way, a surprising share of requests turn out to describe a process problem or a single point of failure rather than a volume problem.

2. 2

   Does it have to be a hire?

   The alternatives are genuinely worth a few minutes each time: redistributing work, automating a step, a contractor for a finite piece, or promoting someone internally and backfilling lower. Each is faster than recruiting and two of them are cheaper.

3. 3

   At what level?

   The question that gets skipped. Hiring one person a level up frequently solves more than two a level down, and costs less in total. It is also harder to reverse, which is why it deserves the deliberate conversation rather than the reflexive one.

4. 4

   What happens if we do not, for two quarters?

   Sometimes the honest answer is that a project slips, which the business can accept. Sometimes it is that the best person in the team leaves, which it cannot. These deserve different priority and request-by-request approval treats them identically.

A twelve-month view is a different document

A workforce plan is not a hiring budget with dates. It is a statement of what the business will need to be able to do that it currently cannot, and where those capabilities will come from.

1  WHERE THE BUSINESS IS GOING
     Two or three sentences. A new site, a new segment,
     a service moving in-house. If this is not known,
     nothing below it can be.

2  CAPABILITY GAPS THAT FOLLOW
     What will be needed that does not exist today. Stated
     as capability, not as job titles.

3  HOW EACH GAP CLOSES
     Hire / develop internally / contract / automate /
     accept. Five options, one chosen, with a reason.

4  WHAT YOU WILL LOSE
     Expected exits, retirements, known flight risks, and
     internal moves that vacate a role.

5  SEQUENCE AND TRIGGERS
     Not just when, but what has to be true first. "Hire
     the second supervisor when the second line runs."

The fourth section is the one most plans omit and it changes the arithmetic considerably. A business planning six hires while three people are quietly planning to leave is planning nine, and the three replacements will arrive as emergencies with no time to consider level or structure.

The fifth section is what makes the plan survive a bad quarter. A plan of dates gets abandoned when revenue misses; a plan of triggers simply does not fire, which is the correct behaviour and does not require anyone to formally give up on it. Between them, those two sections are most of what distinguishes HR strategy and workforce planning from an annual budgeting round.

Build versus buy

For most gaps there is an internal candidate who is not ready yet and an external candidate who is. The reflex is to buy, because it is faster and the risk is visible on only one side.

The cost of always buying compounds. People who watch every senior role fill externally stop believing there is a path, which shows up two years later as attrition among exactly the people who would have been ready by then. And each external senior hire carries a real failure rate that internal promotion does not, because the internal candidate's ability to operate in this specific business is already known.

The practical version is to decide the ratio deliberately rather than case by case — a business that intends to fill, say, half its senior roles internally has to start developing people eighteen months before the roles exist, which is what makes succession and leadership development a planning activity rather than a reaction to a resignation.

The conversation that produces the plan

It is not an HR exercise done to managers. It is two hours with the people who run the business, and it works best with a specific structure.

• Start with the business, not the headcount. What are we trying to do next year that we are not doing now. Headcount discussed before this becomes a negotiation over budget.
• Each manager names their single point of failure. The person whose resignation would cause the most damage. This is usually more urgent than anything on the hiring list, and it is rarely on it.
• Put every request on one page together. Overlap becomes obvious immediately. Three teams asking for similar coordination support is one restructure, not three hires.
• Decide what you are not doing. A plan that approves everything is a budget, not a plan, and it provides no guidance when the quarter goes badly.

Most businesses find the first run of this uncomfortable, because it surfaces disagreements about direction that had been comfortably unspecified. That discomfort is the value. The disagreements existed already and were being resolved implicitly, through whichever manager happened to make the strongest case in a given month.

When to start

The threshold is lower than people assume. Somewhere around forty or fifty people, request-by-request hiring stops being adequate, because the founder can no longer hold the whole shape of the organisation in their head and notice the overlap.

It does not need to be sophisticated. One page, reviewed quarterly, with the five sections above. The value is almost entirely in having the conversation rather than in the artefact, which is why an elaborate model built by one person and circulated tends to change nothing.

Where the shape of the organisation is itself the problem — overlapping roles, decisions with no clear owner, a missing layer — the plan will not fix it, and hiring into it makes it more expensive to correct later. That is organisation design work and it is worth doing before the next nine hires rather than after, which is the sequencing question most HR strategy and workforce planning engagements end up resolving first.