When One Technician Becomes Your Business Model

I was recently working through a staffing problem with a contractor when the conversation turned to the difference between their strongest technician and the next person in the batting order.

The gap was described as being about as wide as the Grand Canyon.

They had been recruiting for quite some time, but that gap remained. And the more we talked through the situation, the more apparent it became that the recruiting problem was only part of what needed attention.

Having an exceptional technician is a wonderful problem to have. Every service company needs people who can diagnose difficult problems, build trust with customers, recognize opportunities, and consistently produce profitable work. Those people deserve recognition, compensation, and opportunities that reflect their contribution.

The trouble starts when one person's extraordinary production becomes the standard by which leadership judges the health of an entire department.

When Strong Revenue Hides a Weak Bench

Imagine a service department where the top technician consistently handles the difficult calls, generates a disproportionate share of the revenue, and closes opportunities that the rest of the team struggles with.

The department's numbers might look respectable. Average ticket is healthy. Conversion is acceptable. Revenue is coming in. Management has enough evidence to believe the department is performing reasonably well.

But look a little closer.

How much of that production is coming from one individual? What happens to the department's results when that person takes a vacation? How many opportunities are being redirected toward that technician because leadership doesn't trust the rest of the team to handle them?

There's a difference between having a superstar and having a department that depends on one.

And when the financial performance remains acceptable, the urgency to address that difference can disappear.

Recruiting stays on the agenda. Managers continue interviewing. Everyone agrees the company needs stronger technicians. But there's no immediate financial emergency forcing leadership to reconsider how it develops the people already on payroll.

The strongest technician keeps producing, and the business keeps operating.

Until something changes.

The Financial Cost Is Bigger Than One Technician's Revenue

Most contractors understand the immediate revenue exposure associated with losing a top producer. What deserves more attention is the infrastructure supporting that production.

Consider what the company has already invested in its service operation.

There's the marketing expense required to generate calls, the customer service representatives answering those calls, dispatchers managing the board, service managers supervising performance, trucks, insurance, software, facilities, and the administrative organization behind everything.

Those expenses support the department, not merely its best technician.

If a disproportionate amount of the department's contribution comes from one person, leadership needs to understand whether the rest of that infrastructure is producing an acceptable return.

I'm not suggesting that every technician should produce identical revenue. Experience, technical ability, customer communication, and the types of calls assigned all influence individual results. Comparing two technicians without accounting for those differences can produce some pretty misleading conclusions.

But those differences are precisely what management needs to understand.

If your best technician consistently receives the strongest opportunities because they're the only person you trust to convert them, you have to separate the technician's ability from the opportunity advantage created by dispatch.

If your newer technicians receive simpler, lower-ticket calls, their revenue may be lower for perfectly legitimate reasons. That doesn't automatically mean they're underperforming.

On the other hand, if technicians with comparable experience and comparable opportunities are producing dramatically different results, the gap deserves investigation.

The question isn't whether everyone can become your best technician.

It's whether the organization knows how to develop a reasonably productive technician without depending on extraordinary individual talent.

The Dispatch Decision That Protects Today and Weakens Tomorrow

This is where the problem becomes particularly uncomfortable.

Let's say a high-value opportunity comes across the board. You have a technician who is exceptionally capable of handling it, and another who needs more experience.

Who gets the call?

In many circumstances, sending your strongest technician is the correct decision. The customer deserves someone capable of performing the work properly, and the company has a responsibility to protect the opportunity.

But if that becomes the answer every single time, the development problem never gets solved.

Your strongest technician continues getting stronger because they're exposed to more complex situations, more customer conversations, and more opportunities to exercise judgment.

Meanwhile, the technician you're hoping will eventually become a stronger producer may never receive the experience required to get there.

I'm not suggesting we sacrifice customer outcomes or gross profit for the sake of training. That would be an equally poor operating decision.

I'm suggesting leadership has to build a deliberate bridge between technical development and production.

Sometimes that means pairing technicians. Sometimes it means structured ride-alongs, reviewing recorded customer interactions, inspecting diagnostic procedures, or giving developing technicians progressively more challenging assignments with appropriate supervision.

The method depends on the business.

What matters is that development becomes something management deliberately schedules, observes, and evaluates rather than something it hopes will happen between service calls.

Recruiting Cannot Be the Entire Talent Strategy

There is a perfectly reasonable argument for recruiting experienced technicians. When a company has immediate demand and insufficient capability, hiring someone who can contribute quickly may be the best available option.

But consider the dependency you're creating if your entire staffing strategy requires finding another exceptional person every time you need to grow.

You're effectively asking the labor market to solve a capability problem your organization hasn't learned to solve internally.

And because the strongest technicians are difficult to replace, the business becomes increasingly vulnerable to the availability, compensation expectations, and career decisions of a relatively small number of people.

I would want to know what happens after someone joins the company.

Who evaluates their technical strengths and weaknesses? How do we determine which calls they're prepared to handle? Who is responsible for developing the areas where they're deficient? How does management know whether they're progressing?

If the answers depend entirely on whichever service manager happens to be in the building, then the company hasn't built a repeatable development process.

That doesn't mean formal training eliminates the need to recruit. It means recruiting and development have to support one another.

The goal isn't to manufacture another superstar overnight. It's to raise the productive capability of the department so the company isn't continually depending on extraordinary individual performance to compensate for ordinary organizational weaknesses.

Measure the Department Without Its Strongest Performer

One exercise I would encourage owners to consider is evaluating departmental performance with the top producer separated from the rest of the team.

Not because that technician has done anything wrong. Quite the opposite.

I want to see what the rest of the organization is capable of producing.

Look at revenue, gross profit contribution, completed calls, conversion, callbacks, and other measures appropriate to the work. Account for call mix, experience, and differences in available hours before drawing conclusions.

Then look at the trend.

Are the remaining technicians improving? Are newer people developing into independently productive employees? Is the gap narrowing because the bench is getting stronger, or is the department becoming increasingly dependent on its strongest individual?

I would also look at how often that person is being pulled into other technicians' jobs, asked to solve technical problems over the phone, or used as the unofficial supervisor when management doesn't have the answer.

Some of that is healthy collaboration. Too much of it can mean the company's apparent production capacity depends on the same individual performing several jobs simultaneously.

That matters when you're deciding whether to add trucks, increase marketing, hire another dispatcher, or expand into another territory.

Before adding more demand, I want to know whether the organization has the capability to handle it profitably without putting an even greater burden on the person already carrying the department.

What Happens When the Superstar Leaves?

The obvious concern is that your strongest technician eventually resigns, retires, becomes unavailable, or takes an opportunity elsewhere.

But I wouldn't wait for that event to evaluate the business.

The real exposure exists while they're still employed.

It shows up in the calls nobody else can handle, the opportunities management won't assign to developing technicians, the customers who insist on one individual, and the amount of supervision required to keep the rest of the department functioning.

None of those conditions automatically makes the company unhealthy. Exceptional employees naturally become trusted resources.

The problem is allowing that dependency to grow without recognizing what it means for the organization's future.

A strong technician should make the company better. Their experience should help develop the people around them, their performance should inform better operating standards, and their success should give management a clearer understanding of what excellence looks like.

But the company still has to do the work of building the next generation of capable technicians.

If your strongest technician leaves tomorrow and the department falls apart, the problem didn't begin on the day they resigned.

It was there while they were still producing.

The question is whether leadership was measuring the strength of the department or simply enjoying the results of its strongest employee.