Most headcount strategies aren't wrong on purpose, they're wrong because they were written for a world where more output reliably required more people, and nobody's gone back to check whether that assumption still holds. It usually doesn't, not fully, and the five signs below aren't vague cultural observations, they're specific and checkable against your own hiring plan, org chart and last two quarters of output. If two or more of these describe your company, the plan isn't just aging, it's actively costing you against competitors who've already replanned around leverage instead of headcount.
Sign one: headcount is planned as a ratio, not an ownership gap
If your hiring plan says something like 'one support hire per X customers' or 'one engineer per $Y of ARR,' check when that ratio was set and whether anyone has revisited it since AI tooling changed what one person in that function can handle. Ratio-based headcount planning was a reasonable proxy when the underlying per-person capacity was roughly stable across a company's growth. It stops being reasonable the moment tooling changes that capacity, and most companies are still running ratios calibrated a year or more ago, silently overhiring against a bar that's moved.
Sign two: nobody can name the specific ownership gap a new hire fills
Ask, honestly, of your next three planned hires: what will this person own that a tool, or an existing person equipped with a better tool, genuinely cannot? If the honest answer is 'more capacity for the same work the team already does,' that's a tooling question in disguise, not a hiring need. A healthy headcount plan can answer this question specifically and concretely for every open role; a plan that answers it with 'we're growing, we need more people' hasn't actually diagnosed the gap, it's assumed one exists because growth is happening.
- For each planned hire, write down the specific outcome they'll own that isn't currently owned by anyone or any tool.
- If the answer is 'help with' or 'support' an existing owner, that's a scope or tooling problem, not a new-seat problem.
- If you can't answer this in one sentence per role, the plan was built on a ratio or a feeling, not a diagnosed gap.
Sign three: recent hires added coordination cost faster than output
Look honestly at your last three to five hires: did the team's shipping pace visibly increase, or did the number of syncs, review steps, and cross-functional check-ins increase more noticeably than actual output did? Coordination cost rises faster than headcount as a team grows, which means a company that's still hiring by ratio is often adding coordination overhead faster than it's adding shippable output, a trade that looks like growth on the org chart and feels like slowdown in practice. If your team's velocity per person has quietly declined over the last two hiring rounds, this sign already applies to you.
Sign four: headcount growth is still a board-update success metric
Check your last few board updates or leadership all-hands: is 'we grew the team to X people' presented as a win in itself, separate from output or revenue per person? Headcount used to be a reasonable proxy for organizational seriousness and momentum. Investors and boards increasingly read a rising headcount number the opposite way, as a cost and a risk signal, unless it's paired with output or leverage metrics that justify it. If your reporting still leads with headcount growth rather than output-per-person or leverage metrics, the strategy behind it is very likely still growth-first, not leverage-first.
| Old metric | What it hides | Better metric to pair it with |
|---|---|---|
| Total headcount | Whether output grew proportionally, or lagged | Revenue or output per employee, quarter over quarter |
| Hires this quarter | Whether each hire filled a diagnosed ownership gap | % of hires tied to a named, specific outcome gap |
| Team size by function | Whether coordination cost grew faster than shipped output | Cycle time or ship rate per team, before and after |
Sign five: leaner competitors match or beat your pace, and you've explained it away
If a competitor with visibly fewer people is shipping at your pace or faster, and your internal explanation is 'they're cutting corners' or 'it won't last,' that's worth testing rather than assuming. Sometimes that explanation is right. Often, on closer look, it's a leverage-first competitor who's already restructured around outcome ownership and AI tooling, and the pace difference is real and durable, not a shortcut that will catch up with them. Treating a leaner competitor's speed as an anomaly instead of a signal is exactly how a headcount strategy stays outdated past the point it should have been revisited.
What a leverage-first plan replaces each sign with
- 1Replace ratio-based headcount targets with a per-role ownership diagnosis, reviewed at least twice a year, not set once and left alone.
- 2Require a one-sentence answer to 'what will this hire own that a tool or existing person can't' before any req gets approved.
- 3Track coordination cost (syncs, review layers, handoffs) alongside headcount, and treat a rising ratio of the former as a warning, not a normal cost of growth.
- 4Report output or leverage per person in board updates alongside, not instead of, headcount, and flag when headcount grows faster than output does.
- 5When a leaner competitor matches your pace, investigate their actual structure before assuming it's unsustainable, then borrow what's real.
