Nobody calls me when the leader is the problem.
They call me when the team is underperforming, when attrition is high, when collaboration has broken down, when results are below expectation. The assumption, almost always, is that something is wrong with the team. So they bring in someone like me to figure out what it is and fix it.
And sometimes that’s right. Teams do develop dysfunctions. Skills do need building. Group dynamics do go sideways.
But a pattern I’ve encountered more times than I can count goes like this. I spend the first week observing. Sitting in meetings, doing individual conversations, watching how work actually moves through the team. And somewhere in that first week, I start to notice something nobody has named. The team isn’t the bottleneck. The leader is.
It almost never looks dramatic. It looks like a manager who reviews everything before it goes out, not because quality is poor but because letting go feels unsafe. It looks like a decision-making process that technically involves the team but in practice always ends in the same place: waiting for the leader to confirm. It looks like a brilliant individual contributor who got promoted into management and never quite made the shift from being the best at the work to creating the conditions for others to do their best work.
The identity never caught up with the role.
I’m not talking about bad leaders. I’m talking about capable, committed, often highly respected people who are, with the best of intentions, making their teams smaller than they should be. The micromanager who genuinely experiences their constant involvement as support and is baffled when it lands as surveillance. The conflict-avoidant leader who believes they’re maintaining harmony by not naming difficult things, while their team builds elaborate workarounds for problems that one honest conversation would dissolve. The high-achiever who unconsciously raises the cost of other people’s visibility because their own competence is so central to how they see themselves.
These leaders are not failing visibly. They’re showing up. They care. Which is exactly why the problem persists, because from the outside, including from the leader’s own perspective, it doesn’t look like a leadership problem. It looks like a team that needs development.
There is a version of this story that ends badly. The team continues to underperform, some of the best people leave, and the leader gets either a new team or a performance conversation, neither of which addresses the actual issue.
The version I prefer goes like this. Someone, a coach, an HR partner, an honest peer, shows the leader what their team’s experience actually looks like. Not as an attack but as data. These are the moments where your behavior is creating friction. This is what your team experiences when you review their work before they’ve finished it. This is the cost of waiting for your sign-off on decisions they could be making.
The leader I think about most from this pattern was a technical director at a professional services firm. Two resignations in six months. Team consistently missing output targets. When I mapped the workflow, everything flowed through him. Not because anyone had designed it that way. Because over years, it had become the path of least resistance. People had learned, quietly, that bringing him a finished product was faster than exercising their own judgment and having it revisited.
He hadn’t intended any of it. When I showed him the map, he was genuinely surprised. Then he was quiet for a long time.
Six months later the same team was delivering ahead of schedule. Two people who had been invisible were now leading workstreams. He told me it was the most uncomfortable and most useful feedback he’d ever received.
The team didn’t need development. They needed someone to look up the org chart for once.
