Giving Feedback That Doesn't Blow Up

Why this matters

Most owners are bad at feedback in one of two directions. They avoid it until they are furious and then explode, or they soften it into mush the tech does not even register as criticism. Both fail. The avoided feedback festers and the crew never improves, the explosive feedback gets you a defensive, resentful tech who tunes you out. Good feedback is a learnable procedure, not a personality trait. Run it the same way every time and you can correct a problem without making an enemy, which is the whole job. This is the sequence.

Step 1: Decide if it even needs a sit-down

Not every correction needs a formal conversation. Sort first.

• A small, in-the-moment fix gets handled in the moment, lightly. "Hey, snug that fitting another quarter turn." No meeting required, and making one is overkill that puts people on edge.
• A pattern, a safety issue, or anything emotional gets a real, private conversation. If it has happened more than once, or it could hurt someone, or you are angry about it, it earns a sit-down.

Using a sledgehammer on a small thing trains the crew to dread you. Using a hint on a real problem means it never changes. Match the weight of the response to the weight of the issue.

Step 2: Cool down first, then prepare

Never give feedback hot. Feedback delivered in anger is about your emotion, not their improvement, and they will hear the anger and miss the lesson. Wait until you can talk about it flat. Then prepare three things:

• The specific behavior, observable, not a character judgment. "The last two invoices went out with the wrong totals," not "you are careless."
• The impact, why it matters. "The customer called confused and it cost us trust."
• The change you want, concrete. "Double-check the totals against the line items before you send."

If you cannot name a specific behavior, you are not ready, you are just annoyed, and you should wait until you have the facts.

Step 3: Pick the right place and time

Praise in public, correct in private. This is not optional. Correcting a tech in front of the crew or a customer guarantees defensiveness, because now they are protecting their standing in front of an audience, not listening to you.

• Private, away from the crew, the customer, and the radio.
• Soon, while the event is fresh, but not in the heat of it. Same day or next, not three weeks later when they have forgotten.
• Unhurried. A correction squeezed into thirty seconds between jobs reads as an ambush.

Step 4: Lead with the specific, skip the fake sandwich

The old "compliment, criticism, compliment" sandwich is mostly dead for a reason: people learn the pattern and discount the bread to brace for the meat. Be more direct and more respectful than that.

1. Name the topic plainly. "I want to talk about the invoices from this week."
2. State the specific behavior and the impact, calmly, without the character attack. Facts, not adjectives.
3. Then stop talking and let them respond. This is the step everyone skips. You are not delivering a verdict, you are opening a conversation.

You can absolutely acknowledge what they do well, genuinely, when it is true. What you avoid is the formulaic compliment that exists only to cushion the blow, because everyone sees through it.

Step 5: Listen for the reason

When you pause, you often learn something that changes the whole conversation. Maybe the invoices were wrong because nobody showed them the system, or because the source data they were given was bad. Feedback is a two-way diagnosis, not a one-way download.

• If there is a real cause you missed, the conversation pivots to fixing that, and you just avoided unfairly blaming someone.
• If they get defensive, do not match it. Acknowledge the feeling, hold the fact: "I hear that it has been a hectic week. The totals still have to be right before they go out."
• If they own it, you are basically done, move to the fix.

Step 6: Agree on the change and the follow-up

Feedback that ends with feelings and no plan changes nothing. Close the loop:

• Confirm the specific change out loud, so you both heard the same thing.
• Offer the support if there is a skill gap underneath. "Let me walk you through the check once so it is faster."
• Name a checkpoint if it is a pattern. "Let us touch base in two weeks and make sure it is sticking." A follow-up tells them this was real and you will notice.

Step 7: Let it go once it is handled

When the conversation is done and the behavior is corrected, it is over. Do not bring it up again, do not hold it over them, do not mention it to the crew. A tech who fixes the thing and then gets reminded of it for months learns that owning a mistake here is a trap, and they will stop owning the next one. Clean feedback has a clean ending.

The shape to remember

Specific behavior, real impact, then listen, then a concrete change, then drop it. Run that same shape on a wrong invoice, a missed callback, or a sloppy install, and feedback stops being a fight you avoid and becomes a normal part of running a good crew. The techs who get clean, fair, specific feedback are the ones who get better. The ones who get silence or explosions are the ones who leave.

References

• Trade-standard practice for coaching and performance feedback
• See related: Receiving Criticism as a Lead, Conducting Performance Reviews
• See related: The Carried Underperformer, Callbacks From One Tech: Coaching