Team Performance Problems Are Communication Problems

You give a directive. It seems clear to you. You’ve thought about it. You’ve decided what needs to happen. You communicate it in a meeting, send an email, mention it in passing.

Two weeks later, the work comes back and it’s not what you asked for. Your frustration spikes. Your team obviously didn’t listen. They obviously don’t care. They’re incompetent.

Except they’re not. They understood something completely different than what you thought you communicated. And now you’re both frustrated because you think it’s a competence problem when it’s actually a communication problem.

This is one of the most common patterns I see in struggling organizations. The leader assumes people understand. The team is confused but afraid to ask. Work gets done wrong. People get blamed. Trust erodes. And the real problem — clarity — never gets addressed.

The Clarity Gap

Here’s what’s true: when you’ve been thinking about something for days or weeks, it’s obvious to you. You understand the context. You know why it matters. You can picture the end result. All the pieces fit together in your mind.

Your team hasn’t been thinking about it. They’re in the middle of five other things. They got a message that sounded something like: “We need to do X.” And they interpreted it based on their context, their experience, what they’ve heard before.

The gap between what’s clear in your head and what’s clear to them is enormous. And most leaders don’t account for it.

I worked with a VP who wanted to implement a new customer feedback process. She thought it was obvious. Get customer feedback, compile it, share it weekly. Simple. But the team interpreted it differently. Some thought they should survey all customers. Some thought they should call the biggest customers. Some didn’t know what “feedback” meant — the positive stuff or the problems?

The first week was chaos. People working at cross purposes. Results that made no sense. The VP was furious. She thought the team was incompetent. The team was exhausted and confused. None of them were right or wrong. They just weren’t on the same page.

You’re not stuck — you’re just repeating a pattern. The pattern of assuming understanding when it doesn’t exist yet. Change it.

The Competence Misdiagnosis

When the work comes back wrong, your brain goes to competence. This person isn’t capable. They don’t understand. They’re not smart enough. They’re not paying attention.

But competence is usually not the issue. Focus determines direction. The direction people are moving in is based on what they understand. If they’re moving in the wrong direction, it’s not because they’re incapable. It’s because they understood something different.

Here’s a test: does this person do good work in other areas? Are they capable in their job when the instructions are clear? If yes, then the problem is not competence. The problem is clarity.

When you misdiagnose the problem, you pick the wrong solution. You think you need to manage the person more closely or consider replacing them. When what you actually need is to communicate more clearly. And the relationship damage that happens while you’re “managing” them or questioning their competence is real. Trust erodes. They get defensive. The work actually gets worse.

Better questions create better lives, and better organizations. The first question should always be: did they actually understand what I was asking?

Why People Don’t Ask for Clarity

Here’s the thing that’s important to understand: your team probably did recognize the gap. They probably realized they didn’t fully understand. But they didn’t ask.

Why? Several reasons. They’re afraid of looking stupid. They’re afraid of disappointing you. They’ve learned from past experience that when they ask questions, they get punished somehow — made to feel bad, put on the spot, or told “you should know this.” Or they’ve seen that it’s just faster to move forward and figure it out as they go.

If your team is not asking for clarity, it’s because you’ve created an environment where it doesn’t feel safe. Or where it doesn’t feel necessary. Either way, that’s a culture problem. And culture is owned by the leader.

So when the work comes back wrong, before you blame them, ask yourself: did I create space for them to ask clarifying questions? Did I invite it? Did I make it safe? Or did I just send out a directive and expect them to execute?

In the best organizations I work with, asking clarifying questions is expected. It’s normal. It’s encouraged. The leader explicitly invites it. “I’m going to explain what I need. Tell me what you hear. Ask any question that comes up. Help me make sure we’re on the same page.”

That takes an extra 10 minutes. And it saves weeks of wasted work and frustration.

How to Communicate So People Actually Understand

Start with why. Don’t just tell them what to do. Tell them why it matters. What problem are we solving? Why does this need to happen now? What will be different when this is done? People move faster and better when they understand the purpose. And when they understand the purpose, they can make good decisions if circumstances change.

Be specific. Not “increase customer satisfaction.” That means nothing. “We need to respond to customer support emails within 4 hours instead of the current 24 hours. This is what we’re measuring and why it matters.” Now they know what success looks like.

Paint a picture. Give an example of what done looks like. What does success actually look like? What does failure look like? Help them visualize it. People understand through images and stories much better than through abstract instructions.

Invite questions. “I want to make sure this is clear. What questions do you have?” And then pause. Let them think. Don’t fill the silence. Give them space to ask. And when they do, answer genuinely. Don’t make them feel bad for asking.

Check for understanding. Have them tell you back what they heard. “Okay, so here’s what I’m hearing you’re asking for… is that right?” They might say something different than what you thought you said. That’s good. That’s the moment to correct. Before the work starts.

Repeat it. You’ll probably have to explain important things more than once. That’s not because people are slow. It’s because complexity requires repetition. Say it in the meeting. Follow up with a written summary. Reference it as people do the work. The more important it is, the more it needs repeating.

The Responsibility is on You

This is important: the responsibility for clarity is not on the person receiving the message. It’s on the person sending it.

You know the context. You’ve been thinking about this for weeks. You have expertise in the area. So the burden is on you to translate that context into something that someone who hasn’t been thinking about it can understand.

If people don’t understand, that doesn’t mean they’re not listening. It means you didn’t communicate in a way that landed for them. That’s on you to fix.

This shift in mindset changes everything. Instead of getting frustrated that they don’t understand, you get curious about what’s getting lost. Instead of blaming them, you solve the problem. You think about how to explain it differently. You ask what’s confusing. You try again.

Success leaves clues. And one of the clues is that the most effective leaders are also the best communicators. Not because they’re fancy speakers. Because they care deeply about being understood. They repeat. They check. They adjust based on what they see.

What to Do When Work Comes Back Wrong

You’ve done the work. You communicated as clearly as you could. The work still came back wrong. Now what?

First: don’t blame. Don’t criticize. Don’t make the person feel bad. That shuts down the conversation.

Second: get curious. “I see this isn’t quite what I was looking for. Help me understand what you were thinking. Where did you interpret differently?” Listen. Ask more questions. Try to understand their logic.

Third: find the gap. Where did the communication break down? What did they understand that was different from what you meant? Be honest about your part in that gap.

Fourth: clarify and retry. “Okay, so here’s what I actually meant…” And then have them articulate back to you before they try again.

This takes longer than just saying “do it again, and get it right this time.” But it builds capability. It builds trust. And the next time you give them a directive, they’ll be more likely to ask clarifying questions if they’re confused.

Create Systems That Prevent Misalignment

Don’t just try to communicate better in the moment. Build systems that prevent misalignment from happening.

Use written directives, not just verbal ones. When it’s in writing, there’s less ambiguity. And people can refer back to it.

Build in checkpoints. For bigger projects, check in partway through. Make sure people are still on the same page. It’s much better to catch misalignment halfway than at the end.

Have regular alignment meetings. Weekly if the work is complex. The point is not to micromanage. The point is to surface confusion early so you can course-correct.

Create templates or examples for recurring work. If it’s something people do often, give them a clear example of what good looks like.

The Long-Term Impact

Getting clear is not just about fixing today’s problem. It’s about building a culture where clarity is normal. Where people ask questions. Where instructions are specific. Where there’s shared understanding.

In that kind of culture, work gets done faster. People feel empowered instead of confused. They make better decisions because they understand the “why” behind the directive. They stay longer because they feel like they’re part of something that makes sense.

The next time you have a performance issue with your team, pause. Before you conclude that someone isn’t capable, question whether they actually understood. Get curious. Ask better questions. You’ll probably find that the problem was never competence. It was clarity. And that’s something you can fix. Communication’s impact on team performance