Getting a new technician productive faster

Hiring a technician is expensive in a way that is mostly invisible, because the cost is not the salary — it is the months of partial productivity, plus the senior tech whose own output drops while they carry a passenger.

Most shops do not measure this at all. They know roughly that "it takes a while", and they find out how long only when someone leaves at month four and the whole cost is written off.

Define ramp time so you can see it

Pick a threshold and measure weeks to reach it. Something like: the number of weeks until a tech completes a normal day of assigned calls, solo, at your standard efficiency, without escalating more than once.

The exact threshold matters less than measuring the same one every time. Once you have it for three or four hires, you have a baseline — and a way to tell whether a change to onboarding actually did anything, which is otherwise pure opinion.

Why ride-alongs alone do not scale

Pairing a new tech with a senior one is the default, and it is genuinely good for the parts that need hands — brazing, diagnostics under real conditions, customer interaction. It has two problems as a whole strategy.

It halves your best technician's productive output for as long as it lasts, which is the most expensive training there is. And it is unstructured: what the new tech learns depends entirely on which calls happened to come in that week. Two hires who start a month apart get completely different educations, and neither of them covers what did not happen to break.

A three-stage path with checkpoints

The structure that works in most shops is progressive independence with an explicit gate between stages.

Stage one — shadow

They observe and assist. The goal is context, not skill: how your company works, what the paperwork demands, how your customers are spoken to. Keep it short. Beyond a couple of weeks, watching stops teaching.

Stage two — assisted

They run the call; the senior tech is present but silent unless safety or the customer is at risk. This is the stage most shops skip, and skipping it is why techs go from passenger to solo and immediately generate callbacks. The value here is that mistakes happen with a safety net.

Stage three — solo with a floor

They run their own calls, with deliberately filtered work: known equipment, straightforward faults, forgiving customers. Escalation is expected rather than punished. The mistake here is dispatching by availability the moment someone is solo — one bad commercial call in week nine can undo two months of confidence.

Write the gate between each stage down. "Has completed X maintenance calls solo without a return visit" is a checkpoint. "Seems ready" is not, and it is how people get pushed out too early.

Remove the interruption tax

A new technician's day is punctuated by questions they cannot answer alone. Each one costs twice: their time waiting, and the senior tech or dispatcher pulled off their own work.

Most of those questions are not judgment calls. They are lookups — what does this code mean, what is the charge for this model, what did we do here last time. A new tech who can answer those without calling anyone gets independent much faster, and the calls that remain are the ones genuinely worth a conversation.

There is a confidence effect too, and experienced service managers will recognise it: techs stop asking before they stop needing to ask, because nobody wants to be the person who calls four times a day. That silence is where callbacks come from.

Track two things during ramp

• Escalations per day, trending down. If it plateaus above zero, they have hit a specific gap worth naming. If it drops to zero suspiciously fast, they have stopped asking — which is worse.
• Callback rate on their solo work, compared against your shop average rather than against zero. New techs will have some. The question is the trend.

And ask at 30, 60 and 90 days what they still do not feel confident about. People will tell you if the question is specific and there is no penalty attached to the answer.