Most performance shortfalls are answered with a hiring plan. The compounders answer them with a capability plan, of which hiring is only one lever — and rarely the highest-leverage one.
When is hiring the wrong answer to a performance problem?
The reversal
Headcount is the most legible resource and the least reversible cost. The build-versus-buy-versus-borrow-versus-automate framing is decades old and consistently ignored under pressure. A structured capability plan typically shows that 30–50% of hires proposed to solve a performance issue would be better served by process redesign, tooling, contractor capacity, or an internal capability programme — at a fraction of the fixed-cost commitment.
The insight stack
What actually moves the P&L
Diagnose the capability gap before the headcount gap
A hiring requisition is downstream of a capability decision. Force the conversation upstream: what capability is missing, at what depth, for what duration? Only after that answer is stable does the build/buy/borrow/automate question become tractable.
Distinguish durable capability from surge capacity
Durable capability belongs on the payroll. Surge capacity — anything with a defined start and end, or anything cyclical — almost never does. Confusing the two produces two symmetrical failures: hiring for surge (over-fixed cost) and contracting for durable (under-institutionalised capability).
Automation reshapes the capability question, not just the cost question
Every capability decision made today should be re-framed against a 24-month automation curve. A workflow that will be 60% automatable within 18 months is not a hiring problem; it is a sequencing problem. This is where the AI Operations agenda intersects performance directly.
Case example
A £18M professional services firm
A professional services firm was preparing to hire eight analysts to keep up with rising delivery load. A capability review split the underlying work into three streams: 45% was durable client-facing analytical work (correctly identified as a hire); 30% was cyclical peak-season load (better served by a bench of vetted contractors); 25% was reporting and formatting that a structured tooling investment could automate within four months. The final plan hired three analysts, contracted four, and invested £120K in workflow automation. Twelve months later, delivery margin was up 620 bps and analyst turnover — historically driven by low-value work — fell to a third of the prior year.
Mini-playbook
Capability review, four questions
What capability is missing, at what depth, for what duration?
Is the underlying work durable, cyclical, or one-off?
What proportion of the work will be automatable within 24 months?
For the durable share only — build, buy, borrow, or partner?
Only after these are answered — write the requisition.
How Strategy Labs installs this
Anchored to Operating model design
CAE runs the capability review against the operating model and performance management artefacts, forcing the hire/contract/automate decision to be made against the operating plan rather than in a spreadsheet.
PDC captures the capability inventory and the automation roadmap, so successive hiring decisions accumulate into a coherent operating strategy rather than a headcount ratchet.
Frequently asked
Related questions executives ask
- What is a healthy ratio of permanent to flexible capacity?
- Depends on cyclicality. For businesses with meaningful seasonal or project-based load, 70–85% durable and 15–30% flexible is typical among high-margin operators; skewing further toward permanent inflates fixed cost through the trough.
- How do we avoid over-contracting into structural work?
- Contract only against defined, time-bounded scopes. Any contractor whose scope keeps renewing is either a hidden employee or a hidden capability gap; both need to be surfaced explicitly.
- When should automation precede hiring?
- Any workflow with high repetition, structured inputs, and predictable exceptions should be assessed for automation before it is staffed. The economics rarely support hiring against a workflow that will be substantially automated within 18 months.
Over to you
Of the last five hires you approved, how many would still be approved after a structured capability review?
Continue reading
Discussion
(…)Comments are moderated before appearing. Your email is only used for moderation and is never shown publicly.
Loading discussion…