Open the average recruiting dashboard and you'll find thirty tiles: pipeline velocity by stage, sourcer response rates, interview-to-onsite ratios, diversity funnel deltas, candidate NPS. Each one was added for a reason, and together they answer no question anyone is actually asking. For AI roles, where the market moves fast and a wrong hire is expensive, the question is simple: are we getting the right people, fast enough, and do they work out? Five numbers answer it. The rest is decoration, and worse than useless decoration, because every extra tile dilutes attention from the numbers that should be driving decisions this week.
The test a metric has to pass
Before listing the five, it's worth stating the filter that produces them, because the filter matters more than the list. A hiring metric earns its place only if a bad reading would change a decision within a week: reallocate sourcing budget, cut an interview round, escalate a stalled approval, revisit an offer band. Metrics that would never change a decision, no matter what value they showed, are reporting theater. Applications per posting is the classic example: whether it's 40 or 400, nobody does anything different, because volume was never the constraint for senior AI roles. Attention is a budget. A 30-tile dashboard doesn't give you 30 insights; it gives you five insights and 25 places for them to hide.
The five, and why each earns its place
| Metric | Plain definition | The decision it drives |
|---|---|---|
| Time-to-shortlist | Days from opening the role to having 3-5 candidates you'd genuinely hire | Is sourcing working, or do we need a different channel or partner |
| Time-to-offer | Days from first conversation with a candidate to a signed-off offer in their inbox | Where the process itself is leaking days — rounds, scheduling, approvals |
| Offer-accept rate | Of offers made, the share that get signed | Are we competitive on package, speed and pitch, or losing at the last step |
| 90-day success rate | Of people who started, the share still in seat and shipping at day 90 | Is our vetting bar actually predicting performance |
| Source quality | For each channel, the share of candidates who reach shortlist (and later, who succeed) | Where the next sourcing hour and dollar should go |
Why these five cover the whole system
The five aren't arbitrary — together they instrument every stage where hiring can fail, and nothing else. Time-to-shortlist isolates the top of the funnel: if you can't produce a credible shortlist in a reasonable window, no downstream fix matters. Time-to-offer isolates your own process: the market's best candidates decide inside a couple of weeks, so every day between first call and offer is a day a competitor can close them first. Offer-accept rate is your reality check on competitiveness — a strong funnel with a weak accept rate means you're doing expensive work to lose at the end. Ninety-day success rate is the only number that validates the vetting itself; everything upstream is a proxy until the person either ships or doesn't. And source quality closes the loop, telling you which channel produced the people who cleared the other four metrics, so next quarter's effort compounds instead of resetting.
- If time-to-shortlist is bad: the problem is sourcing, not process. Change channels before touching the interview loop.
- If time-to-offer is bad: the problem is internal. Map the dead time; it's usually scheduling and approvals, not deliberation.
- If offer-accept is bad: the problem is competitiveness — package, speed or pitch. More funnel volume won't fix it.
- If 90-day success is bad: the problem is the bar. Speed up nothing until the vetting signal is fixed.
What to deliberately not track
The stronger discipline is the second list: things you decide not to track, on purpose, and say so. Not because the data is unavailable — it's usually one click away — but because tracking it invites managing it, and managing an activity metric distorts behavior. A recruiter judged on interviews scheduled will schedule interviews; a team judged on pipeline size will keep weak candidates warm. Every one of these measures effort or motion; none measures whether hiring worked.
| Metric | Why it's decoration |
|---|---|
| Applications per posting | Volume is not the constraint for senior AI roles; signal is. High volume often means a vague posting |
| Interviews conducted per week | Measures activity. A team can interview constantly and hire nobody good |
| Pipeline size by stage | A big pipeline of people you won't hire is a cost, not an asset |
| Time-in-stage micro-breakdowns | Useful once, during a process audit; noise on a standing dashboard |
| Candidate NPS | Worth reading as comments, not tracking as a number; it moves with pleasantness, not rigor |
| Cost-per-hire in isolation | Meaningless without the 90-day success rate next to it; a cheap bad hire is the most expensive kind |
Definitions a CEO understands in one read
Each of the five should be explainable in one sentence to someone who has never opened an ATS, because if the definition needs a footnote, the metric is measuring your process instead of your result. The one-sentence versions: 'How many days until we had a real shortlist.' 'How many days from meeting someone to putting an offer in their hands.' 'When we make offers, do people say yes.' 'Three months in, are the people we hired actually delivering.' 'Which channels found the people who worked out.' Notice what's absent: stages, ratios, funnel jargon. A CEO reading these five numbers monthly knows whether hiring works, where it's broken, and roughly what to fix — which is the entire job of a dashboard.
The one-look dashboard
The whole thing fits on half a page: five rows, three columns — current value, target, trend arrow. Time-to-shortlist and time-to-offer in days, against targets you set from your own baseline (measure first, then cut). Offer-accept and 90-day success as percentages. Source quality as a short ranked list rather than a single number: each channel with its shortlist-rate, updated monthly. Review it weekly for the two time metrics — those move fast enough to act on — and monthly for the rest. Anything that wants to join the dashboard has to name the decision it drives and which of the five it explains better; if it can't, it goes in the appendix nobody reads, which is where it always belonged.
- Five rows, three columns: value, target, trend. If it doesn't fit on half a page, it's not this dashboard.
- Weekly cadence for time-to-shortlist and time-to-offer; monthly for accept rate, 90-day success, and source quality.
- Targets come from your own measured baseline, then get tightened — not from someone else's benchmark deck.
- New metric proposals must name the decision they drive. No decision, no tile.
