Extended definition
Time to productivity (TTP) measures the gap between a new hire’s first day and the point where they’re doing the job at the standard you hired them for. You’ll also see it called ramp-up time, time to proficiency or time to full productivity. It picks up where onboarding begins and the usual hiring metrics stop. Time to fill and time to hire end when someone accepts an offer or starts. Time to productivity asks how long until that person is actually pulling their weight.
The hard part is defining “productive.” There’s no universal standard, so each role needs a milestone agreed before the person starts. It should be observable and tied to the job:
- A sales rep closing a full month at quota.
- A support agent handling a full queue at the team’s target quality score.
- An engineer shipping changes to production without a reviewer rewriting them.
- A recruiter running a full requisition load with shortlists the hiring managers are happy with.
Without that milestone, TTP turns into a manager’s gut feel, which drifts from team to team and can’t be compared over time.
How to measure time to productivity
For one hire, the formula is simple:
Time to productivity = date the agreed milestone is first met minus the start date
For a group, average the individual results for people in the same role who started in the same period. Here’s a worked example with illustrative numbers. Four support agents start in the same month and reach the agreed milestone after 42, 49, 56 and 63 days. Their average time to productivity is 210 days divided by 4, or 52.5 days.
Two refinements make the number more useful:
- Track progress, not just the finish line — You can also record each hire’s share of full output at 30, 60 and 90 days. That shows whether someone is on track well before the milestone date.
- Record who never got there — If someone leaves before reaching the milestone, log it. Dropping them from the average makes the cohort look better than it was, which is why TTP is worth reading alongside 90-day retention.
Why time to productivity matters
Until a new hire is productive, you’re paying a full salary for partial output, and often some of a colleague’s time to train them as well. That’s why the cost of vacancy doesn’t stop when the seat is filled: it tapers off as the new hire ramps up. A shorter ramp-up is money back, which is why time-to-productivity savings show up in hiring ROI calculations.
It’s also one of the clearest checks on whether hiring is working. A long ramp-up can mean the hire didn’t have the skills the interview said they had, or that onboarding is thin. Split TTP by source, interviewer or assessment score, and you can start to see which. That makes it a natural input to quality of hire, alongside performance ratings and retention.
Common mistakes and misconceptions about time to productivity
- Measuring without a defined milestone — If “productive” is decided after the fact, the metric measures the manager’s mood, not the hire.
- Comparing across roles — A support agent and a senior engineer ramp at different speeds. Benchmark each role against its own history.
- Blaming one team — A long ramp-up gets pinned on recruiting or on onboarding when the cause could be either, or both. Look at the split before assigning it.
- Chasing speed alone — Pushing someone to a full workload before they’re ready can trade a shorter TTP for more errors and an early exit.
- Starting the clock in the wrong place — TTP starts on day one. Time spent filling the role belongs to time to fill, so keep the two separate rather than adding them into one number.
Frequently asked questions
How do you calculate time to productivity?
Subtract the new hire's start date from the date they first meet a milestone you agreed in advance, such as a full workload at target quality. That gives one person's time to productivity in days. For a team or role, average the results for everyone who started in the same period, and log anyone who left before reaching the milestone rather than dropping them, or the average will look better than it was.
What is a good time to productivity?
There isn't a universal benchmark, because it depends on the role, its complexity and how productive is defined. A good time to productivity is one that's shorter than your own baseline for the same role, without a drop in quality or retention. Set the baseline from your last few cohorts, then judge changes in hiring or onboarding against it rather than against another company's number.
Is time to productivity a KPI?
It can be, and it's one of the few hiring-related metrics that measures what happens after the start date. As a KPI it works best when each role has a defined milestone, the number is tracked by cohort, and it's read alongside quality and retention measures. On its own, a falling number can hide problems, such as new hires being pushed to a full workload before they're ready.
What is another term for time to productivity?
The most common alternatives are ramp-up time, time to proficiency, time to full productivity and speed to competency. Sales teams often shorten it to ramp time. They all describe the same idea: how long a new hire takes to perform at the expected level for their role. The label matters less than defining the milestone that counts as productive and measuring it the same way every time.
How does onboarding affect time to productivity?
Directly, because onboarding fills most of the period being measured. Clear goals for the first weeks, early access to tools and systems, a named buddy and regular check-ins all help close the gap between day one and full output. If a role's time to productivity rises while interview scores hold steady, onboarding is the first place to look. If it rises for hires from one source, look at selection instead.