Better After Me: Why Great Leaders Build Organisations That Outgrow Them

Better After Me: Why Great Leaders Build Organisations That Outgrow Them

👁1views

Great leaders build organisations that outgrow them by aiming for success after they leave, not just while they lead. They develop people who are stronger in areas where the leader is weak, build structures that compensate for personal limitations, and coach judgment instead of issuing instructions, so the organisation does not depend on them.

Better After Me: Why Great Leaders Build Organisations That Outgrow ThemAndrew Baker's Technology Blog Posts, 20/Nov/2026
https://andrewbaker.ninja/2026/11/20/better-after-me-why-great-leaders-build-organisations-that-outgrow-them/

Article Summary
  • 1.
    What it is
    Leadership succession is explored through the author's experience replacing his predecessor as CIO at Capitec. The article contrasts trying to be the best leader with building an organisation that is better after you leave.
  • 2.
    Why it matters
    It argues that a leader who becomes indispensable leaves a weaker organisation, so the real job is to remove your weaknesses from the organisation as well as from yourself.
  • 3.
    Key takeaway
    Fixing today's problem is not succession; developing people's judgment so they spot tomorrow's problem is.
1,851 words · ~10 min read
Listen to this article0 plays

For most of my career I have wanted to be the best at whatever I was doing. In high frequency trading I wanted to be the best at it, as a CTO I wanted to be the best CTO, and in every role since I have wanted to build things other people couldn’t build and solve problems other people couldn’t solve. I am competitive and always have been, and for a long time I assumed that was what good leadership looked like.

When I became CIO at Capitec I slowly started to understand something about my predecessor that I had completely missed while working alongside him. He was playing a different game to me, and I think working that out is the most important leadership lesson I have learned.

1. He Was Playing a Different Game

My predecessor wasn’t trying to build an organisation that would be at its best while he ran it. He was trying to build one that would be better after he left, and that changes how you lead in almost every decision you make.

If your aim is to be the best CIO, you focus on your own decisions, your own capabilities and your own reputation. You get very good at solving problems and spotting what other people miss, and because you are good at it the organisation leans on you more and more, which feels like success right up until you leave. Then the decisions that depended on your judgment, the risks only you understood and the standards only you enforced all leave with you. If the organisation is weaker the day after you go, I’m not sure you can call that successful leadership, and I had never asked myself that question until I started thinking about the person who came before me.

2. Five Things on His Last Day

On his last day he walked into my office and told me five things I needed to work on. I’m not going to share them, because the specifics don’t matter here, but they were probably the most accurate observations about my weaknesses anyone has ever given me. I remember sitting there wondering how he had seen them so clearly and why he had picked that moment to say them.

At the time I heard five pieces of feedback. I’ve thought about that conversation a lot since, and I now think he was simply trying to make me better. He wasn’t showing me how much he knew or reminding me what I didn’t know; he was giving me something I could use to become a better leader than him. There was no speech, no ceremony and no expectation of thanks, just five observations on his way out of the building, and I don’t think I appreciated them properly when I got them.

3. Fixing Problems Versus Fixing Thinking

That conversation changed how I work with my own leadership team. I have always been demanding: I expect drive, a good grasp of risk, sound decisions and clear priorities. When something isn’t right my instinct is to step in and tell people what to fix, what to prioritise and what risk they have missed, and quite often I’m right.

Being right isn’t the same as being effective, though. If I tell someone what to prioritise they will probably prioritise it, but all I have done is fix today’s problem. They are no better at spotting tomorrow’s, and if I have to keep telling them, I haven’t developed their judgment at all; I have just made myself part of their decision making, which doesn’t scale and certainly isn’t succession.

So now, when someone keeps missing a risk or struggling to prioritise, I try not to hand them another list of instructions. I sit down with them and ask them to walk me through their thinking: why they prioritised what they did, which risks they considered, what they chose not to do and what would have changed their mind. Then I explain how I would have approached the same problem, focusing on why rather than what. The goal is not to transfer a decision, it is to transfer the ability to make good decisions. It takes far more time and patience, and it forces me to understand my own thinking well enough to explain it, but it is the only version that lasts.

4. Give People a Hard Time, Lovingly

Caring about your team is usually described as being supportive and kind, and that matters, but it also means having the uncomfortable conversations. If someone has a weakness that will eventually hurt them, their colleagues or the organisation, ignoring it isn’t kindness, it’s avoidance.

So give people a hard time, lovingly. Challenge their thinking, make them explain their decisions, don’t accept lazy answers from people you know can do better, and be relentless about the behaviours that matter. The key is that they know why you are doing it. Pushing someone because they are frustrating you is about your comfort; pushing them because you want them to succeed after you’ve gone is about their future, and people can feel which one it is. There is also a line between demanding and destructive, and staying on the right side of it depends on people knowing you believe in them and are invested in their success.

5. You Stop Competing With Your Own Team

One of the less obvious effects of this approach is that you stop competing with your directs or worrying about them outshining you. You actually want them to. You want their strengths to be visible, you want them to be able to stand in your shoes, and once that is really the goal, the insecurity about someone below you being better than you just goes away.

It’s a subtle shift, but it makes all the difference. You become proud of your people and what they achieve, even when it is more than you have achieved, and you celebrate their wins because you mean it rather than because it is expected of a manager. The focus moves off you and onto them. It also scales, because directs who work for a leader like that tend to lead their own teams the same way, and over time it becomes part of the culture rather than one person’s habit.

6. The Trap of Being Indispensable

Technology leaders are especially exposed here, because we are rewarded for being the person who knows the most: the one who understands the architecture, fixes the crisis at two in the morning and sees the technical risk first. That expertise becomes part of who we are, and everyone depending on us feels like proof we are doing well.

Indispensability can be a leadership failure disguised as an achievement. If the architecture only makes sense to you, it isn’t a sustainable architecture, and if the team only makes good decisions when you are in the room, you haven’t built a leadership team, you’ve built a dependency. We spend our careers removing single points of failure from systems, and I can’t see why leadership should be any different.

That doesn’t mean organisations never need a strong individual. Sometimes someone has to make the hard call, impose an unpopular standard or step in because nobody else can, and refusing to do that in the name of developing people is abdication. The difference is whether your strengths are building capability around you or hardening into a permanent dependency. Step in when you have to, but treat each time you do as a sign of something you haven’t built yet.

Jim Collins found something related in his research on Level 5 Leadership. The leaders of companies that made a sustained jump from good to great directed their ambition at the institution rather than themselves, and tended to set their successors up for even greater success, while many of the comparison leaders set theirs up to fail. He wasn’t studying leaders deliberately removing their own weaknesses from the organisation, so that part is my interpretation, but it fits with what he found.

7. Your Weaknesses Should End With You

My predecessor knew his weaknesses and worked to build an organisation that wouldn’t inherit them, and that is the idea I keep coming back to. Nobody becomes perfect, but you can be deliberate about what you pass on. If I’m impatient, I should develop leaders who combine urgency with patience, and if I lean too hard on my own judgment, I should build a team I trust enough to disagree with me. Every time I find a weakness in myself, the question is not only how I fix it but how I stop the organisation inheriting it.

This isn’t an excuse to stop working on yourself. You still do your best and still work through your imperfections, and a big part of this is constant self reflection: being honest about your blind spots, checking whether your team has the same ones, and working on both at once. Weaknesses tend to copy themselves, because leaders hire and promote people who think like them, so a flaw you never deal with in yourself usually turns up again in the people around you. The alternative is a selfish kind of leadership where the real goal is to be the most important person in the building, and that can look impressive for a while but leaves the organisation weaker when you go.

My strengths should be the foundation my successor builds on, and my weaknesses should be problems they no longer have to solve. It’s a high bar and I don’t know whether I’ll clear it, but I’m fairly sure it’s the right one.

8. Better After Me

I still want to be excellent at what I do, and I don’t expect the competitive streak to go anywhere, but I think for much of my career I was competing in the wrong competition. The job isn’t to be the best CIO; it’s to build an organisation that produces a better CIO after me, one that keeps what I did well and has already learned from what I did badly. Your biggest achievement might be something you never see, and I find that oddly freeing.

I don’t know whether my predecessor would describe any of this in these terms, and this is my own reading of what I experienced. What I do know is that he left me something more valuable than a job title or an organisation to run; he left me a different definition of success. One day, when it is my turn to walk into my successor’s office for the last time, I hope I can give them something equally valuable, which is not an organisation that needs me, but one that is better because I was there and better still because I have gone.

Further Reading

  • Jim Collins, Level 5 Leadership: The Triumph of Humility and Fierce Resolve, Harvard Business Review, 2001.
  • Kimberly Wade-Benzoni, How to Think About Building Your Legacy, Harvard Business Review, 2016.
  • Rebecca Slan Jerusalim and Navio Kwok, The Vital Role of the Outgoing CEO, Harvard Business Review, 2024.
  • Coaching (Asking) vs. Directing (Telling), Harvard John A. Paulson School of Engineering and Applied Sciences.

Leave a comment

Your email address will not be published. Your first comment is held for approval.