The Hiring System Health Framework assesses an organisation's executive hiring function at the system level — not the mandate level. It evaluates four system layers: observability (can you see what is happening inside active mandates?), intelligence (do you know why mandates succeed or fail?), execution (can you act on mandate signals faster than failure accelerates?), and attribution (can you measure the ROI of your hiring system?). Each layer is scored 0–25, producing a system health score of 0–100. A score below 50 means the organisation is operating a hiring system that is structurally likely to produce failure at scale.
System Health vs. Mandate Health
A mandate can be healthy inside an unhealthy system — just as a single service can be running well inside a degraded infrastructure. The Hiring System Health Framework evaluates the infrastructure itself: the monitoring, the intelligence, the execution capability, and the ROI visibility. An unhealthy system produces healthy mandates by accident and failing mandates by design. A healthy system produces healthy mandates by design and catches failing mandates before they fail.
"Datadog doesn't exist because individual servers were crashing. It exists because the infrastructure for knowing whether servers might crash didn't exist. The Hiring System Health Framework is the same insight applied to executive search."
System Health Layer Scoring
| Layer | Weight | What It Measures | Score 20–25 (Healthy) | Score 0–10 (Critical) |
|---|---|---|---|---|
| Observability | 25% | Real-time visibility into mandate signals: response rates, stage velocity, recruiter load, HM engagement | Automated signal collection; daily Health Score; breach alerts firing | No real-time data; weekly or monthly reporting only |
| Intelligence | 25% | Understanding of why mandates succeed and fail: playbook effectiveness, market patterns, prediction accuracy | Failure Prediction Engine active; playbook library built and updated; market data accumulated | No systematic post-mandate review; no playbook documentation; anecdotal knowledge only |
| Execution | 25% | Ability to act on signals faster than failure accelerates: recovery playbook trigger time, intervention success rate | Recovery playbooks trigger within 24hr of threshold breach; 70%+ intervention success rate | Manual intervention only; average 5–7 days from signal to action; low recovery rate |
| Attribution | 25% | Ability to measure the financial ROI of hiring operations: cost per placement, cost of vacancy, system ROI | Full attribution layer; cost-of-vacancy calculated per mandate; ROI reported to CEO/CFO monthly | No financial attribution; fee cost only; cost of vacancy not calculated; board-level hiring data absent |
Frequently Asked Questions
What is the most common system health profile for a Series B SaaS company?
Observability: 8/25 (basic ATS reporting only). Intelligence: 5/25 (no systematic playbook documentation). Execution: 12/25 (manual playbooks, inconsistently applied). Attribution: 4/25 (fee cost tracked, no ROI). Total system health score: approximately 29/100. This is a Level 2 organisation on the Maturity Model — tracked but not managed. The most impactful single upgrade from this state is closing the observability gap: even basic real-time tracking of response rates and stage velocity produces immediate intervention capability.
How does the Hiring System Health Framework differ from the Hiring Operations Maturity Model?
The Maturity Model describes the five levels of operational sophistication and the capabilities at each level. The System Health Framework provides a diagnostic score for the current state across four specific system layers. They are complementary: the Maturity Model tells you where you are on the journey; the System Health Framework tells you which specific capability gap is most limiting your current level.
Can an organisation score high on execution but low on observability?
Rarely — and when it happens, the high execution score is misleading. An organisation that executes recovery actions well but has no real-time observability is executing reactively, not proactively: they notice failure after it is visible (too late for maximum-efficiency recovery) and then recover it quickly. This pattern produces lower mandate health overall than an organisation with strong observability and moderate execution, because early detection is worth more than fast recovery.