You think you're delegating, but your team might see it differently
- Ashley

- Jun 4
- 2 min read
Most of the leaders I work with aren't over-involved because they're bad at delegating. They're over-involved because they care, because they're busy, and because stepping back is genuinely harder than it looks from the outside. If you're doing too much yourself, there's almost certainly a good reason. Probably several.
In my experience, they tend to fall into two categories: the fears that make letting go feel risky, and the personal rewards that make holding on feel right.
On the fear side, there's the worry that quality will drop and that it will reflect on them. There's the guilt of adding more to a team that already feels stretched. And there's the sense that setting someone up properly would take more time than they have right now, so it's faster and cleaner to just handle it themselves. All of these are reasonable. All of them are also quietly expensive over time.
On the personal side, there's something that doesn't get talked about enough: a lot of leaders genuinely love the work. The doing is energizing, it's where they built their reputation, and stepping back from it feels like losing something real. For leaders who came up through a technical or specialist path, there's often an added layer, a worry that if they stop doing the hands-on work they'll lose the edge that made them valuable in the first place. That's not ego. That's a completely human response to a transition nobody really prepares you for.
The problem is that while all of this is happening, the team isn't growing. People don't develop judgment when decisions are made above them. They don't build confidence when problems are solved for them. And the leader stays stuck in work that belongs at a level below them, which means the work that actually requires their seniority keeps getting deferred.
The shift that changes this isn't about dumping work on people or letting go blindly. It's about getting genuinely clear on what a good outcome looks like before work begins, and learning to ask questions instead of provide answers when things get difficult. Both of those sound simple. Neither of them is. But both are learnable, and when they start to click, the difference for the leader and the team is significant.
If this is something you're noticing in yourself, or seeing in your organization, let's chat.

Comments