Time to productivity is the number of days between a new hire's start date and the point where they meet an agreed performance bar for their role. It differs from time to hire, which ends at acceptance, and from onboarding length, which is a calendar of activities rather than an outcome.
This is the hard part, and skipping it produces a metric nobody trusts. The bar must be observable and specific to a role family, not a general sense that someone has settled in. For a support role it might be handling a standard case load unaided at the team's quality standard. For a salesperson, a first closed deal sourced independently. For an engineer, shipping a change of defined scope without supervision. Write the bar down before the hire starts, agree it with the manager, and keep it stable long enough to compare cohorts. Roles where nobody can articulate the bar are usually roles with unclear expectations generally, which is worth discovering on its own. Reuse the language from the [job description](/job-descriptions) so the bar matches what was advertised.
Time to hire ends the moment a candidate accepts, so it says nothing about whether the person could do the job. Onboarding length is a schedule: two weeks of induction, a thirty-day plan, a checklist completed. Neither measures capability. Time to productivity is the only one of the three that reports an outcome, which is also why it is the hardest to collect. The three connect in a useful way. A fast time to hire that produces a long ramp suggests the process optimised for speed over fit. A short ramp following a long, careful search suggests the extra time bought something real. Reading them as a sequence gives a much better picture of hiring effectiveness than any of them alone.
Manager subjectivity heads the list. When the bar is a judgement call, two managers will place the same person weeks apart, and a generous manager makes their hires look excellent. Role type is the second issue: individual contributors reach a measurable output bar far sooner than leaders, whose contribution shows up through a team over quarters, so averaging across both produces a number that describes nobody. Company conditions matter too. A hire joining during a reorganisation ramps slowly for reasons unrelated to selection. And small cohorts make month-to-month movement meaningless. Record the bar, the assessor and the conditions alongside the number of days, then compare like with like. Without that context the metric becomes a way to argue rather than a way to learn.
Three levers do most of the work, and only one of them belongs to recruiting. Accurate role description shortens the ramp because the person arrives expecting the job they get. Preboarding shortens it because access, equipment and context are handled before day one instead of consuming the first week. And a manager who sets the bar explicitly on day one shortens it because the hire knows what they are aiming at. Assessment design matters too: a work sample resembling the real job predicts ramp better than a conversation about it. Recruiting can supply the interview evidence and the [talent acquisition platform](/talent-acquisition-software) record that lets a manager see what was assessed, which stops the first month being spent rediscovering it.
Pitch N Hire unifies sourcing, screening and hiring decisions on one AI-native platform. Book a quick demo on your real roles.
Prefer to talk? Book a demo · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
