Questions we answerHiring and headcount
Why do new starters take so long to get up to speed?
Usually because the knowledge is in one busy person's head and nobody owns the first month — not because the induction is thin or the person is slow.
Free · a few minutes · starts from “We have a capability gap”
The short answer
Usually because what they need to know lives in one busy person's head, and nobody owns their first month — not because the person is slow or the induction was too short. Onboarding software rarely helps at this size, because the missing thing is not a checklist. Find the three questions every new starter has to ask somebody, write those down, and give one named person responsibility for the first month. If the role itself was never defined, start there instead.
Slow onboarding is a symptom, and it is usually a symptom of something that was already true before the person arrived. The knowledge was concentrated, the role was vague, or nobody had time — and hiring simply made all three visible.
That is why the obvious interventions disappoint. A longer induction, a better handbook or a piece of onboarding software all address the ceremony rather than the cause, and none of them make the one person who knows things any less busy.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- New starters get stuck on the same three things, and only one person can unstick them.
- The person who knows is also the busiest, so questions queue.
- Nobody could say whose job it was to make the first month work.
Signs it's something else
- The role has changed twice since the advert, so nobody is clear what good looks like yet.
- The new starter has what they need and the work itself is genuinely hard, which takes the time it takes.
- Everybody takes this long, including people who have been here for years, which points at the process rather than at onboarding.
What's usually behind it
- Knowledge concentrated in one person who is too busy to teach and too central to interrupt.
- A role that was shaped after the person arrived rather than before.
- Nobody with explicit responsibility for the first month, so it belongs to everybody and therefore nobody.
What people usually get wrong
- Buying onboarding software for a twelve-person business, which organises the paperwork and leaves the cause untouched.
- Assigning the induction to whoever is free rather than to whoever knows.
- Writing an enormous handbook nobody reads instead of the three answers everybody needs.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Name an owner for the first month
Always. It is the cheapest intervention here and the most frequently skipped.
Write down the three repeated questions
New starters reliably get stuck in the same places. Answer those and leave the rest.
Define the role properly
The job was shaped after the person arrived. Time to productive cannot be fixed downstream of that.
Reduce the dependency
The bottleneck is one person's availability, which will be a problem long after this hire settles.
When doing nothing is the right call
Some roles genuinely take months, and treating normal ramp-up as a fault creates pressure that makes it slower. The signal worth acting on is new starters stuck on the same things, not new starters taking time.
What the diagnostic asks
- Whether the gap is capability, capacity, or both.
- Who owns this work today and how much of it is written down.
- How repeatable the role's core tasks are.
- How long this has been the pattern and whether it is getting worse.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Develop
Build the capability in someone already in the team, with time and support.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
What changes the answer
- One person holding the knowledge makes this a dependency problem rather than an induction one.
- A role that was never defined makes it a design problem, and no amount of onboarding fixes it.
- Hiring into the same role repeatedly justifies real effort; a one-off hire justifies much less.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Too much depends on one person. What are my options?Reduce the fragility before it becomes a crisis: write the work down, develop a second person, move adjacent work off them, or decide it is acceptable for now with a date to look again.
- We have a skills gap. Should I train, hire or bring someone in?It depends on how long you need the skill, how soon, and whether anyone in the team is close to it. Each answer points at a different route.
- Nobody has written our processes down. Is that a problem?Only where a process runs regularly and one person knows it. Documenting everything is a project small teams abandon; documenting a broken process makes the bad version official.
- Nobody owns this work. What do I do?Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
- Should I replace someone who left?A departure is the cheapest chance you will get to ask whether the role should exist in the shape it did. Replacing like for like is a decision, not a default.
- Can I afford to hire right now?Affordability is not the salary. It is the salary plus recruitment, onboarding, management time and the months before the person is productive — against what happens if you do not.