Your Team Shouldn't Have to Guess What You Mean
"That's not what I meant."
Have you ever said that after someone on your team finished something you asked them to do?
Maybe they misunderstood the assignment. Maybe they focused on the wrong thing. Maybe they spent hours building something when you expected a quick summary. Or maybe Friday afternoon arrived and you discovered that when you said, "I need this by Friday," they heard something very different from what you meant.
It's easy to look at the result and think, How did they not understand what I wanted?
But there's another question worth asking:
How clear was I about what I wanted?
You Know More Than You Think You Said
As the manager, you usually have more information than the person you're talking to.
You know why the work matters. You know what your boss is expecting. You know what happened the last time this came up. You know whether the deadline is firm or flexible. You know what other projects are competing for attention. And you probably have a pretty good picture in your head of what the finished product should look like.
The problem is that much of that information is still in your head.
Psychologists call this the curse of knowledge. In a well-known Stanford study, people tapped out the rhythm of familiar songs like "Happy Birthday" and predicted listeners would name about half of them. The listeners got roughly 1 in 40. The tappers could hear the tune in their heads. The listeners just heard knocking.
Managers do a lot of knocking.
You say, "Can you pull those numbers together for me by Friday?"
Seems clear enough.
But which numbers? How much detail do you need? What are you going to do with them? Is Friday morning okay, or do you mean end of day? Is this more important than the other project you asked them to finish this week?
You know the answers.
Do they?
Clear communication isn't just giving someone an instruction. It's making sure they have enough information to act on it.
Give People What They Need to Succeed
Before you hand something off, run through four quick questions:
Outcome: What do you need, and what does "done" look like?
Context: Why does this matter? Who will use it? What happens next?
Priority: Where does this fall compared with everything else on their plate?
Follow-through: When will you reconnect, and when should they come back to you if they hit a problem?
“Clear is kind. Unclear is unkind.”
Here's what that looks like with those Friday numbers.
Before: "Can you pull those numbers together for me by Friday?"
After: "Can you pull Q3 sales by region? Just the totals, no deep analysis. I'm using them in my update to leadership on Monday, so I need them by Friday at noon. This comes ahead of the vendor report, which can slide to next week. Let's check in Thursday morning, but ping me sooner if the regional data's a mess."
The second version takes about 30 seconds longer. It doesn't require a meeting, a slide deck, or a project charter. But those 30 seconds can save hours of rework, frustration, and "that's not what I meant" later.
"ASAP" Is Not a Priority System
One of the easiest ways to create confusion is to make everything sound urgent.
"I need this as soon as possible."
"Can you make this a priority?"
"I really need this by tomorrow."
Meanwhile, the person you're talking to is already working on the three other things you told them were priorities.
Now they have to figure out which priority is actually the priority.
When you hand someone something new, don't assume they know where it fits. If it needs to jump to the top of the list, say so. Just as important, tell them what moves down:
"This goes to the top. The budget review can wait until Tuesday."
Otherwise, you're asking them to guess. And they will usually guess wrong, because they're working with half the information you have.
Don't Make Your Team Decode You
The guessing doesn't stop with assignments.
Is this a suggestion or a direction?
Do you want me to make the decision, or do you want to approve it?
When you said, "You might want to take another look at this," did you mean I should actually change it?
Are you asking because you're curious, or because you think I did something wrong?
When people have to keep interpreting what their manager really means, it creates unnecessary work. Some people will make their best guess and move forward. Others will stall because they're worried about getting it wrong.
Both cost you time.
A simple fix is to label which mode you're in:
"This is just a thought. Take it or leave it."
"This one's your call."
"I need to sign off before this goes out."
Your team shouldn't have to become experts at reading between your lines.
Clarity Isn't Micromanagement
Some managers hold back on being specific because they don't want to micromanage.
But there's a difference between telling someone exactly how to do the work and making sure they understand what you need.
You can be clear about the outcome, the boundaries, the priority, and the deadline without controlling every step along the way.
In fact, clarity gives people more freedom. When someone understands what success looks like, they have more room to decide how to get there.
That's not micromanagement. That's setting them up to succeed.
It's also why Clarity comes first in my Clarity → Confidence → Credibility framework. Your team can't act confidently on something they had to guess at, and you can't build credibility as a leader when people are never quite sure what you meant.
Your Turn
Reflect: Think about something you asked someone on your team to do this week. Were you as clear as you thought you were?
Assess: Rate yourself from 1 to 10 on each of the four: outcome, context, priority, and follow-through. Which one scored lowest?
Engage: Pick one current assignment and check in. Instead of asking, "Does that make sense?" ask, "Walk me through how you're thinking about this." Then choose one thing you'll do differently to move your lowest score up a point.
Because "That's not what I meant" shouldn't be a regular part of your vocabulary.
Leave me a comment on how this exercise went.
