Self-organisation in teams – why leadership still matters

At some point, many leaders and founders reach a breaking point. Everything runs through them, every decision lands on their desk, the team waits for approvals. The solution seems obvious: more ownership, less hierarchy, self-organisation.

So leadership steps back. Often deliberately, and with the best intentions.

And then the opposite of what was hoped for happens. The team waits. Issues go undecided. People ask for more input than before. At some point, someone asks for more leadership – the very thing you were trying to reduce.

This isn't a sign that the team can't or won't step up. It's the logical response to an unclear situation.

When leadership pulls back without explicitly defining decision-making boundaries, the result isn't empowerment – it's uncertainty. Who gets to decide what? Where does responsibility begin, and where does it end? When is alignment necessary, and when isn't it?

Without answers to these questions, people naturally default to caution. They hedge, seek reassurance, leave things undone rather than risk making the wrong call. This paradoxically creates more dependency on leadership – even though leadership had exactly the opposite in mind.

There's a second pattern I regularly see in practice: decisions get delegated, then quietly taken back. A proposal comes back with "but actually, it should probably work like this." A team decides something, and shortly after, the outcome gets "briefly revisited" – and ultimately overruled.

Teams learn from these patterns fast. If your decisions keep getting overridden, you eventually stop deciding. Not because you don't want to. It's simply rational: why invest energy when the result will be corrected anyway?
What looks like a lack of ownership is often the logical response to a contradictory signal.

Self-organisation doesn't emerge from leadership stepping back – it emerges from leadership deliberately shaping what belongs to the team and what doesn't. That's not more control. It's more clarity.

A few questions that help:

Which decisions actually belong to the team?
Get as specific as possible. What can the team decide without checking in? Where is sign-off genuinely necessary – and why?

Where am I quietly taking decisions back?
This rarely happens deliberately. Usually it comes from high standards, experience, a strong sense of responsibility. But the system learns regardless. It's worth being honest here: which topics are hard to let go of – even after you've delegated them? Sometimes there's more to it than standards. It's also about what your own role means when others are the ones deciding.

What are the guardrails?
Self-organisation needs a clear framework. Which values, quality standards, or strategic priorities are non-negotiable? Once those are explicit, teams can actually work autonomously within that space.

How do we handle decisions we disagree with?
Letting go of responsibility means accepting that someone else makes the call – and that you might not like it. If that's hard to sit with, you'll keep pulling decisions back. And in doing so, you'll keep the team from ever moving forward on their own.

In most organisations, not every decision can or should sit with the team – and that's not the goal. The goal is to make it transparent: which topics belong to the team, which don't, and why.

Setting up that framework takes effort upfront. A conversation, a clarification session, maybe a workshop. But it's exactly what creates relief in the long run. When decision-making boundaries are clear, there are fewer questions to field. Teams can genuinely work independently. And leadership doesn't have to be the bottleneck anymore.

Clarity isn't a constraint on self-organisation. It's what makes it possible.