You gave clear direction to your team. And what came back was late, half-done, or just a mess.
And then you probably did what a lot of good leaders do in that situation. You sighed, and you fixed it. You told yourself it was faster this way. You probably also felt that low hum of frustration: Why do I have to spell out every little thing? Why can’t they just do the job?
That irritation is real. It’s frustrating to feel like the quality bar only holds because you’re personally holding it up.
Most of the time, “they just won’t do it” isn’t a people problem. It’s a clarity problem.
The gap you can’t see
When a manager says “handle the loads today,” they usually have a full picture in their head—the right product to the right customer, correct weight, scale ticket completed and matched to the order, staged in delivery order, out the door by 2:00.
The employee heard three words: handle the loads.
What feels like non-compliance is often the distance between what you pictured and what you said out loud.
Erin has the perfect example, and if you have kids, you will probably relate. You tell your kids to clean their room. You come back an hour later and the floor is technically walkable, and you are frustrated. Their definition of “clean room” and your definition of “clean room” were not the same. To them, clean means the clothes are off the floor. To you, it means the bed is made, the hamper is empty, and the floor is vacuumed. You never agreed on what the finished thing looks like.
“But this should be common sense”
Here’s the thought that’s probably surfacing right now: Some of this shouldn’t need saying at all. When you use a tool, you put it back. When you finish with equipment, you clean it and return it. That’s not a task, that’s common sense. Having to spell it out feels almost insulting to you and to them.
It feels like common sense to you because of years of experience and a standard you’ve carried so long you’ve stopped noticing you have it. What’s obvious to you is invisible to someone who was never taught it, never saw it modeled, or simply sees it differently than you do.
It’s hard to hold someone to a standard you never stated. “Common sense” is unenforceable. When you get frustrated that they didn’t meet it, you’re holding them to a rule that lives in your head. “Stated” is something else entirely. Saying the obvious thing one time is a small price to pay for having the work done the way it needs to be done.
It shows up in the finishing standard, too. Ask someone to clean out a bin and you mean empty—every last bit out. They get most of it out, look at it, and call it done. To them, it’s done. “Most of it” is clean. To you, “most of it” is half a job. Neither of you is wrong about the word; you just never agreed on where “done” looks like. That gap between your finished and their finished is where the frustration lives.
Step One: get specific about what “done” looks like
Don’t just assign the task. Describe the finished product.
Instead of “handle the loads today,” it’s: “I need the three loads out by 2:00 p.m., each one weighed and the ticket matched to the order before it leaves the scale.”
Notice what that does. It names what, by when, to what standard, and what success looks like when it’s finished. You’ve closed the gap between the picture in your head and the picture in theirs.
A useful gut check before you hand something off: Could someone who isn’t me tell whether this was done right? If the answer is no, you haven’t defined success, you’ve defined the task.
Step Two: Say the words “I expect”
This one is small and it is powerful.
Even when we’re being direct, we often stop short of naming the direction as an expectation. “Can you get those loads out by 2:00?” “Let’s try to have those loads ready by two.” “Those loads need to go out today.” All of these are clearer than “handle the loads”; none of them plainly tells the person this is what I’m holding you to.
“I expect” removes the guesswork: “I expect the three loads out by 2:00, each ticket matched to the order before it leaves the scale.”
“I expect” isn’t harsh. It’s honest. It tells the person it matters, it’s not a suggestion, and you’re going to hold them to it. People appreciate that clarity far more than they appreciate guessing at how serious you really were.
“I expect” only carries the weight you’ve backed up. If the last ten times the loads went out at 3:00 and nothing was ever said, your team has learned that 2:00 really means “whenever you get it done.” Say “I expect them out by 2:00” now and they hear the same soft 2:00 they’ve always heard. That’s not defiance, it’s your people reading the pattern accurately.
When it misses
Sometimes you’ll do both steps and the work still comes back half-done. It happens, that’s reality. What you do in that moment is what turns a stated expectation into a real one. The mistake is letting it slide “just this once.” Every time you quietly absorb the miss and do it yourself, you’re not avoiding the problem, you’re teaching it. You are showing your team that you’ll cover the gap.
Follow up…. every time. Not harshly, consistently. A miss you address once and then let go the next three times teaches the expectation is soft again, and you’re back where you started. Consistency is the whole game here: it’s the difference between an expectation people have learned to take seriously and one they’ve learned they can wait out.
When you do address it, be clear about three things: the Behavior you saw, the Impact it had, and what you want Tomorrow.
“A load went out with the ticket unmatched to the order (behavior). The customer received the wrong product, and I spent the afternoon untangling it and we have to return to deliver the correct product and retrieve the wrong product (impact). Going forward, I expect every ticket is matched to the order before the truck leaves the scale, and anything that looks off held until you’ve checked with me (tomorrow).”
Specific, not personal.
The payoff
Here’s what makes this worth the effort. Every time you quietly fix someone’s work instead of clarifying and holding the line, you teach them two things: that you’ll catch it, and that the real standard is whatever you’ll tolerate. You are making a short term correction, you are signing up to keep doing it.
Getting specific about what success looks like and saying “I expect” out loud does the opposite. It hands the work back to where it belongs, it gives your team a real shot at getting it right, and it slowly gets you out of the weeds you never should have been in.
The frustration you’re feeling is a signal. Most of the time, it’s not telling you your people don’t care. It’s telling you the picture in your head never made it to theirs, and that’s the most fixable problem there is.