I hear this complaint constantly from founders and senior leaders: "My team just won't take ownership. I have to be involved in everything. They won't make a move without checking with me first."

The diagnosis that usually follows is some version of a capability gap — the team isn't experienced enough, skilled enough, or confident enough to operate independently. The solution offered is usually more training, better hiring, or clearer processes.

Sometimes that's right. But more often, the real problem is invisible — because it lives in the leader's behaviour, not the team's.

"Your team is not failing to make decisions. They are responding rationally to the incentives your leadership has created."

How Permission Gets Withdrawn

It rarely happens through an explicit command. No leader stands up and announces: "From now on, all decisions run through me." Instead, permission erodes gradually, through a series of small signals that accumulate into a clear message.

A team member makes a call. The leader overrides it — perhaps with good reason. The team member notes: decisions get reversed here. Next time, they check first.

A project moves forward without sign-off. The leader expresses frustration — even subtly. The team registers: moving independently creates friction. They wait to be told.

A decision is made in a meeting. The leader later revisits it, adjusts it, refines it. The team learns: nothing is really final until it passes through the leader. They stop treating their own conclusions as real.

None of these moments, individually, feels significant. Together, they create a culture of learned dependency — one that is entirely rational given the signals in the environment.

The Capability Mirage

Here is what makes this pattern so pernicious: once it's established, it does start to look like a capability problem.

Because people who are not practising decision-making get worse at it. Because the team members who could tolerate autonomy — the ones with the highest potential — leave for environments where they can use it. Because the ones who remain are, over time, selected for comfort with dependency.

So the leader looks at their team and sees exactly what they feared: people who genuinely cannot operate without input. And they conclude their original diagnosis was right.

It was not. They created the conditions, and the conditions produced the outcome.

What Autonomy Actually Requires

Genuine team autonomy is not the absence of leadership. It is the presence of a very specific kind of leadership — one that does three things consistently.

First, it establishes clear decision rights. Who is authorised to decide what, at what level, without escalation? Most organisations have never answered this question explicitly. And in the absence of an explicit answer, the default is always: check with the boss.

Second, it tolerates imperfect decisions. This is the harder part. If every suboptimal choice gets corrected, refined, or revisited, the cost of making decisions rises. Eventually, the rational response is to not make them at all. Autonomy requires accepting that some things will be done differently than you would have done them — and that this is a price worth paying.

Third, it builds capability deliberately. This is not the same as hoping people will figure it out. It means creating structured opportunities for people to practise decision-making with real stakes, real feedback, and real consequences. It means coaching rather than correcting.

The Permission Conversation

The fastest way to begin shifting this pattern is often the most direct: have an explicit conversation about permission.

What can your team decide without coming to you? What should they bring to you — and why? What does it look like when they've handled something well? What would you like to stop being asked about?

These conversations are uncomfortable because they surface assumptions that have been operating silently. But they are also clarifying in a way that no amount of new process or training can replicate.

Your team doesn't need more skills to make more decisions. They need to know — clearly, explicitly, and backed by your behaviour — that they are actually allowed to.

A Final Note

If you read this and felt a flicker of recognition, resist the urge to fix it all at once. Recalibrating a culture of dependency takes time, because trust — in both directions — has to be rebuilt incrementally.

Start small. Identify one category of decisions you want to genuinely hand over. Communicate it clearly. Then hold the line when the instinct to step back in arises — and it will arise.

The way you respond to the first autonomous decisions your team makes will determine whether anything actually changes.