Six months in, your new hire still asks basic questions. You're starting to wonder if you hired wrong. Maybe they're slow. Maybe the role is over their head. Maybe you should have gone with the other finalist.
You're asking the wrong question. The right one is: how long should this take, and what have you done to make it happen faster?
Most managers don't actually know the answer. They have a vague feeling that someone should be "up to speed" by month three, get nervous by month six, and panic by month nine — but those numbers come from nowhere. They're vibes, not benchmarks.
Here's what the data actually says. Gallup pegs the average at around 12 months to reach full productivity. Other research lands closer to eight months. But averages hide the real picture. Entry-level roles typically reach full productivity in 1 to 3 months. Mid-level roles take 3 to 6 months. Senior or technical roles take 6 months to a year, sometimes longer. If you're managing a complex domain role and expecting fluency at 90 days, you're not setting a high bar — you're setting a fictional one.
The bigger problem isn't the timeline. It's that 35% of companies have no formal onboarding program, and only 37% extend onboarding beyond the first month. Organizations with a standard onboarding process see 50% greater new hire productivity. Translation: ramp time isn't really a function of the hire. It's a function of the system they're dropped into. And that system is yours.
So before you assess whether your new hire is too slow, do three things.
Define what "productive" actually means — before they start. Most managers can't articulate this. They know it when they see it. That's not a standard, that's a feeling. Write it down. For a mid-level engineer, productive might mean: ships a feature end-to-end without a senior review blocking them, owns one service in on-call rotation, and unblocks themselves on unfamiliar code within a day. For a sales hire: hits 80% of quota, runs discovery calls without you in the room, and forecasts within 15% accuracy. Specific. Observable. Binary.
Use 30/60/90 as a forecast, not a calendar. Most 30/60/90 plans are activity lists — meet these people, read these docs, complete this training. That's onboarding theater. A real plan ties each window to a slice of your productivity definition. By day 30, they own X. By day 60, they own Y. By day 90, they own Z. If they miss a milestone, you have a specific conversation about a specific gap — not a vague feeling that they're "behind."
When they miss, diagnose the bottleneck. New hires lag for one of four reasons: missing knowledge (they don't know the thing), missing access (they can't get to the thing), missing context (they don't know why the thing matters), or missing judgment (they know the thing but don't know when to apply it). Each requires a different intervention. Pairing them with a peer fixes knowledge gaps. Filing an IT ticket fixes access. Sitting them in on cross-functional meetings fixes context. Only judgment requires real time and reps — and judgment is the one you should be most patient with.
A reality check. Senior hires take longer than you think, and that's fine. Someone joining at the director level needs to learn the political map before they can lead anything, and that map takes 6-9 months minimum. Roles with deep domain context — regulated industries, enterprise sales, specialized engineering — also justify longer ramps. Don't compare your new VP to your new associate and conclude one is underperforming.
But here's the part most managers won't sit with: if your hires keep taking 9+ months to ramp, regardless of who they are or where they came from, the bottleneck isn't them. It's the environment you're handing them. Unclear expectations, no documentation, no peer mentor, no defined wins for the first quarter. You hired the person, then you set them loose to figure it out. That's not onboarding. That's hazing with a salary.
Bottom line: Time-to-productivity is a manager metric, not an employee one. If you can't say what "ramped" looks like before they start, the clock isn't measuring them — it's measuring you.