One of the patterns I see most consistently in the women I work with is team dependency leadership — and it almost never starts where they think it does. 

Why team problems so often turn out to be identity problems — and what to do when you start to suspect that’s true for you.

One of the most consistent things I see in the women I work with is a version of the same realisation, arriving at different speeds for different people.

They come in with a team problem. Or what looks like one. The team isn’t taking ownership. Things still loop back to the leader. The same conversations repeat. Delegation happens in theory and somehow doesn’t quite happen in practice.

And somewhere in the first few months of working together, often quietly, often without any dramatic moment attached to it, they begin to see that the business has been organised around them in a way they didn’t choose and couldn’t see from inside it.

That recognition is almost always followed by something they don’t expect. Not relief. Not immediately. First, something closer to grief.

Because it means the thing that felt like competence was also a cost.

What I’ve come to understand about over-responsible leadership is that it rarely begins as a management style. It begins as a survival strategy. Being the one who carries everything — who never drops the thread, who catches it before it falls, who pre-empts the problem before the team even sees it — that behaviour was forged in a context where it worked. Where it had to work. Where the alternative felt genuinely unsafe.

That might have been a previous workplace. It might have been a family dynamic carried forward. It might have been the earliest years of building the business, when she genuinely was the only one who could hold it and the stakes were real and the margin was thin.

But then the business grew. The team grew. The context changed.

The pattern didn’t.

And so a team that is fully capable of stepping up keeps not quite stepping up — because the leader, without realising it, has been teaching them week after week that she’ll catch it. That her presence is the safety net. That the handover is never quite final.

This is not a character flaw. It is a very human response to a leadership identity that was built in one season and never quite updated.

The difficulty, of course, is that identity doesn’t yield to a better system.

I’ve watched women implement genuinely excellent accountability structures, clearer role definitions, better handover protocols — and still find themselves re-entering at 9pm to check the thing they handed over at 4. Not because the system failed. Because the system and the identity were pointing in different directions, and identity tends to win that argument quietly and consistently.

The work I find myself most interested in is the bit that happens before the system. The question of who the leader believes herself to be in the business — what she thinks her value is built on, what she’s afraid of finding out if she genuinely lets go, what the team coming to her for everything is giving her as well as costing her.

That last question is usually the most confronting. There is something in the dynamic of being needed. It’s not simple vanity. It’s often something closer to belonging, or proof of worth, or the particular safety of indispensability. Understanding that — really sitting with it rather than rushing past it — is what makes it possible to choose differently.

Because the goal isn’t to become a leader who doesn’t care or who lets everything fall away. The goal is to become a leader who can tell the difference between what genuinely needs her and what has simply been trained to. That discernment is what makes space. And space is what allows the team to grow into the people the business actually needs them to be.

I’ve seen this shift happen across industries and team sizes and very different personal histories. It is never fast. It is always non-linear. And it’s the shift I never get tired of watching someone make.

Three questions worth sitting with:

What would have to be true about your leadership for your team to step up without being asked?

When you imagine genuinely letting go of something you currently hold — not delegating but truly handing over — what’s the first thing you feel, and where does it come from?

The version of your business that runs without you at the centre: is that something you want, or is part of you still not sure?

Until next time,

Kat

Frequently Asked Questions.

Why does my team keep coming back to me even when I’ve delegated?

When a team consistently defers to its leader despite clear delegation, it’s rarely a capability problem. More often, the team has been trained — gradually and unintentionally — to rely on the leader as a safety net. This happens when a leader has a pattern of catching problems before they land, re-entering tasks after handing them over, or pre-solving issues before the team has a chance to work through them. The team learns that the handover is never quite final. Changing this dynamic requires the leader to look at the pattern underneath the behaviour, not just the behaviour itself.

Why doesn’t better delegation fix the problem of everything coming back to me?

Clearer delegation, better handover protocols, and tighter accountability systems all help — but they work at the level of behaviour. If the leader’s identity is still organised around being the one who holds everything, those systems will quietly be undermined. She may implement an excellent handover process and still find herself mentally carrying the task she technically assigned three days ago. The doing was delegated; the weight stayed. Real change in team dependency happens when the leader examines what being needed is doing for her — not just what it’s costing her.

What does it mean when a leader’s identity is built around over-responsibility?

Over-responsible leadership rarely begins as a management style. It usually begins as a survival strategy — a response to a context where carrying everything was what kept things safe, or what earned the leader her place. That might have been a previous workplace, a family dynamic, or the early years of building a business when the stakes were high and the margin for error was thin. When the context changes but the pattern doesn’t, the leader ends up running a grown business with a set of behaviours that were built for a much harder season. Recognising this is the beginning of changing it.

How do I get my team to take more ownership without micromanaging?

The most effective path to team ownership isn’t a better management technique — it’s a shift in how the leader shows up. Teams step up when they genuinely believe their leader trusts them to handle things and will not quietly re-enter. That trust has to be visible in behaviour: sitting with imperfect outcomes, asking questions rather than providing solutions, and letting some things land without catching them first. This feels uncomfortable before it feels right. The discomfort is usually information about where the real work is.

What is the difference between leadership coaching and fixing a team problem?

Most team problems — dependency, lack of ownership, poor follow-through — have their roots in leadership patterns rather than team capability. Leadership coaching addresses those patterns directly: how the leader sees herself in the business, what her default responses are under pressure, and what the team dynamics are actually reflecting about how the business has been led. This is different from a team training programme, which works at the level of skills. Both can be useful, but skills training without leadership pattern work tends to produce short-term improvement and long-term recurrence.