Give the hard feedback while the problem is still small

Say you've got a service tech who's been leaving job sites sloppy. Nothing catastrophic. Wrappers in the driveway, a return call two weeks later for a fitting he didn't torque down. You notice it in March. You mention it, sort of, in a way that lets both of you pretend it wasn't a correction. Then you notice it again in April, and May, and by June you're rehearsing a speech in the truck because a customer left a review that cost you the referral chain out of an entire neighborhood.

That June conversation is brutal. The March one would have taken ninety seconds.

That's the whole game. Hard feedback doesn't wreck morale. Late feedback wrecks morale, because by the time you deliver it you're not correcting a behavior anymore, you're unloading six months of stored-up frustration on a guy who thought everything was fine. He's not hearing coaching. He's hearing an ambush.

The cost of waiting has a shape

Every week you sit on it, three things get worse.

The problem compounds. Whatever he's doing wrong, he's now done it forty more times and built a habit around it. You've also taught him it's acceptable, because you watched it and said nothing. When you finally object, you're reversing a rule you enforced by silence.

And your own tone degrades. Feedback given at week one sounds like information. Feedback given at week twenty sounds like a verdict. Same words, completely different temperature, because by then you've got a case file and he can hear it.

The operators who are good at this aren't blunter than you. They're just faster.

Set the room before you set the tone

Never in front of the crew. Never in a group text. Never over Slack, where you can't hear the pause on the other end and he can reread your sentence nineteen times at 11 p.m.

Face to face if you're in the same building. Phone or video if you're not. Not email, ever, for the first pass. Email is for the summary afterward.

Don't do it Friday at 4:50. He'll stew all weekend with nowhere to put it and no chance to fix anything. Tuesday morning is the best slot in the week. He's got four working days to show you a different version of himself, and you've got four days to notice.

One more thing on setup: don't schedule a fifteen-minute "quick chat" with no agenda. That's the meeting everybody assumes is a firing. Tell him the subject in the invite. "Want to go over how the Halstead job closed out." He shows up prepared instead of terrified.

Say the thing in the first fifteen seconds

Open with the correction. Not the weather, not the pleasantries, not a warm-up compliment you don't mean.

"The last three installs came back with callbacks. I need to talk about why."

That's it. Say it and stop. The silence afterward is uncomfortable and you should let it sit there, because that silence is where he starts thinking instead of bracing.

What kills this is the wind-up. Two minutes of "so, how's the family, listen, you know I think the world of you" and he already knows something bad is coming, he just doesn't know what, so he spends your entire preamble running through every possible sin. By the time you get to the actual point he's exhausted and defensive.

The compliment sandwich has one legitimate use: somebody genuinely fragile who's about to hear something big, once. Use it more than that and your praise becomes worthless. People start flinching every time you tell them they did a good job, because they've learned the "but" is coming.

Describe the behavior, never the man

"You were careless on that job" is an argument. "The union wasn't torqued and the customer called Tuesday" is a fact.

He can dispute the first one forever. He can't dispute the second one, and more importantly, he doesn't have to defend his character to talk about it. You've given him a way to agree with you without admitting he's a bad person. That's not softness, it's engineering. You want the fastest available route to him fixing it.

Bring the specifics. Dates, job numbers, the actual thing the customer said. Vague feedback is the cruelest kind, because he can't act on it. "Your attitude's been off" gives a man nothing to work with except anxiety. "You cut me off twice in the Thursday meeting and rolled your eyes when Dana was talking" gives him something he can stop doing tomorrow.

If you can't name the specific instance, you're not ready to have the conversation. Go get one.

Then shut up and let him answer

Ask, and mean it: "What's going on?"

Sometimes the answer reframes everything. His truck's been down and he's borrowing a van with no shelving. He's covering two routes because you never backfilled the guy who quit in February. His mother's in hospice and he hasn't told anybody.

None of that makes the callbacks acceptable. All of it changes what you do next.

And sometimes there's no reason, and he knows it, and he says so. That's the best version. Take it and move on. Don't make him grovel. The moment a man admits fault, your job switches from prosecution to planning, immediately.

Land on a specific, checkable thing

The conversation isn't over when he understands. It's over when you both know what changes and when you'll look at it again.

Not "be more careful." Something you could verify with your own eyes: photo of every completed connection before he leaves the site, texted to dispatch, starting Monday. Two weeks. Then you check.

Put three lines in an email afterward. What you talked about, what he agreed to do, when you'll review it. No lecture, no restating the disappointment. It's a record, and it's a kindness, because six weeks from now neither of you will remember the details the same way.

Say plainly which conversation this is

This is where most managers create the damage they were trying to avoid.

There's coaching, and there's a warning, and they're not the same conversation. Coaching means you expect him to keep working here for years and you're investing in him. A warning means his job is genuinely at risk.

Tell him which one it is. Out loud. "This is coaching, you're not in trouble" or "I need you to understand this is serious and it can't happen again." When you leave that ambiguous, everybody assumes the worse one, and the guy goes home and tells his wife he thinks he's getting fired over a driveway full of wrappers.

Softening a real warning until it sounds like coaching is worse. He walks out relieved, changes nothing, and gets blindsided in September by a termination he had no warning was coming. That's the failure people mean when they say a manager blindsided them. It usually wasn't malice. It was a boss who couldn't stand to be disliked for eleven minutes.

What actually tanks morale

Not hardness. Inconsistency.

Crews can take a demanding boss. What they can't take is a boss who chews out the new kid for a mistake the senior guy makes weekly. Or one who's ice-cold in March and generous in April depending on the bank balance. Or one who corrects in public and praises in private, which is exactly backwards.

Correct in private. Praise where people can hear it. Hold the top performer to the same standard as the bottom one, especially the top performer, because everybody's watching whether that's true.

And when he fixes it, say so. Not a ceremony. Just, "Those last four closed clean. Noticed." Ten seconds, and it does more for a crew than any offsite you'll ever pay for.

The manager everybody respects isn't the nice one. It's the one you never have to guess about.