The Performance Conversation That Changes Behavior
Why this matters
Most correction conversations fail in a predictable way: the owner is vague to avoid conflict, the tech nods, nothing changes, and three weeks later the owner is angrier and the tech is blindsided when it escalates. A performance conversation that actually changes behavior is not softer or harder than that, it is more precise. It names one thing, ties it to a real effect, and ends with a change both people agreed to out loud. This is the single most leveraged fifteen minutes a manager spends, and it is a skill, not a personality trait. Here is the shape that lands.
Have it now, and have it privately
Two settings kill a correction before you open your mouth. The first is delay. A conversation about a thing that happened two months ago reads as an ambush, and you have taught the tech that the standard did not matter until suddenly it did. Have it within a day or two of what you saw. The second is an audience. Correcting a tech in front of the crew or a customer turns a coaching moment into a humiliation, and they will spend the whole conversation defending their pride instead of hearing you. Private, prompt, and calm is the container. Get that wrong and the content does not matter.
Name one behavior, not a pile
Walking in with a list of six grievances guarantees the tech hears none of them and feels attacked by all of them. Pick the one that matters most and lead with it. If there are genuinely several, the biggest one earns this conversation and the rest wait. One clear correction that changes a behavior beats a comprehensive list that changes nothing.
And name a behavior, not a character trait. "You have a bad attitude" is a verdict a person can only argue with. "You cut off the customer twice on the Reyes call and walked out before answering her question" is a fact they can only work with. The more specific and observable, the less room to deflect.
Connect it to an effect they can feel
A behavior with no stated consequence sounds like a preference, and people do not change for a preference. Close the gap between what they did and why it matters, in one line:
- "When the paperwork comes in blank, the office cannot bill it, and you do not get paid on time either."
- "When you skip the walkthrough, we eat the callback, and the customer stops trusting us."
The effect makes the standard feel real instead of arbitrary. Tie it to the customer, the crew, the shop, or the tech's own paycheck, whatever is truest.
Then stop talking and listen for the cause
This is the step most managers skip, and it is where the conversation earns its keep. After you have named the behavior and its effect, ask what is going on and go quiet. Real silence, not a half-second before you keep lecturing. A drop in performance often has a root you cannot see from the outside: a tool that keeps failing, a process that does not work, a home situation, a resentment you never heard. Sometimes fixing the cause fixes the behavior on the spot, and you walk out having solved a problem instead of issued a warning. You will never hear the cause if you do all the talking.
State the standard and the consequence plainly
Once you both understand the situation, be explicit about three things, with no fog:
- What you need instead, stated as an observable behavior.
- By when you need to see it.
- What happens if it does not change. You do not have to threaten. You do have to be honest that this is a real line and not a suggestion.
People cannot hit a bar you will not state. Vagueness here feels kinder in the room and is crueler over time, because it sets the tech up to fail a test they were never clearly given.
Get it back in their words and close the loop
End by having the tech restate what they are going to do differently, in their own words, not just a "yeah, got it." "So going forward, what does this look like on your next call?" This surfaces a misunderstanding while it is still free, and it converts a lecture into an agreement. Then write a short note for yourself: date, what you discussed, what you both agreed to. Not to build a case, to make the next conversation reference this one instead of starting over.
The tone to hold
The stance that works is not soft and not harsh. It is "I think you are better than this, and I am telling you straight because I would rather fix it than replace you." Techs can tell the difference between a manager protecting the shop and one venting frustration. The first one they respect and respond to. The second one they wait out. Come in believing the person can change, be specific enough that they know exactly what to do, and honest enough that they know it matters. That combination is what turns a conversation into a behavior.
References
- Society for Human Resource Management (SHRM), delivering effective performance feedback
- U.S. Small Business Administration (SBA), managing employee performance
- See related: Setting Expectations a Tech Can Actually Be Held To; Coaching a Struggling Employee Back to Standard