Hiring pipeline diagnosis
Recruiting Funnel
The recruiting funnel treats hiring as a conversion pipeline — applicants to screens to interviews to offers to hires — with a measurable rate at every stage.
Its value is diagnostic: the funnel tells you exactly where a hiring problem lives, so you stop fixing sourcing when the leak is at offer.
- Problem
- Hiring pipeline diagnosis
- Altitude
- Function
- Effort to run
- Light
- Evidence base
- Established
Theory & origin
Borrowed from sales pipeline management, the funnel became the standard analytical lens for talent acquisition as applicant-tracking systems made stage data cheap. The mechanics are conversion arithmetic: stage-to-stage rates, time-in-stage, and cost-per-stage, benchmarked by role family. The insight discipline is that leaks have signatures — a weak top means employer brand or sourcing, a screen-to-interview collapse means miscalibrated criteria or a slow scheduling loop, offer declines mean comp or candidate experience. The critique worth carrying: candidates are not leads, and a funnel run purely for conversion efficiency produces the ghosting and keyword-gaming that damage the employer brand feeding its top.
Explore the model
How a consultant runs it
- 01 Instrument the stages first — most "hiring crises" arrive with no reliable stage data to diagnose.
- 02 Compute conversion, time-in-stage, and drop-out reasons per stage, benchmarked by role family.
- 03 Find the leak before proposing fixes: sourcing money spent on an offer-stage problem is pure waste.
- 04 Fix the biggest leak with the cheapest credible lever — structured criteria, scheduling SLAs, offer-approval speed.
- 05 Track candidate experience alongside conversion (decline reasons, NPS); a funnel optimized against candidates poisons its own top.
When to use
- 01 Diagnosing why roles stay open: locating which stage actually leaks
- 02 Budget conversations — defending or reallocating sourcing spend with conversion evidence
- 03 Setting recruiting SLAs and capacity plans grounded in stage math
When not to use
- 01 Executive and rare-skill searches, where n is tiny and relationships beat conversion math
- 02 As a pure efficiency machine — optimizing conversion while ghosting candidates burns the brand that feeds the funnel
- 03 Without stage discipline in the ATS; garbage stage data produces confident, wrong diagnoses
Worked example
An engineering org misses its hiring plan and asks for more sourcing budget. The funnel says otherwise: 400 applicants, 120 screened, 40 interviewed — healthy — but 12 offers produced only 6 hires, a 50% accept rate against a 85% benchmark. Decline interviews reveal a three-week offer-approval loop losing candidates to faster competitors. The fix costs nothing: pre-approved comp bands and a 48-hour offer SLA. Accept rate recovers to 83% the next quarter; the sourcing budget was never the problem.
Common pitfalls
- 01 Fixing the top of the funnel because it is visible, when the leak is at offer
- 02 Conversion rates without time-in-stage — a healthy rate that takes six weeks still loses the candidate
- 03 Screening criteria nobody calibrated, quietly filtering exactly the candidates the role needs
- 04 Optimizing to fill speed and never checking quality-of-hire, so the funnel wins while the org loses
Sample deliverable
One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.
Input — raw data
- Applicants400
- Screened120
- Interviewed40
- Offers12
- Hired6
Process — mapped
Stage counts convert to rates; the collapse against benchmark locates the leak
Funnel diagnosis — Relationship Managers, Q2
- Leakoffer accept 50% vs 85% bench
- Cause3-week approval loop
- Fixpre-approved bands + 48h SLA