When something no longer needs you

Most of the students had no idea who I was.

Last Friday I went back to The Gap State High School for the Launch Innovation Conference, and spent the afternoon judging an innovation challenge I had once helped run.

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, spoke with students whose entire experience of the program had happened after I left, and watched them run it well.

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

What we get wrong about legacy

Legacy is easy to picture as remembrance — names, stories, traditions, whether anyone knows who started something.

I learned otherwise when I first left Launch, and going back confirmed it. Legacy is not what people remember about you. It is what keeps working because of what you helped build.

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 invisible to the person who created it.

Leadership should 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, fixing things at the last minute, forgetting things, getting things wrong, and living with the consequences.

The value was never that everything worked. It was that the responsibility was real.

Near the end of school I mentored some of the students who would eventually take over. On Friday I watched two of them, Thomas and Presiyan, closing out their own time with the program.

What stood out was not how visible they were. It was how often they stepped back — giving newer leaders room to take ownership, supporting younger students, never needing to dominate the room to prove they were leading it.

One of the easiest traps in leadership is mistaking importance for dependence. If nothing works without you, that can feel like proof you are valuable. Often it is proof you failed to build enough capability around you.

At Slash we think leadership should raise 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 develops

Most development is still designed around information. We teach, explain, train, hand people frameworks. All of it helps. None of it is enough.

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

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

None of which is an argument for recklessness. People need support, boundaries, and enough safety to learn without causing unreasonable harm. But if nobody depends on the outcome, the responsibility is not fully real.

Ownership means letting people change what you built

Here is the uncomfortable part. If something genuinely belongs to the people who come next, they have to be allowed to change it.

That is harder than it sounds. Founders struggle with it. So do managers, parents and institutions. We say we want people to take ownership, then bristle when ownership produces decisions we would not have made.

Preservation is not 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 evidence it worked.

At Group level we call this 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 weight.

Good work leaves capability behind

The same question runs underneath everything we build. A client should not need us forever to operate what we built for them. A team should not depend on one indispensable person to function. A program should not become the only place someone can find direction. A company should eventually become an institution rather than a permanent extension of its founders.

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

That is the standard we are trying to hold across the Group. It is also what Friday reminded me. 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 in Launch right now are the students who will lead it next. Most of them have no idea how much it will shape them. I did not either — the lessons kept arriving years after I left.

That is why going back felt strange. Everything was familiar, and I was nowhere near the centre of it.

Which is exactly what should have happened. The best thing we can build is not something that keeps a place for us. It is something strong enough to keep moving once we have left the room.