A Tech Does Great Work but Has a Bad Attitude: Decision Tree

Why this matters

A skilled tech with a bad attitude is the problem owners handle worst, usually by swinging between two mistakes: tolerating it because the work is good, or over-reacting and cutting a useful person who was actually telling you something true. The right fix depends entirely on what is driving the attitude and who is absorbing it, and those are different questions from "do I keep them." This tree sorts the attitude before you decide anything, so your response lands where it belongs. The keep-or-cut call comes later, and only for the cases that earn it.

Safety first: rule out the version that is not an attitude problem

Before you treat this as attitude, check for conduct that is not attitude at all: threats, intimidation, violence, harassment of a coworker, or someone impaired on the job. If any of that is present, stop here. This is not a coaching case, and skill is irrelevant to it. Separate the person from the crew if there is any immediate risk, then handle it as a for-cause matter now, documented, with a hard line. Because for-cause handling varies by state, confirm the steps with an employment attorney or your state labor office in the same motion. The rest of this tree applies only to the merely sour, not the dangerous.

Start here: name the behavior, not the vibe

"Bad attitude" is not something you can act on. Write down the specific thing they do: shows up short and stays short, pushes back on every new process, goes quiet and does the minimum, mutters to the crew, sighs at customers. You cannot route a feeling. The specific behavior tells you both what is driving it and who it lands on, which are the two forks that decide your move.

Fork 1: is the attitude attached to a real grievance?

This is the fork owners skip, and it is the most common miss. A skilled person's sourness is often a signal, not a defect.

• If the attitude tracks a legitimate cause - underused and bored, a promise you did not keep, a broken process they are right about, passed over without explanation - then the attitude is a symptom. Fix the cause and the attitude usually follows. Disciplining it here just confirms to a good tech that you do not listen, and it is how you lose them. See related: Separating a Skills Gap From a Will Gap.
• If there is no real grievance, or the grievance was genuinely addressed and the attitude stayed, continue.

Ask them directly and listen for whether the complaint holds up. A grievance with a point gets fixed; a grievance that is only a habit of complaint gets handled as behavior.

Fork 2: who is absorbing it?

The same attitude is a minor annoyance or a real fire depending on where it lands. Route by target.

• At you, in private (grumbling, pushback in a one-on-one): lowest urgency. Blunt honesty from a skilled hand is not toxicity, and a tech who challenges you in private can be worth more than one who nods and coasts. Set the line on tone, keep the dissent.
• At customers (curt, dismissive, visibly annoyed on site): high urgency. This costs you reviews, referrals, and repeat work directly. Address it now, name the specific on-site behavior, and make the standard concrete.
• At the crew, especially juniors (mocking, undermining, spreading cynicism): highest urgency. This is the one that spreads and drives out good people. Do not let skill buy a pass on it. See related: The Skilled Employee Who Poisons the Crew.

Fork 3: coach it once, then read the response

For anything left after the first two forks, the attitude is real, unforced, and landing on someone. Now coach it, once and clearly: name the exact behavior, name its effect, state the standard and a bounded window. Then watch what they do, because the response is the actual diagnosis.

• If they hear it and adjust, you had a fixable habit. Reinforce it and move on.
• If they comply for a week and revert, or get defensive and blame everyone else, the behavior is a choice they intend to keep.
• If they answer accountability with a threat to walk or take customers, they have shown you who they think runs the shop.

When it becomes a keep-or-cut question

The moment coaching has had a fair, clear shot and the behavior is still landing on customers or crew, this stops being a diagnosis and becomes a retention decision. Hand it to that call rather than coaching in circles. See related: Good Tech, Bad Attitude: Coach vs Cut Decision Tree, and The Toxic Star: Keep vs Cut Decision Tree.

Recap

1. Safety and harassment first. That is conduct, not attitude, and skill does not offset it.
2. Name the specific behavior, not the vibe.
3. Check for a real grievance underneath; fix the cause before you correct the person.
4. Route by who absorbs it: private dissent is cheap, customer-facing and crew-facing are urgent.
5. Coach once, clearly, and judge the change. Only if it persists does it become a keep-or-cut call.

References

• Society for Human Resource Management (SHRM), performance management and workplace conduct
• U.S. Small Business Administration (SBA), managing problem employees
• See related: Separating a Skills Gap From a Will Gap
• See related: Good Tech, Bad Attitude: Coach vs Cut Decision Tree, The Skilled Employee Who Poisons the Crew