They Did What You Said

...so why did it go wrong?

A leader I worked with once checked all of the boxes. Smart, personable nature, and fancy title. They were charismatic, and loved to talk. In a particular meeting I recall, they went on a tangent and ended up asking for a printing feature on one of our internal web sites. It wasn’t on the road map, and it wasn’t planned. In my head, I thought, who asks for printing in the 21st century. The meeting ended, and I thought that the team would add a backlog item for the feature and go back to the much higher priority work.

A week later, a partner team asked about a feature they had been waiting for. It was a reasonable request, but I found out that the feature hadn’t even been started yet. Worse, the leader from the previous paragraph heard about the delay and berated their team for not meeting customer expectations.

It turns out that the team pivoted to working on printing features and delayed higher priority features from other teams. The leader is frustrated. They said a thing, and people did the thing. But what they said wasn’t what they wanted.

The team did exactly what they were told. They just weren’t told the right thing.

A Trust Problem

This isn’t really a communication problem. It’s a trust problem.

When a team trusts their leader, they‘ll push back on requests that don’t make sense. They ask clarifying questions. They say “hey, are you sure about this? We’ve got three other teams waiting on us.” They treat a casual comment as a casual comment, not a directive.

When a team doesn’t fully trust their leader (yet?), they will do exactly what they’re told. Not because they’re robots, but because the cost of questioning feels higher than the cost of just doing it. They’ve learned, consciously or not, that the safest path is compliance.

Compliance and commitment look identical during a meeting. They feel completely different six weeks later when you’re looking at what was actually done.

The Hard Secret

Here’s the part nobody tells you when you get promoted to Director or VP.

You spent years getting good at something. Delivering software, leading teams, solving hard problems. You built a reputation. People respected your opinions. When you said something, it carried weight because you’d earned it.

Then you stepped into a bigger role, and without noticing it, or without anyone announcing it, the rules changed.

Your title got bigger but your influence didn’t automatically follow. In fact, for a while it probably got smaller, because now you may be leading people who don’t know you yet. They know your title. They don’t know yet if you’re someone worth trusting.

So they hedge. They comply. They nod in meetings and then go figure out what you actually meant, or what the safest interpretation of your words is. And sometimes, like our printing feature story, they get it completely wrong.

This isn’t a failure of your team. It’s a gap in the foundation.

When trust is missing, information stops flowing. People don’t tell you about the printing feature detour until it’s already a problem. They don’t tell you the roadmap is unrealistic until you’ve already committed to it. They don’t tell you that two of your best people are thinking about leaving, or that a critical project is on fire. You find out about everything late, through the wrong channels, or not at all. And the harder you push for answers, the less you get, because the safest thing for everyone around you is to just tell you what you want to hear.

Building Trust

Trust is built in a thousand tiny moments.

It gets built when you admit you don’t know something instead of guessing confidently. It gets built when someone on your team makes a mistake and your first response is curiosity instead of blame. It gets built when you give context instead of direction, and when you explain the why behind what you’re asking for so people can make good decisions when you’re not in the room.

It gets built when people realize you see them as humans and not headcount. That you care about their career, not just their output. That when things get hard, you’re going to be straight with them instead of managing their perception of you.

None of that comes with your title. All of it has to be earned, slowly, through thousands of interactions that will feel tiny in isolation.

You Get What You Ask For

The leaders who figure this out early stop trying to lead with authority and start leading with context and curiosity. They ask more questions than they answer. They’re transparent, and share more information than feels strictly necessary. They create enough safety that people tell them the truth, including the truth that their printing feature idea probably shouldn’t jump the queue.

The leaders who don’t figure it out will keep getting compliance. They’ll also keep getting empty nods in meetings and continue to see missed expectations. And they’ll keep wondering why their team doesn’t just do what they asked.

And the frustrating part is that they’re almost always good leaders in other ways. They’re smart, experienced, and capable. They just never found the manual for this part of the job, because there isn’t one.

If you’re a Director or VP and something in here feels familiar, you’re not doing it wrong. You’re doing something genuinely hard, and you’re probably doing it without much support.

The skills that got you to this level are real. But leading at this level is a different craft, and it takes time to build the foundation that makes it work.

If this is where you are right now, let me know. I’d love to hear more.

---

If this resonates with a problem you’re facing, I have a few consulting slots open. Book some time with me to discuss.