When something no longer needs you

There is something strange about returning to something you once helped lead and realising it no longer needs you.

Last week I went back to The Gap State High School for the Launch Innovation Conference. Launch was a significant part of my high school years: a student-led program where young people were trusted with real responsibility — organising events, coordinating teams, solving problems, making decisions, fixing mistakes, and building things other people depended on.

For several years, I helped carry it. This time I did not. I came back as a spectator.

I judged an innovation challenge I had once helped run. I spoke with students whose experience of Launch had developed long after I left. Many of them had no idea who I was.

That was probably the most important part of the day. It was not my Launch anymore. The people inside it had made it their own.

What we misunderstand about legacy

When we talk about legacy it is easy to imagine remembrance — names, stories, traditions, recognition, whether people know who started something.

I learned something different when I first left Launch, and going back reinforced it. Legacy is not primarily what people remember about you. It is what continues because of what you helped build.

That might be a standard someone still holds. A belief they pass on. A way of treating people. A piece of knowledge, a capability, a system. Or simply the confidence to take responsibility for something themselves.

The strongest legacy is usually the least visible to the person who helped create it.

Leadership should eventually make itself less necessary

At Launch I worked alongside people who are still some of my closest friends. We were trusted with a surprising amount — coordinating events, working through problems, fixing things at the last minute, forgetting things, getting things wrong, and learning through the consequences.

The value was not that everything worked perfectly. It was that the responsibility was real.

Later, as I approached the end of school, I had the chance to mentor younger students who would eventually take over. On Friday I watched two of them, Thomas and Presiyan, nearing the end of their own time with the program.

What stood out was not how visible they were. It was how often they stepped back. They gave newer leaders room to take ownership, and supported younger students with patience. They did not need to dominate the room to prove they were leading it.

One of the easiest traps in leadership is to confuse importance with dependence. If nothing works without you, that can feel like evidence that you are valuable. Sometimes it is evidence that you have failed to build enough capability around you.

At Slash we think leadership should increase the capability and judgement of the people around it rather than make the leader indispensable. A good leader should eventually be able to leave the room.

Responsibility is how capability actually develops

This matters well beyond leadership handovers.

A lot of development is still designed around information. We teach, we explain, we train, we hand people frameworks. All of that can help. But capability is not created by information alone.

People develop when they are given something meaningful enough to carry. They meet ambiguity. They have to decide. Someone depends on the outcome. Things go wrong. They get feedback, and they adjust. Then, if the environment is built well, they are trusted with something larger.

That idea now sits explicitly inside how we think about human development at Slash: capability develops through action, challenge, feedback, responsibility, opportunity and choice.

Responsibility should not be reckless. People need support, boundaries, and enough safety to learn without causing unreasonable harm. But if nobody depends on the outcome, something important is missing — the responsibility is not fully real.

Ownership means letting people change what you built

There is a less comfortable part of this.

If something genuinely belongs to the people who come next, they have to be allowed to change it. That is hard. Founders find it hard. So do managers, parents and institutions. We say we want people to take ownership, then get uneasy when ownership produces decisions different from our own.

Preservation is not the same as stewardship.

The newer Launch teams did not preserve the version I knew. They changed how they show up, and built their own relationships, traditions and rhythms. That is not a failure of legacy. That is the point.

At Group level we describe this as independence without isolation: something should be able to stand on its own without being cut off from the support, relationships and knowledge around it.

The test is not whether the next person reproduces you. It is whether they can carry the responsibility well.

Good work should leave more capability behind

This is one of the ideas that increasingly connects the different things we build.

In technology, a client should not need us forever just to understand or operate what we built. In leadership, a team should not depend on one indispensable person to keep functioning. In development, the goal is not to keep someone reliant on a program for direction. In venture building, a company should eventually become an institution rather than a permanent extension of its founders.

Different domains, one underlying question: what can this person, team, system or organisation now carry that it could not carry before?

That is close to the standard we are trying to hold across the Group. And it is what Friday reminded me about Launch. The strongest evidence that something mattered is not that people remember who was there before. It is that the capability stayed.

The room keeps changing

Somewhere inside Launch now are the students who will lead it next. Some of them probably do not yet know how much the experience will shape them. I did not understand it at the time either — the lessons kept changing long after I left.

That is probably why going back felt strange. I was looking at something familiar and I was no longer part of its centre.

Which was the good news. Perhaps the best thing we can build is not something that preserves our place in it. Perhaps it is something strong enough to keep moving after we leave the room.