A Good Tech Is Underperforming: Decision Tree

Why this matters

This is not the tech who was never good. This is the one who was, and lately is not. The numbers slipped, the callbacks ticked up, the paperwork got sloppy, and it is someone you know can do the work because you have watched them do it well. That change is the whole diagnosis. A tech who never had the skill needs training. A tech who had it and lost the output needs you to find out what changed, because the fix for a skill gap will do nothing for a burnout, a grievance, or a life that came apart at home. Treat the drop as a signal, not a verdict.

Start here: is the slip in safety-critical work?

Before you diagnose anything, check where the decline is showing up. If a normally careful tech is now skipping lockout, cutting corners on gas or electrical, or leaving work that could hurt someone, that part comes out of the field first, today. Pull them off unsupervised safety-critical work until it is right, then run the rest of this tree on the performance itself. A distracted tech is a management problem. A distracted tech working hot is a liability you cannot wait on.

Step 1: confirm the drop is real, not a bad week

Everyone has an off stretch. Before you act, look at the trend over a few weeks, not one job. Pull what you actually track: pace, callbacks, completion, complaints. A single rough job on a genuinely hard call is noise. A steady slide across several weeks and several job types is signal. If it is one bad week with an obvious cause, note it and wait. If the slope is real, continue.

Step 2: sudden or gradual?

The shape of the decline points you toward the cause.

• Sudden (fine one month, off the next) usually means an event: something changed at home, a health issue, a conflict on the crew, a specific incident at work that landed hard. Something happened on a date, and you are looking for it.
• Gradual (a slow fade over months) usually means erosion: creeping burnout, quiet disengagement, a resentment that built, or a tech who has mentally started leaving. Nothing happened on a date; the slope itself is the finding.

Step 3: what changed around them?

Before you assume the problem is inside the tech, check what you changed. Good performers often slip in response to something external you control.

• A workplace change: new pay structure, a route or territory shift, a new boss or lead, a process or software rollout they resent, a promotion they were passed over for.
• A workload change: they got loaded with the hard calls, the overflow, or the training burden and nobody adjusted for it. Your best tech quietly absorbing everyone else's slack looks like a performance drop right before it looks like a resignation.
• A recognition change: they carried a big stretch, nobody noticed, and they throttled back.

If you find a cause here, the fix is often yours to make, and it is cheaper than replacing them.

Step 4: have the direct, curious conversation

You will not diagnose the rest from the outside. Sit down privately and lead with what you have seen and your read that it is not like them: "Your last several jobs are running behind and that is not how you work. What is going on?" Then stop talking. The goal of this conversation is information, not correction. A good tech under strain will usually tell you if you make it safe to. Listen for the three big buckets:

• Personal or health: something outside work is eating their focus. This is a support-and-accommodate situation, often temporary. See related: The Tech Going Through Something Personal.
• Grievance: they feel wronged, overloaded, underpaid relative to a new hire, or overlooked. This is fixable if you hear it and act, and corrosive if you do not.
• Disengagement: they have checked out, are coasting, or are already interviewing. This is the hardest bucket and the one you confirm last, not first.

Step 5: match the response to the cause

• If it is personal or health: offer real flexibility and a defined check-back point. Do not put a grieving or sick tech on a formal plan; carry them like you would want to be carried, within reason.
• If it is a grievance or a workload or recognition change: fix the thing. An adjusted route, an honest pay conversation, an overdue thank-you, a redistributed load. Then watch the trend recover.
• If it is disengagement with no fixable root: now you shift from diagnosis to standard-setting. State the expectation plainly, name the gap, and give a clear, bounded chance to close it. If it does not, you are into the coach-or-cut decision like any other underperformer.

Step 6: watch the slope after you act

Give the fix a defined window and read the trend, not the next single day. A good tech with a real reason usually rebounds visibly once the cause is addressed. If you fixed a genuine external cause and the output still does not recover, the story was never the cause they named, and you treat it as disengagement.

Quick recap

1. Safety-critical slips come out of the field first.
2. Confirm the drop is a trend, not a bad week.
3. Read the shape: sudden points to an event, gradual points to erosion.
4. Check what you changed before blaming the tech.
5. Have the curious conversation and sort personal vs grievance vs disengagement.
6. Fix the cause, then judge the slope over a fair window.

References

• Trade-standard practice for field-technician performance diagnosis
• OSHA General Duty Clause on safe work practices (29 CFR 1910)
• See related: The Carried Underperformer: Decision Tree; Coach the Underperformer or Cut Them Loose: Decision Tree