Why does your team keep getting it wrong when you were clear?

Your team keeps getting it wrong because clarity is measured at the receiving end, not the sending end. You know what you meant, so the sentence sounded complete when you said it. The only real test is what people did next, and if three of them walked out of the same conversation with three different plans, the direction was not clear no matter how carefully you worded it.

I spent twenty seven years in packaging and manufacturing operations, technician to supervisor to a vice president who also carried human resources, and almost every problem that reached my desk as a people problem started as a clarity problem. Somebody was doing exactly what they thought they had been asked to do.

Why does "I was clear" fail as a test?

Because you are grading your own work against information nobody else has.

You were in the meeting where the decision was made. You know which customer is behind it, what happens if it slips, and which of the three competing jobs actually matters this week. When you give the instruction, your brain fills all of that in silently and the sentence feels finished. Your supervisor hears the sentence without any of the context, then has to guess at the missing parts on a busy floor with the phone ringing.

The second reason is that people almost never tell you they are confused. Admitting you did not follow the boss carries a cost, and the safer move is to walk away, do your best interpretation, and hope it lands. That is not a bad team. That is a normal team.

What is it actually costing you?

The bill shows up somewhere other than the conversation, which is why it rarely gets traced back.

It costs you rework, because the job gets done to the wrong standard and then done again. It costs you speed, because your people slow down and wait for you to be available rather than risk guessing twice. It costs you judgment, because a team that has been corrected for an honest interpretation learns to do nothing without you. And eventually it costs you the truth, because once people learn that a clarifying question reads as not paying attention, they stop asking and start covering.

The most expensive version is the quiet one. Nothing blows up. The line just runs a little wide of where you thought it was pointed, for months.

What is actually missing from most instructions?

Four things, and most directions carry only the first.

1. What done looks like. Not the task, the finished state. "Run the changeover" is a task. "The line is running the new spec at full rate with the first article approved" is a finished state, and somebody other than you can check it.
2. When, stated as a time and not as a feeling. "As soon as you can" is not a deadline, it is a mood. Give a time, then ask straight away whether it is realistic. You would rather hear no on Monday than find out on Thursday.
3. What it beats. Priority only means something in relation to something else. If you have called four things a priority this week, you have not set priorities, you have handed the decision to whoever is under the most pressure at the time.
4. Who decides when reality changes. Reality always changes. Say in advance what they handle themselves and what has to come to you, and be specific enough that they do not have to judge whether this counts as important.

The fourth one is what saves your weekends. A supervisor who knows exactly where their authority ends stops calling you about everything and stops calling you about nothing, which are the two failure modes and they come from the same gap.

What does the gap look like in practice?

Here is the pattern I see most often on a floor, with the version that actually travels.

None of the left column is bad management. All of it is normal, and all of it sounds perfectly clear coming out of your own mouth.

Why does the same instruction land differently on different people?

Because people take information in differently, and most of us give a direction the way we would want to receive it.

One supervisor wants the headline and starts moving before you have finished the sentence, so the detail at the end never arrives. Another cannot start until the specification is complete, and reads a loose instruction as a sign the plan is not ready. A third will agree in the room to avoid friction and raise the real concern later, or never. A fourth catches the energy in your voice and remembers the enthusiasm rather than the date.

All four of those are people doing their best with the same forty seconds. Adapting how you deliver the message is not softening it, it is the difference between saying something and being understood. That is the work I do with DISC, which helps answer two questions every leader eventually asks: why do I respond the way I do, and why do they respond so differently? As I tell the leaders I coach, you can't intentionally change a behavior you don't recognize.

How do you check that it landed?

Not by asking "any questions?" Nobody has ever said yes to that on a plant floor.

Ask them to tell you back. "Just so I know I explained it properly, what are you going to do first?" That phrasing matters, because it puts the burden on your explanation rather than on their attention, which makes it safe to be honest. You will find the gap in about ten seconds, and those ten seconds are the cheapest part of the whole exchange.

Then look at the second signal, which is what they actually did. If a supervisor came back with something adjacent to what you asked for, resist the urge to correct the person and go back and read your own instruction first. Most of the time it is genuinely in there, and you can see the exact sentence they built their version out of.

And write down anything that has to survive a shift change. If it only exists in a conversation you had at seven in the morning, it does not exist for the crew coming in at three.

Can you be too specific?

Yes, and this is where clear leaders overcorrect into micromanagement.

Be precise about the outcome and the boundary, and loose about the method. The moment you specify every step you have taken the thinking back, and you get exactly what you asked for and nothing more. You also lose the improvement, because the person doing the job daily knows things about it that you do not.

The test I use is simple. If I am specifying how, I should be able to say why that particular how matters, usually safety, a spec, or a regulatory requirement. If I cannot, I am specifying it out of habit or anxiety, and I should give them the outcome and get out of the way.

Common questions

How do I tell a clarity problem from a performance problem? Look at whether the misses are consistent. If different people miss the same instruction in different ways, that is clarity. If one person misses instructions everyone else follows, that is a performance conversation, and it will be a much fairer one once you are certain the direction was solid.

Does this mean I have to write everything down? No. Write down what has to survive time and handoffs, which is usually deadlines, standards and the boundary of somebody's authority. The rest can live in conversation. The rule of thumb is that if you would be annoyed to find it had been forgotten, it should not be stored in somebody's memory.

My team says they understand and then they do not. What do I do? Stop asking whether they understand and start asking what they are going to do. Understanding is a feeling, and people will report it honestly and still be wrong. A plan is checkable, and the gap surfaces immediately.

Is repeating myself the answer? Repetition helps with priority and does nothing for ambiguity. If the message was unclear, saying it three more times produces three more interpretations. Change the message, then repeat the version that works.

Most of the leaders I work with are not unclear people. They are experienced people carrying context their teams cannot see, which is a different problem and a fixable one. If that sounds familiar, read more about Executive & Performance Coaching or book a free consultation.