The Fast but Sloppy Tech: Decision Tree

Why this matters

The fast-but-sloppy tech is one of the hardest people to manage, because the speed is real and visible and the sloppiness shows up later as callbacks, complaints, and rework you eat. They book a lot of jobs and look like a star until you total up the return trips. Left alone, they cost you more than a slow careful tech, and worse, they teach the crew that speed beats quality. This is a fixable problem most of the time, but you have to diagnose the cause before you reach for the fix.

Start here: confirm it is real and find the pattern

Before you confront anyone, get the facts. Pull the callback and rework data for the last few months. Look at this tech's rate against the crew average. Read the actual complaints, do not rely on a gut feeling.

Then sort the misses into a pattern:

• Same mistake repeatedly? That points to a knowledge or habit gap.
• Scattered, careless mistakes? That points to rushing or not caring.
• Only on certain job types? That points to a skill gap in one area.
• Only when overloaded? That points to a scheduling problem you created.

The pattern tells you which branch to take. Skip this step and you will coach the wrong thing.

Branch 1: Is it a skill gap or a care gap?

This is the fork that determines everything. Ask: does this tech know how to do it right and choose not to, or do they not actually know?

If the mistakes are the same technical error over and over, it is likely a skill or knowledge gap. The tech is moving fast through a step they never fully learned. This is the good news case, because skill gaps are teachable. Pair them with a strong tech on that specific task, do a few ride-alongs, have them walk you through the procedure so you can hear where the understanding breaks. Do not discipline a knowledge gap. Train it.

If the tech clearly knows the right way but skips it to save time, it is a care or habit gap. They are trading quality for speed because, in their mind, speed is what gets rewarded. This is a culture and accountability problem, and it goes to Branch 2.

Branch 2: Have you accidentally rewarded the speed?

Before you blame the tech, check your own incentives. Many fast-but-sloppy techs are doing exactly what they were trained to do.

If you pay or praise mostly on jobs-per-day or revenue, you built this. The tech is optimizing the number you put money and attention behind. The fix is not to yell at the tech, it is to change what you reward: add a quality gate so callbacks reduce the bonus, and start praising clean work as loudly as you praise fast work. Fix the incentive and a lot of "sloppy" techs clean up on their own.

If your incentives already balance speed and quality and the tech still rushes, move to the direct conversation in Branch 3.

Branch 3: The direct conversation

Sit down with the data in front of you. Not an ambush, a coaching talk.

• Lead with the facts, not adjectives. "Your callback rate is roughly double the crew. Here are three from last month." Concrete beats "you're sloppy."
• Acknowledge the strength. "You're one of the fastest guys I've got. That's real and I value it."
• Name the standard. "The job isn't done when it's fast, it's done when it doesn't come back. I need both."
• Ask, do not assume. "What's getting in the way of finishing clean?" Sometimes the answer surprises you: overloaded schedule, missing tools, unclear expectations.

Set a clear, measurable target and a date. "Let's get the callback rate under the line over the next sixty days." Then put it in writing so there is no ambiguity later.

Branch 4: They improve, or they don't

If the rate comes down, recognize it. Tell them you see the change and it matters. The behavior you praise is the behavior you keep. A fast tech who learns to finish clean is one of your most valuable people.

If nothing changes after honest coaching, a fair target, and real time, you are now looking at a fit and accountability issue, not a training issue. Move to a documented performance process: written warning, defined expectations, a final timeline. Keep records of the data and the conversations. Follow your written policy and, where discipline or termination is on the table, confirm your steps against your state's employment rules or an attorney, since requirements vary.

A tech who will not meet the quality standard, no matter how fast, is teaching your whole crew that the standard is optional. Protecting the standard sometimes means letting that person go. Slow is bad. Fast-and-wrong is worse, because you pay for the job twice.

References

• Society for Human Resource Management (SHRM), performance management and progressive discipline
• U.S. Small Business Administration (SBA), managing employee performance
• See related: Paying for Performance Without Gaming It
• See related: The Stay Interview: Keeping Them Before They Leave