The Carried Underperformer: Decision Tree
Why this matters
Every crew has someone the others quietly cover for. They take twice as long, leave the cleanup, miss the things a second-year should catch, and the rest of the team picks up the slack without saying anything, until they do. A carried underperformer is not just one weak link, they are a slow leak in everyone else's morale. The strong people see who is dragging, they see you not addressing it, and they conclude that effort does not matter here. This tree separates the techs who can be fixed from the ones who are dead weight, so you stop paying for the wrong one.
Start here: is the underperformance a safety issue
Before you coach anything, ask whether the gap is in safety-critical work, missed lockout, sloppy gas or electrical practice, shortcuts that could hurt someone or burn a house down. If yes, that is not a development conversation, it is a "you do not do that work unsupervised until this is right" call, today. A slow tech is a scheduling problem. An unsafe tech is a liability you cannot carry no matter how much you like them. Pull the unsafe work first, then run the tree on the performance itself.
Step 1: Name the actual gap
"Underperformer" is too vague to fix. Pin down which kind of gap it is, because they have different cures.
| Gap type | What you see | Fixable by |
|---|---|---|
| Skill gap | Knows what to do, cannot yet do it well | Training and reps |
| Knowledge gap | Does not know the right method | Teaching, a checklist, a mentor |
| Speed gap | Does it right but far too slow | Reps, then a candid pace conversation |
| Will gap | Can do it, chooses not to put in the effort | A boundary, not more training |
| Fit gap | Wrong role or wrong trade for them | A move, or an exit |
The first three you can coach. A will gap does not respond to training because the person is not lacking ability, they are lacking effort. A fit gap does not respond to either. Diagnosing this wrong is why owners pour months of training into someone who was never going to try.
Step 2: Confirm they actually know they are behind
Surprisingly often, the carried tech does not know. The crew has covered so smoothly and you have said so little that the person genuinely thinks they are doing fine. Before you escalate, they get a clear, specific, private conversation: here is the standard, here is where you are against it, here is what good looks like. No hints, no "you might want to pick it up." Concrete: "A maintenance call should take about this long and yours run nearly double, and the last three left parts behind. Let us close that gap."
Step 3: Set a real plan with a real deadline
Vague feedback gets vague results. If the gap is coachable, build a short plan they can actually hit:
- One or two specific targets, not ten. Pace on a defined job type. A clean checklist completion. Pick what matters most.
- A support, not just a demand. Pair them with your best tech for a week, give them the checklist, ride along once. You are obligated to make improvement possible, not just to ask for it.
- A date. "Let us look at this again in thirty days." A plan with no deadline is a wish.
Write it down. A documented plan protects the tech (they know exactly what to do) and protects you (if it comes to an exit, you tried fairly and have the record).
Step 4: Read the trend, not the day
Improvement is rarely a straight line. Watch the slope over the window, not a single good or bad day.
- If they are closing the gap, even unevenly, keep coaching. Reps take time and you have a return on the way.
- If they are flat, dig into why. Is the plan wrong, the support thin, or is this actually a will or fit gap wearing a skill costume.
- If they slide back the moment the pressure is off, you have your answer. The issue was never ability.
Step 5: Decide develop, redeploy, or release
After a fair, supported, documented attempt, one of three calls is honest.
- Develop. Coachable gap, real progress, worth the investment. Most newer techs with a skill or knowledge gap land here. Keep going.
- Redeploy. Good person, wrong role. The slow installer who is meticulous on maintenance, the tech who is weak in the field but sharp on the phone. A fit gap is often a placement problem, not a people problem. Move them before you lose them.
- Release. A will gap that did not change after a clear boundary, or a fit gap with no role that fits, is dead weight you are asking your best people to carry. Keeping them is a tax on everyone who pulls their own weight. Let them go cleanly and with dignity.
Step 6: Close the loop with the crew
The people who carried this person have been watching. You will not, and should not, share the private details, but the crew needs to see that you saw it and acted. When the situation resolves, the slack-pickers feel it immediately. If you do nothing, they learn the lesson you least want taught: that the way to get ahead here is to do less and let others cover.
Quick recap
- Safety gaps come out of the field first, no exceptions.
- Name the gap: skill, knowledge, speed, will, or fit.
- Tell them plainly and specifically where they stand.
- Build a supported, dated, written plan if it is coachable.
- Judge the trend, then develop, redeploy, or release.
References
- Trade-standard practice for performance management and field-tech development
- OSHA General Duty Clause on safe work practices (29 CFR 1910)
- See related: Build a Skills Matrix: Who Can Do What, Conducting Performance Reviews, Firing With Dignity: The Respectful Exit