Headcount planning that survives contact with reality
Most annual plans are dead by March. Build one that bends instead.
Every autumn the same ritual happens. Finance asks for next year numbers, each function pads their ask, someone cuts twenty percent across the board, and the resulting spreadsheet is treated as truth until the first reforecast.
The problem is not the spreadsheet. It is that headcount is planned as a list of roles instead of a set of decisions with triggers attached.
Plan capacity, approve roles later
Split the plan into two layers. The first is capacity: how much salary the function can carry by quarter. The second is composition: which roles you actually open. Finance cares almost entirely about the first. Hiring managers argue almost entirely about the second, usually in September, about work that will not exist in June.
When you separate them, you can swap a mid level engineer for two support hires in April without reopening the planning process.
Attach a trigger to every role
A role with no trigger is a wish. A trigger is a measurable condition that says now. Support hires when ticket backlog passes a threshold for three consecutive weeks. Second sales pod when the first hits eighty percent of quota twice. Second recruiter when open reqs per recruiter passes twelve.
This does two useful things. It moves the argument from opinion to evidence, and it gives you a defensible reason to say not yet without being the department that blocks growth.
Sequence the ramp, not the start date
Managers plan for the day someone signs. The cost curve and the productivity curve both start later. A sales hire in a market with a six month ramp who starts in October contributes nothing to that year. Say that out loud during planning and half the late year asks move themselves to January.
Keep a small unallocated pool
Reserve roughly ten percent of the plan with no name attached. Something will break, someone will resign at the worst moment, an acquisition will land. A pool means responding to that does not require a board approval cycle.
Review monthly, replan quarterly
A short monthly check on triggers and actuals. A proper replan each quarter where roles can move, merge or die. Anything less frequent and the plan detaches from the business. Anything more and you spend the year planning instead of hiring.
The point is not accuracy. Nobody predicts a year correctly. The point is a plan that can absorb being wrong without a crisis meeting.