4d (edited) • 📣General discussion📣
How to hold a tech accountable without losing him
This is the practical working guide I used to write the previous story post:
This is an action document and practical framework you can use to handle any discipline or accountability conversation in your shop.
By-the-way, The Technician Find Copilot Bot is trained on this conversation framework. You can feed it the scenario from your shop and it will guide you through having the conversation so it won't be awkward.
DM me if you want a 14-day free trial of the bot.
_______________________________________________
The confession inside the question
A shop owner said this out loud:
"Some of my guys are special snowflakes and can't take critical feedback. If I hold them accountable these guys could walk out today and get another job making more money. What can I do?"
Read the second sentence again. That is the whole problem, and it is not about sensitivity.
He is not asking how to hold a tech accountable. He knows how. He is asking how to hold a tech accountable while he believes he has no leverage. And a man who believes he has no leverage does one of two things. He says nothing for six weeks. Or he says something that arrives with six weeks of stored pressure behind it.
The tech is not sensitive to feedback.
The tech is sensitive to feedback that arrives with a debt attached.
Four distinctions that do all the work
1. When you tell a man something he already knows, the only thing he receives is your opinion of him.
The tech knows he left the hood up. He heard it hit the ceiling. He knows he was late; he watched the clock in his truck on the way in.
So when the owner "simply points out the error," no information changes hands. The fact was already in the room. The only new thing the tech receives is a verdict on his character, delivered without the word being said.
That is why he shuts down. There is nothing to discuss. He has been informed of your disappointment and dismissed.
The move: never open with the fact. Open with what you don't know.
2. A mistake is an event. Lateness is a decision, repeated.
Shops get this exactly backwards. They discipline the accident and tolerate the pattern.
The bent hood is an event. Events are fixed with systems, not with shame. The right question is what sequence produced it, and what part of that sequence you can change so it cannot happen again to anyone.
Chronic lateness is a decision, made fresh every morning, and it has been ratified by your silence. Decisions are not fixed with systems. They are fixed with agreements and consequences.
Confront the accident to fix the system. Confront the pattern to make an agreement. Never swap them.
3. Feedback is a withdrawal. If you have not made a deposit, it bounces.
There is a generational read on this that is half right. Younger techs may or may not be thinner-skinned. But the truth is that they usually have less tenure, which means less accumulated evidence that you are safe. Your twenty-year guy can absorb a hard word because he has watched you be fair four hundred times. The kid has watched you be fair nine times.
What if sensitivity is not a personality trait? What if you thought about it as an account balance?
The move: if the last three things you said to a tech were corrections, you have no standing to make the fourth one. Fix that first. It takes a week.
4. A tech who goes quiet is not refusing to talk. He is waiting to see whether you will rescue him.
Every owner has done it. The tech drops his eyes, goes silent, and the owner fills the air. "Look, it's not a big deal, just watch it next time." Conversation over. No agreement made. Nothing changed.
Silence worked. So he will use it again.
If you have a tech who reliably shuts down, you probably trained him.
The move: when he goes quiet, you go quiet. Count to ten in your head. The person who breaks the silence gives up the conversation.
The reframe this whole guide rests on
You are not delivering a verdict to a resistant tech.
You are jointly interrogating the gap between what happened and what both of you assumed was true.
That word jointly is not softness. It is the only thing that makes accountability stick, because a man will not enforce an agreement he did not help write.
And the test that you have done it right is uncomfortable:
By the end of the conversation, you have changed your mind about at least one thing.
If you cannot lose, he cannot participate. And a conversation he cannot participate in is not accountability. It is a verdict with extra steps.
Before the conversation: five minutes with a pen
Do not walk in without doing this. Answer in writing, short.
- What is the fact? One sentence. No adjectives. "He was late nine of the last twenty days." Not "he's always late."
- What is at stake? For the shop, for the team, for him. Get to a real number or a real consequence.
- What is my contribution? This is the one everybody skips. Six weeks of silence is a contribution. No written lift procedure is a contribution. Praising speed and then punishing a rushed job is a contribution.
- What do I not know? Write down three things you are assuming and cannot prove.
- What agreement do I want to leave with? If you can't name it, you are not ready to have the conversation. You are ready to complain.
If step 3 comes back empty, you have not looked. Look again.
The opening sixty seconds
Seven moves. Sixty seconds. Do not rush it and do not extend it.
- Name the issue. Once, flat, no adjectives.
- Give one specific example. One. Not five. Five is a case you have been building, and he will hear that.
- Say what you feel. Not to manipulate. Because concealing it is what makes your tone strange, and the strange tone is what he reacts to.
- Say what is at stake. The number. The consequence. Out loud.
- Name your contribution. Real, not performative.
- Say you want to resolve it. Plainly.
- Ask him to respond. Then stop talking.
Then you shut up. Completely. This is the hardest instruction in this document.
Staying in the room
Three things will happen. Have a plan for each.
He gets angry. Good. Anger is participation. Do not match it and do not retreat. "That's fair. Tell me more about that." Anger that gets heard becomes information. Anger that gets punished becomes a resignation in ninety days.
He goes quiet. Count to ten. If he is still quiet: "Take your time. I'd rather sit here than have you tell me what you think I want to hear."
He says "then fire me" or "I'll just leave." This is the moment the owner's fear gets tested. Do not blink and do not threaten. "I don't want that. I want to fix this. But I'm not going to pretend it isn't happening, because that's not fair to you either."
Then keep going. Do not close the conversation until there is an agreement.
Closing: two questions that make it stick
Do not write the agreement for him. He will not enforce your agreement. He will enforce his.
- "What do you think needs to change?" Ask before you offer. If his answer is thinner than yours, add yours. But ask first.
- "How will we both know it's working?" This converts an intention into a measure. A measure both of you named cannot be arbitrary later.
Then say the last part out loud, because it is the part he is silently asking about:
"I'm telling you this because I want you here in five years. If I didn't, I'd just let it slide and replace you."
That sentence is the entire difference between accountability and a warning shot.
Running it: the tech who is chronically late
Your contribution, named honestly: being on time is "no question" a condition of employment. But nobody has said it to this tech, recently, with a number attached. "No question" is the exact phrase that precedes an unspoken expectation. It is official truth. It is not yet ground truth.
Say this:
"I want to talk about start time. Twice this week you were in after 8:15. When you're not here at 8, Danny picks up your first ticket, and I've never once asked him if he minds. That's on me, not you. Here's what I don't know: whether this is something going on at home, or whether 8 o'clock has just stopped meaning 8 o'clock around here. Because I haven't said anything for two months, and silence usually means it's fine. So I'll own that. What's going on?"
Then wait.
Note what is not in there. No "always." No "you're a good tech, but." No list. No tone. Nothing he can dispute, so nothing he has to defend.
If the reason is real, you fix the reason. If there is no reason, you get to the second half:
"Okay. Then here's where I'm stuck. I can't run a schedule I can't count on, and Danny can't either. What do you think needs to change?"
Wait. He proposes. You adjust. Then the measure:
"So the next four weeks, you're in and clocked on by 8. If something comes up, you text me the night before or by 6 a.m. What happens if it doesn't hold?"
Let him say the consequence. He will usually name one harsher than yours. Take his.
Then write it down. Two lines, in an email to him that night. Not a warning. A record of what you both said, so nobody has to remember it under pressure in six weeks.
Running it: the $900 hood
This one is not a discipline problem. Treating it as one is the single most expensive mistake available to you.
Here is a shop owner in this community, describing his second-week junior tech who bent the hood on a new van:
"He walked from the shop into the owner's office and said, do you want my resignation, or do you just want me to go?"
The owner's answer was: what do you mean?
That tech is approaching two years there now. The shop's core value is a picture of a bandaid and the words honest, even when it hurts. Their rule is simple. Mistakes are how you learn. What gets you fired is lying about it, or making the same one twice.
Read that owner's read on it: "if people are not making mistakes, they're either covering something up or they're not learning."
That is the frame. Now the conversation.
Do not open with the hood. He knows about the hood. He has thought about nothing else since it happened.
Say this:
"Walk me through the ninety seconds before you went to shut that hood down."
Then listen for the real answer, which is almost never carelessness. It is a phone call. A rushed ticket. An unfamiliar vehicle. A hood prop that looked like a strut. A helper who moved the car. Somewhere in that ninety seconds is a hole in your shop, not a hole in his character.
Then:
"That's nine hundred dollars. I'm not asking you for it and I'm not writing you up. I'm telling you the number because you deserve to know what it cost, and because I don't ever want to spend it again. So what would have to be true in this shop for that to be impossible?"
Now he is diagnosing. Which is the one thing he is world class at, and the one thing that will make him yours.
Then close it in front of the team, not privately:
"We ate nine hundred dollars on a hood this week. Here's the check we're adding. Nobody's in trouble. If you break something, you tell me. What gets you fired here is hiding it."
You just spent $900 buying a culture where mistakes surface early. That is the cheapest culture anybody has ever bought.
One caution: do not deduct it from his pay. In many states you legally cannot, and I am not a lawyer, so check yours. But the deeper reason is arithmetic. Charging him $900 buys you $900 and costs you a tech, plus the next four techs who hear the story.
About the walkout
"If I hold them accountable these guys could walk out today and get another job making more money."
Some of that is true. Most of it is fear doing math.
Here is what techs actually say when nobody is selling them anything:
"Culture is the number one factor that makes me want to go to work. A learning/teaching environment that nurtures growth and encourages learning from mistakes instead of chastising and belittling."
"People quit managers. Not jobs."
"Sitting down with the techs one on one and having a real conversation peer to peer not boss to employee is going to be the best way to get this problem sorted out."
Techs do not leave shops that hold them accountable. They leave shops where accountability is arbitrary, delayed, and personal. A tech who walks over a fairly conducted conversation was already gone. He just hadn't told you.
And the tech who stays through one of these conversations is more yours afterward than before. Because you did the thing almost no owner does. You told him the truth, you took your share of it, and you did not make him small.
The reusable version
Tape this to the inside of your office door. It works for a late tech, a bent hood, a service advisor discounting jobs, a partner who won't answer email.
- What is the fact? One sentence, no adjectives.
- What is my contribution? Find it before you walk in.
- What do I not know? Ask that first, not the fact.
- Say the stake and the number. Out loud, once.
- Then stop talking. Let the silence do the work.
- Ask what needs to change. Before you say what needs to change.
- Agree on the measure. How will we both know it's working?
- Change your mind about one thing. If you didn't, it wasn't a conversation.
- Put it in writing that night. Two lines.
- Tell him why you bothered. Because you want him here in five years.
What The Technician hears
Run any version of this past a good tech before you use it. Here is what he is listening for.
He hears whether the fact came before the question. Fact first means verdict. Question first means conversation.
He hears whether you took any of it. If you took none of it, you are not correcting him. You are ranking him.
He hears whether you said the number. Vague costs mean the cost is his reputation. A real number means the cost is a real number.
He hears whether the same rule applies to the guy who has been there twelve years. If it doesn't, nothing else you said matters.
And he hears whether you would have said any of it if you weren't afraid he'd leave.
That last one is the whole game. He can tell. He has always been able to tell.
3
0 comments
How to hold a tech accountable without losing him
skool.com/technicianfind
Proven templates, strategies, training and top-level networking to help independent auto repair shops hire quality staff faster.
Leaderboard (30-day)
1
+3
2
+3
3
+2
4
+2
5
+1
Powered by