User
Write something
EasyBench Live: Weekly Clinic is happening in 48 hours
How to hold a tech accountable without losing him
This is the practical working guide I used to write the previous story post: https://www.skool.com/technicianfind/he-said-nothing-wrong-the-tech-hasnt-spoken-to-him-since 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.
3
0
How to hold a tech accountable without losing him
He Said Nothing Wrong. The Tech Hasn't Spoken to Him Since.
Second week on the job, a junior tech went to close the hood on a brand new van. He thought it had struts. It had a prop. He bent it. Then he walked off the shop floor, into the owner's office, and said this. "Do you want my resignation? Or do you just want me to go?" The owner looked at him. "What do you mean?" Hold that. We are coming back to it, and it is not the story you think it is. Different shop. Different hood. A tech raises a full-size SUV on the lift with the hood still open. The hood hits the ceiling. Nine hundred dollars in damage. Nobody is arguing about what happened. Technician error, start to finish. He had several years in that building. The owner said this: "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?" So he talked to the tech. He pointed out the error. Calmly. No yelling. Every word of it true. That was three days ago. The tech has barely spoken since. You have done this. You were level. You did not raise your voice. You had the facts on your side. And the guy went cold on you anyway. Now you are walking on eggshells in a building you own. You are managing a mood instead of running a shop. You are doing it while you are already a man down. And a sentence has started forming in the back of your head. These guys can't take anything. Before you finish that sentence, answer this one. Why does a calm, accurate, factual statement make a grown man go silent? Because he already knew. He heard the hood hit. He stood there while somebody went for a ladder. He has run it back in his head every night for three days. When you pointed out the error, nothing crossed the room. Not one piece of information. When you tell a man something he already knows, the only thing he receives is your opinion of him. A channel with nothing in it does not stay empty. It fills with whatever else is available.
3
0
He Said Nothing Wrong. The Tech Hasn't Spoken to Him Since.
You Don't Have an Applicant Quality Problem
There, I said it! The applicants aren't usually the problem. I know that isn't what you want to hear. But nearly every time an owner tells me the candidates are garbage, we find out nobody ever opened them or at least never reviewed and processed them correctly. I've written about this before. I'm writing about it again because I watched it happen twice in the last two weeks. Two shops, both ready to blow up a campaign that was working fine. This one keeps costing people hires. So we're going to cover it again. Here's how it sounds when it starts. "Nobody qualified is applying." "No one wants to do this kind of work anymore." "I've exhausted all other options and I don't know what else to do." So the ad gets changed. Then changed again. Then the pay goes up. Then the town takes the blame. Sit with this one for a second. "Nobody good is applying" is a check engine light. It is not a diagnosis. You would never quote a customer a repair based on how he described the noise over the phone. You'd get hands on the vehicle. You'd pull codes. You'd watch live data. You'd verify before you replaced a part. Hiring is the one system in your building where you accept the phone call description and start throwing parts at it. WHERE IT ACTUALLY BREAKS Most owners are judging applicant quality from email notifications. The automatic ones. A name. Maybe a resume snippet. Often nothing you could make a decision from. The notification is a window. The account is the shop floor. You are standing in the parking lot deciding whether the bay is clean. Last month an owner told me his campaign was dead. Nothing coming in. Ready to pull it. @Christi Warren on my team got on a screen share and opened the account with him on the phone. Twenty-two applications he had never opened. Three he would have hired. Now here is the part that stings, and it's the reason I keep writing about this. The owner usually isn't the one reviewing. He handed it to a manager. A service advisor. His wife. Somebody who has forty other things on the list.
You Don't Have an Applicant Quality Problem
Your techs clam up in one-on-ones. That silence is worse than the complaining.
A shop owner told me this last week. "My techs complain when we're slow." "When we're busy, they complain the advisors are selling too much work." "And when I sit them down one-on-one, they clam up. Don't give me anything I can use." Then he said the line I hear from almost every owner sooner or later. "These guys are never happy." Here's what I told him. None of those three things are the real problem. This isn't a communication problem. It's a translation problem. Your techs are talking. Constantly. You're listening for the wrong language. Managers communicate in solutions. "Here's the issue, here's what I need." Techs communicate in observations. "We're slow." "They're selling too much." You're waiting for a work order. He's handing you a symptom. The complaint is almost never about the complaint. "We're slow" rarely means "I'm bored." It means "I'm watching my paycheck shrink and starting to wonder if I should look around." "The advisors are selling too much" rarely means "sell less work." Read that one twice. It costs owners good techs every year. A good tech almost never wants less work. He wants less chaos. "Selling too much" means "I'm getting rushed. I don't have time to diagnose it right. My name's going on this repair and quality's slipping." You want the wrench in his hand. He's telling you the wrench keeps getting yanked out of it. Same words. Different message. Now the part quietly wrecking your one-on-ones. You're asking the wrong question. "What can I do better?" "What do you guys want?" "What are your concerns?" Those questions ask a tech to diagnose your management. That's not how his brain is wired. Put a car in front of him with a pull to the left and he'll find it in ten minutes. Ask him to diagnose your leadership and you get "everything's fine." Techs diagnose systems. So hand him a system to diagnose. "What slowed you down this week?" "What job ate your lunch?" "Where are we wasting the most time?" "If you ran this place for one day, what's the first thing you'd fix?"
4
0
Your techs clam up in one-on-ones. That silence is worse than the complaining.
Happy Birthday America!
Wow, 250 years! I hope everyone is having an amazing day of celebration.
3
0
Happy Birthday America!
1-30 of 445
Technician Find Community
skool.com/technicianfind
Proven templates, strategies, training and top-level networking to help independent auto repair shops hire quality staff faster.
Leaderboard (30-day)
Powered by