Article
The Self-Reliance Curve

Ownership: the moment your team has moved past you

Raymond Honings 25 November 2025
An empty manager's chair in a meeting room where the team is working on a challenge themselves.
Summary

The best leadership moment is when your team solves the problem you did not know about yet. A manager came back from three days away expecting chaos: the supplier issue was resolved, the client question handled, the tension between two colleagues talked through. It felt strange, as though he was no longer needed. That strange feeling is precisely the sign that it works. Indispensability is not value, it is dependency in a good suit.

Key Insights
  • The goal isn't to be needed. The goal is to be trusted. That's a big difference.
  • When people need you, they wait. When people trust you, they move.
  • A team becomes self-regulating when leadership is woven into how they work, not summoned only when called.

The best leadership moment? When your team solves the problem you didn't even know about.

Three days away, everything handled

A manager told me this last month over coffee.

We were catching up. He described his week. Then he stopped halfway through a sentence.

"Something strange happened. I was away for three days. Wedding in Portugal. Phone mostly off. When I came back, I expected chaos. Maybe a few fires to put out. But they had already handled it. The supplier issue I was worried about? Solved. The customer question that needed an answer? Handled. The tension between two colleagues? They had talked about it."

He looked at me.

"Honestly, it felt strange. Like maybe I wasn't needed anymore."

I smiled. Because that strange feeling is the sign that it's working.

It felt strange

The fact that it feels strange reveals something about how we've learned leadership.

We learn that good leadership means being indispensable. Being the one with answers. Being the one who steps in when it gets hard.

Indispensability feels like value. A team that can do without you feels like loss of value. That's why it feels 'strange' when you come back and no one has saved a crisis for you.

But indispensability isn't value. It's dependency wearing a good jacket. And dependency is costly for the leader, the team, and the organization. For the leader because she can never truly disconnect. For the team because it doesn't learn to carry. For the organization because everything hangs on one person.

Indispensable versus trusted

Here's what most leaders miss.

The goal isn't to be needed. The goal is to be trusted. And that's a big difference.

A leader who is needed fills space. A leader who is trusted opens space. The first produces teams that wait. The second produces teams that act.

The difference doesn't sit in the team's skill. It sits in where the leader gets her value from. Whoever gets her value from solving keeps solving. Whoever gets her value from seeing the team solve, moves the system in a different direction.

Need waits, trust moves

When people need you, they wait. When people trust you, they move.

Those two sentences seem small but explain a lot. A team that waits sometimes looks helpful. They don't want to make a mistake. They want to incorporate your input. They want alignment. All good reasons, all symptoms of a team in 'need' mode.

A team that moves first feels to the leader as if something is happening unsupervised. Sometimes things go differently than she would have wanted. But ten things that deviate slightly and nine times resolved well yields more than ten things that first had to land on her desk.

The shift doesn't happen by accident

That shift doesn't happen by accident.

It starts when you stop solving and start asking questions.

When you let people sit in discomfort instead of rescuing them.

When you make it safe to try, fail and learn without judgment.

Three movements. Small in phrasing, heavy in execution. Because each movement asks the leader to give up something that first gave comfort. The solving instinct gives comfort. The rescue instinct gives comfort. Judgment gives comfort. All three need to lessen a bit before the system can find its own balance.

The signal: 'we handled it'

Slowly something changes. People stop checking in before they act. They start solving problems before you even see them. They give each other feedback without you having to be in the room.

That's when a team becomes self-regulating. Not because they don't need leadership. But because leadership is already woven into how they work.

I see this with the teams I guide: the moment when someone says 'we handled it' instead of 'what should I do?'

That isn't loss of control. It's evidence that the culture holds.

Leadership as shaping environment

As Edgar Schein taught us: real leadership is less about steering behavior and more about shaping the environment where the right behavior becomes natural.

That sounds abstract. In practice it means: fewer rules, more rituals. Fewer control points, more shared definitions. Fewer answers, more sharp questions. Whoever sets up the environment differently doesn't need to constantly correct behavior. The behavior adapts itself.

The next time you come back and the team has handled everything without you: pause before you take something back. That moment isn't a transgression. That moment is evidence that it's working.

A Take-Home Message

The goal isn't to be needed. The goal is to be trusted. When people need you, they wait. When people trust you, they move.

The shift doesn't happen by accident. Stop solving, start asking questions, let people sit in discomfort, and make it safe to try and fail without judgment.

The next time you come back and the team has handled everything: that strange feeling isn't loss. It's evidence.

Frequently Asked Questions

How do I know if my team really needs me or has learned to wait? +
Test it. Be explicitly unavailable for one clearly bounded period (a day, a week). Not as a secret experiment, but as a clear agreement. See what happens. A team that really needs you can make that visible in your absence through targeted questions. A team that has learned to wait slows down without naming what they're missing. Observation during your absence is much sharper than any conversation beforehand.
What do I do if I come back and the team handled it 'wrong'? +
First: confirm that they handled it. That's the most important signal. Then: discuss the approach, not the outcome. 'Wrong' can mean they made different trade-offs than you would have. That's information, not a mistake. Ask why they made that trade-off. Often you discover they saw something you wouldn't have seen. Sometimes you discover an agreement was missing. Both are valuable to know.
What if 'taking ownership' has never been the culture? +
Then you don't start with 'take ownership'. You start with 'what would you do if I weren't here?' Ask that question for every decision that comes to you. Not as a test, as a habit. The team learns that their thinking gets explicitly summoned. After a few weeks the thinking starts before the decision is brought to you. That's the beginning of ownership, and it didn't emerge through a speech, but through a recurring question.
How do I stay a leader if the team does everything themselves? +
By leading at a different level. A leader who no longer has to solve can see what the team can't see: broader context, external signals, long-term implications. A team that regulates itself needs a leader who looks strategically, not operationally. Many leaders discover in this phase that they never really got to strategy because operational puzzles filled all the room.
What if the organization confuses 'presence' with 'leadership'? +
That's a different challenge. Many organizations reward visibility and presence in meetings. A leader who has made her team self-regulating can then be in a contradictory signal: the team works better, but she's less visible. Two strategies. Make results visible, not presence. And document how the team functions in your absence, so others can see that the system works, not only you.
Raymond Honings
About the author

Raymond Honings

Raymond is the founder of Seemotion. He works with managers and leadership teams across cultures, helping them build self-reliant teams that perform under pressure. Over the past years he has worked with more than 1,000 managers worldwide. Today most of his work takes place in Asia, mainly in Korea, Taiwan, China and Japan.