Building Systems That Outlast You: A Leader's Guide to Institutional Legacy

A few years ago, I had the chance to revisit a regional health programme I had led for almost five years — a social franchise network for primary care services in rural communities across two Nigerian states. I had moved on to other roles, and the programme had continued under new management.

I went back expecting, I think, to be proud. I had invested a significant part of myself in that work. The systems we designed, the staff we trained, the community relationships we built — these had taken years of concentrated effort. If they were still functioning, that would be the proof that the work mattered.

What I found was more complicated.

Some things were running well — better than when I had left, in fact. The patient data system had been improved by the team that inherited it. A few of the franchise facility owners had taken on leadership roles in their local government health authorities and were applying what they had learned at scale.

But other things had quietly unravelled. A procurement protocol I had designed — and which had been critical to maintaining supply chain integrity — had been modified in ways that reintroduced the exact inefficiencies it was built to prevent. The modification made sense to the person who made it, given her specific constraints at the time. But the reasoning behind the original design had never been documented. It had lived in my head, and when I left, it left with me.

That visit changed how I think about institutional legacy. And it gave me three lessons I now hold onto quite tightly.

Lesson One: Your Successor Inherits What You Built, Not What You Intended

There is a gap — sometimes a very wide gap — between what a leader intends to create and what actually persists after they leave. In most organisations, the gap is much larger than we admit to ourselves.

We build systems based on our own deep understanding of the context: the supply chain vulnerabilities we learned the hard way, the stakeholder relationships we spent years cultivating, the regulatory nuances we navigated through repeated trial. Our successors inherit the structure of what we built without the context that made the design choices make sense.

The result is what I call "structural orphaning" — a system whose design choices become increasingly mysterious to the people operating it. When they encounter a constraint they do not understand, they work around it rather than understanding why it exists. Gradually, the thing you built drifts away from what you intended.

The solution is not complicated, but it requires discipline: document the reasoning, not just the decision. Every significant design choice — every process, every protocol, every structural feature — should carry with it a clear explanation of why it was built this way, what problem it was solving, and what would break if it were changed. This documentation is not for auditors. It is for your successors. It is the conversation you will not be there to have.

Lesson Two: People Are the Most Durable Infrastructure

When I look back across twenty-five years, the things I built that have lasted longest are not programmes. They are not systems or strategies or structures. They are people.

I think of a young programme officer I worked with in the late 2000s — someone who started as a community mobiliser and who I pushed, repeatedly and sometimes over his own protests, into roles of increasing responsibility. He became uncomfortable with visibility. He preferred to be behind the scenes. I kept creating circumstances that forced him into the front.

Today he leads a national health systems team for one of the major INGOs working in Nigeria. He told me a few years ago, in one of those honest conversations you only have after sufficient distance, that he had resented my insistence at the time. And that he was grateful for it now.

I am not telling that story to flatter myself. I am telling it because it contains the most important insight I have about legacy: the highest-leverage investment a leader can make is not in a programme or a system. It is in a person who will go on to do work you cannot predict, in places you will never reach, long after your formal role has ended.

People, developed well, compound in ways that spreadsheets cannot capture.

Lesson Three: Culture Is Caught, Not Taught

I have worked in organisations with elaborate values frameworks — mission statements printed on walls, competency models documented in HR manuals, leadership principles communicated in all-hands meetings. In my experience, these artefacts correlate almost nothing with the actual culture of the organisations that produce them.

What actually determines culture is what leaders do, specifically when it costs them something.

When a senior leader admits a mistake publicly, rather than deflecting blame, the team learns that honesty is safe. When a leader pushes back on a funder's unrealistic demands in defence of programme quality — rather than accepting the pressure and passing it down to staff — the team learns that quality is a real value, not a slogan. When a leader promotes the person who challenged her thinking over the person who agreed with everything she said, the team learns that intellectual courage is rewarded here.

These moments — repeated, consistent, and observed — are what culture is actually made of. They cannot be documented in a values framework. They can only be lived. And they outlast their author only if they have been lived frequently enough and publicly enough that the team has internalised them as the way things are done here.

This is why I am so resistant to the idea that culture can be "changed" through a communications initiative or a new set of stated values. Culture changes through changed behaviour by leaders. Full stop. Everything else is noise.

A Final Note on the Discomfort of This

Everything I have described requires confronting something that many leaders, myself included, find genuinely uncomfortable: the acknowledgement that the work must eventually proceed without you.

There is a version of leadership that is deeply invested in indispensability. The leader who is the only one who really understands how things work. Who is always the smartest person in the room. Who the organisation visibly struggles without. I have seen this pattern produce capable people who create talented, dependent teams. The capability is real. But so is the fragility.

The work I am most proud of — the work I think about when I ask myself whether my career has mattered — is not the programmes I personally delivered. It is the systems that are still running well without me, and the people who are leading things I could not have imagined when I was their manager.

That is the only measure of institutional legacy I find fully satisfying. And building toward it requires, above everything else, the willingness to make yourself unnecessary. Not immediately. Not without preparation. But deliberately, consistently, and sooner than feels comfortable.

That is, I think, the real work of leadership. And it is the work I am still learning how to do.