How to Measure Time to Productivity for New Hires

The average new hire takes 8 months to reach full productivity. Most teams can't tell you where any given hire sits on that curve — whether they're three weeks ahead or six weeks behind — until a problem makes it obvious. Onboarding gets run on a feeling: "they seem to be getting it." Feelings are a bad way to manage an expensive, eight-month process.

Time to productivity is the metric that turns onboarding from a vibe into something you can manage. It's also the metric most teams skip, usually because they assume measuring it requires an enterprise analytics suite. It doesn't. A handful of simple signals — completion, milestones, and honest check-ins — tell you almost everything you need, and they're worth tracking precisely because companies with a strong onboarding process see 82% higher retention.

This is what to measure, how to measure it without overbuilding, and how to set it up in Trainual so the numbers come from the system you already run onboarding in. (It pairs with the 30-60-90 day onboarding plan — the plan sets the milestones; this piece measures whether you're hitting them.)

What is time to productivity?

Time to productivity is how long it takes a new hire to reach the output expected of a fully ramped person in their role. It's measured from the start date to the point where they're working independently at target quality and pace. Shorter is better — but only if quality holds, which is why it's tracked alongside other signals rather than on its own.

The reason it's the headline onboarding metric is that it captures what everything else is in service of. A new hire can complete every training module and still take eight months to contribute; another can skip half the modules and ramp in six weeks. Time to productivity measures the outcome onboarding exists to produce, not the activity that's supposed to produce it.

What onboarding metrics actually matter?

Five: time to productivity, milestone completion, early retention, ramp consistency across hires, and new hire confidence. Together they answer the only questions that matter — is this hire ramping, is the program working across hires, and where does it break? Each is simple to capture, and none requires more than the system you already onboard in.

The trap is measuring activity instead of progress. Logins, hours logged, and modules opened feel like data, but they tell you someone is busy, not that they're ramping. The metrics worth tracking are the ones tied to the milestones in your plan — and the ones that would change a decision if they moved.

How do you measure time to productivity without an enterprise analytics stack?

Anchor it to milestones, not dashboards. Define what "ramped" looks like in the role, set checkpoints at 30, 60, and 90 days, and measure the gap between the start date and the day the new hire clears the final milestone independently. The instrument isn't a complex report — it's a clear finish line plus the check-ins that track progress toward it.

Most of what you need is already in the path. A role-based training path shows completion and where someone stalled. Version history shows what changed and when, so you can tie a ramp problem to a process that shifted under the new hire. And a searchable knowledge base tells you, by what people search for, where the documentation is thin — which is often where ramp slows. You don't need a separate analytics product to read these signals; you need onboarding to run in one place so the signals exist at all. For the operational how-to on pulling progress and reporting out of your system, using an LMS for team accountability tracking and reporting and scorecards and KPI tracking both go deeper.

What does good time to productivity look like?

It depends on the role, so measure against your own baseline, not a benchmark. Capture how long ramp takes today, then watch whether structured onboarding moves it. Trainual cut sales rep time to value from months to weeks — the number that matters isn't an industry average, it's your own before-and-after.

The point of a baseline is that it makes improvement visible and arguable. "Onboarding feels better" doesn't survive a budget conversation; "ramp dropped from eleven weeks to seven across our last six hires" does. That's the quiet payoff of measuring at all — it turns onboarding from a cost nobody can defend into an investment with a number attached. The companies with measurable ROI from Trainual all share that trait: they can point to a before and an after, because they wrote down the before.

How do you keep onboarding measurement honest over time?

Review the numbers at the same cadence as the plan — every 30 and 90 days — and treat new hire feedback as data, not decoration. The most reliable signal of a broken onboarding step is several hires stalling at the same checkpoint. When the milestones, the path, and the feedback all live in one single source of truth, that pattern is visible instead of anecdotal.

Numbers go stale when nobody owns them. Assign the review, keep it short, and let the AI Assistant surface the documented answers people keep searching for during ramp — those searches are a live map of where onboarding is unclear. This is also where onboarding measurement connects to the bigger picture: the same signals that show a new hire ramping show you whether your first 30 days and your onboarding checklist are doing their job, so the whole cluster improves from one set of measurements.

Quick wins to start this week

You can start measuring time to productivity before your next hire reaches day 30.

Quick win #1: Write down your current ramp time

Estimate how long your last few hires took to work independently. A rough baseline beats no baseline — it's the number every improvement gets measured against.

Quick win #2: Define the day-90 finish line

Name the two or three things a fully ramped person does on their own. That's your time-to-productivity target; everything else measures progress toward it.

Quick win #3: Add a milestone check to your 30- and 90-day reviews

Turn the check-ins into measurements: did this hire clear the milestone the plan set? Track yes or no across hires and the pattern appears fast.

Quick win #4: Watch what new hires search for

The questions new hires ask the knowledge base are a free map of where your documentation — and your ramp — is weakest.

Quick win #5: Pick one metric to report monthly

Choose a single number — time to productivity or milestone completion — and report it monthly. One tracked metric beats a dashboard nobody opens.

Ready to see how Trainual works?

👉 Book a demo and see how Trainual turns your onboarding path into measurable ramp data without a separate analytics tool.

Want a sneak peek?

👉 Read customer stories from teams who can point to a before-and-after on ramp time.

Frequently asked questions

What is time to productivity?

Time to productivity is how long it takes a new hire to reach the output expected of a fully ramped person in their role, measured from the start date to the point where they're working independently at target quality and pace. Shorter is better, but only if quality holds — which is why it's tracked alongside other signals rather than on its own.

What onboarding metrics should I track?

Five matter most: time to productivity, milestone completion, early retention (especially through 90 days), ramp consistency across hires, and new hire confidence from check-ins. Together they tell you whether a hire is ramping, whether the program works across hires, and where it breaks. Avoid activity metrics like logins or hours — they show someone is busy, not that they're progressing.

How do you measure time to productivity?

Define what "ramped" looks like in the role, set checkpoints at 30, 60, and 90 days, and measure the gap between the start date and the day the new hire clears the final milestone independently. You don't need an enterprise analytics suite — a clear finish line, the completion data in your training path, and honest check-ins give you the number.

Do you need special software to measure onboarding?

No. You need onboarding to run in one place so the signals exist. A role-based path shows completion and where people stall, version history ties ramp problems to process changes, and knowledge base searches reveal where documentation is thin. Those are the measurements that matter, and they come from the system you already onboard in rather than a separate analytics product.

What's a good time to productivity?

It depends entirely on the role, so measure against your own baseline rather than an industry average. Capture how long ramp takes today, then watch whether structured onboarding moves it. The useful number is your own before-and-after — that's what proves onboarding is working and what survives a budget conversation.