The Best Leaders I've Watched Did Less

I sat in on a team meeting eighteen months after a leader I admired had left.

The weekly check-in still ran at the same time, same room, same agenda. People showed up. Updates were shared. But something had gone. The meetings used to crackle: challenges got raised, assumptions got tested, someone would push back and the whole room would lean in. Now it was a status report. Smooth, polite and – empty.

Afterwards I asked a new hire why they did things a certain way. She shrugged. "That's just how it was set up."

She didn't say by whom. She didn't know. The rituals were still running but the thinking behind them had gone. Nobody on that team could feel the difference. They thought this was what the leader had built. They had no idea what they'd lost.

The leader who'd left was brilliant. Trusted. Self-aware. She'd read the research on psychological safety and lived it. People had spoken up in her meetings. They'd challenged each other. They'd brought bad news early. By every measure the transformation was working while she was there. Engagement scores were up and the Board was pleased.

I've watched this happen four times. Different companies, different sectors. Always the same arc: a leader does everything the books say. Builds trust. Creates safety. Delivers results. Leaves. And within eighteen months, the whole thing quietly unravels.

Not because they failed at leadership. Because leadership alone was never going to be enough.

Three Camps, One Missing Question

When transformation fails, the post-mortem usually falls into one of three camps.

• Camp 1: The strategy was wrong, or the execution was. Get the strategy right, govern it tightly, and change will follow. There's real substance here. I've watched transformations collapse because nobody could articulate what they were actually trying to achieve.
• Camp 2: The leaders weren't ready. This is where most energy has gone in the past decade. Amy Edmondson's work on psychological safety. Trust, vulnerability, emotional intelligence. I've watched transformations fail because leaders couldn't create the conditions for honest conversation.
• Camp 3: Nothing was built to last. No infrastructure. No transferable principles. No systems that work without their creators. This is the territory I've been writing about for the past five months: the departure test, the difference between rented and built capability.

Each camp is right about what it diagnoses. But each tends to treat its answer as the answer. Fix the strategy. Develop the leaders. Build the systems. As if the problem were a single missing ingredient.

The question that matters: how do these building blocks fit together in a way that creates lasting capability?

Good strategy doesn't remove the need for good leadership. Good leadership doesn't remove the need for good infrastructure. And infrastructure doesn't replace either, it's what connects them and makes them persist beyond the people and the moment.

If you're leading a marketing function through AI adoption, you're living all three camps at once. Your board wants the strategy. Your team needs the leadership. And the infrastructure question: can your people make good judgement calls at scale, without you in the room, is the one nobody's asking. I wrote earlier this year about what happens when teams lose the work that taught them to think. People freeze. Not because they lack ability, but because nobody built the infrastructure for the decisions that remain when the intelligence layer is automated. That freeze is a leadership problem as much as a structural one.

This piece turns to leadership because leadership is where the three camps either connect or fall apart.

Two Questions About Leadership

Within the leadership conversation, there are two questions. Most of the books, programmes, and keynotes address only the first.

• Question 1: Can you lead people through change? Build trust. Create safety. Model vulnerability. And develop your people.
• Question 2: Can you build something that works without you? This is the question that determines whether your transformation was a moment or a capability. Whether you led people through change, or built something that keeps changing after you've gone.

Question 1 without Question 2 produces heroic transformation. Change that depends on the presence of exceptional leaders. It looks like success right up until those leaders are no longer there.

Question 2 without Question 1 doesn't work either. Infrastructure built without trust is just machinery. People comply with it rather than own it. It becomes bureaucracy, not capability.

The leadership that builds lasting capability addresses both questions together. Both at once. Two sides of the same practice.

What Lasting Transformation Demands

After 25 years watching change efforts succeed and fail, I've come to see four things that lasting transformation demands of leaders. Requirements, as structural as anything in the methodology I've written about earlier in this series.

Each one operates at two levels, human and structural. Neither works without the other. The human dimension without the structural creates dependency on exceptional leaders. The structural without the human creates systems nobody believes in.

1. Discovery Over Direction

Leaders who ask questions rather than pronounce answers build trust. They signal that other people's knowledge matters. They create the conditions Edmondson describes where people can contribute without fear.

But discovery does something else. Principles that emerge through collective exploration are owned by the people who surfaced them. They're not the leader's vision, handed down. They're shared understanding, built up. When that leader leaves, the principles stay, because they were never "theirs" to begin with.

I watched it most clearly during the LEGO turnaround in the early 2000s. The new CEO, Jørgen Vig Knudstorp, later reflected: "I wasn't competent for the role, so instead of telling people what to do, I asked questions and focused on getting to the source of truth." That sounds like weakness. But the principles that emerged from those questions still guide it two decades later. They lasted because they were discovered, not decreed.

Most leadership development trains people to be better at giving direction: clearer vision, stronger communication, more compelling storytelling. All valuable. But without the infrastructure to capture and embed what discovery surfaces, even brilliant discovery fades when the leader who facilitated it moves on.

What transformation demands isn't direction or discovery. It's discovery that feeds into systems explicit enough to outlast whoever did the discovering.

2. Protecting Space

This one is easy to misread. It's easy to hear "protecting space" and picture a leader who shields their team from hard questions, absorbing pressure from above, deflecting organisational noise, keeping people comfortable so they can focus.

That's not what I mean. Or rather, that's only half of it, and the half that doesn't build capability on its own.

The leaders I've watched do this well make a distinction. They remove the wrong pressures: the politics, the interference, the meeting about the meeting, the noise that burns energy without building anything. But they don't remove pressure altogether. They make room for the right pressures, i. e., real decisions with real stakes, problems their people need to work through, consequences they have to own.

And then comes the harder part: not stepping in.

Jørgen described this as: "Many of the things happened because I didn't stop them." Not delegation, but something subtler. The restraint of not intervening when you could. Trusting that the person heading toward a mistake might learn more from the stumble than from your correction.

This is the opposite of mollycoddling. The leader clears the path so their team faces genuine challenges and then resists the urge to solve those challenges for them. That's what develops distributed judgement. Not comfort. Exposure to the right kind of difficulty, with the space to work through it.

The structural question is whether those conditions hold when the leader who created them is gone. Does the team keep wrestling with hard decisions? Or does it wait for someone to either shield them or tell them what to do?

3. In Tune, Not Right

Leaders who seek feedback, who model vulnerability, who admit when they're wrong, create conditions for learning. Edmondson's research shows teams where the leader says "I might be wrong" outperform teams where the leader needs to be right.

But "in tune, not right" does something beyond creating a learning culture. It's the only honest response to the kind of system you're actually leading. Every decision you make changes the system you're deciding in. Restructure a team and the culture shifts. Introduce a process and people adapt around it. The ground shifts underneath you, partly because of what you built on it last quarter. In a system like that, "right" is always temporary. The only sustainable posture is continuous calibration.

A leader who says "tell me when I'm out of tune" is building a culture of continuous adjustment, what I've called Type 0 calibration in earlier pieces. The human dimension creates safety to speak up. The structural dimension turns that into a self-correcting system that keeps calibrating whether or not a particular leader is asking.

Jørgen, reflecting on his own leadership: "I don't want to be right, but I want to be in tune. What I want is for people to tell me when I'm out of tune, unfiltered."

Self-awareness is a personal quality. It leaves with the person. The structural question is whether you've built an organisation that self-corrects, not because one leader is unusually open to feedback, but because the system expects and enables continuous adjustment. Build the second while you still have the first.

4. Never Done

Leaders who stay open to learning, who resist the temptation of "we've figured this out", help their teams adapt. Growth mindset, in the popular framing.

But "never done" has a structural implication that goes beyond any one leader's posture. A leader who embodies this builds an organisation that expects and welcomes ongoing tuning, rather than waiting for the next transformation programme.

"There was never a moment when everything worked." That's not a confession of failure. It's a design specification. The system is never finished. Calibration is the permanent state, not the gap between one stable period and the next.

Most organisations treat change as episodic: a disruption to be survived, then a return to normal. Leaders who live "never done" build something different: teams that treat adjustment as the normal state. Good programme management keeps the discipline of that adjustment going: tracking, reviewing, course-correcting. Leadership sets the expectation. Infrastructure and execution make it real.

What transformation demands isn't just a leader who keeps learning. It's connecting that learning orientation to systems and disciplines that keep the organisation learning, with or without any particular leader in the room.

What Creates These Leaders

Jørgen didn't choose intellectual humility as a leadership style. He was forced into it. He genuinely didn't have the answers. The discovery orientation that built lasting capability wasn't a technique: it was the only honest option available.

The pattern holds across 25 years. A crisis that stripped away the option of pretending to know. A role they weren't qualified for. A situation where the old playbook didn't work.

So if these capabilities are often produced by circumstances most leaders don't experience, what fills the gap?

One answer: the methodology can create the conditions the crisis created by accident. When the 4Es requires leaders to explore before prescribing, they practise intellectual humility whether it comes naturally or not. When experimentation demands comfort with real ambiguity, where some hypotheses don't survive, leaders develop that comfort through doing, not training. The methodology doesn't wait for the right leaders to arrive. It creates the conditions that develop the capabilities it requires.

That doesn't mean it's easy. There's another condition that rarely gets discussed: tenure.

Game theorists call it the shadow of the future.

Short-tenure leaders, the ones who know they'll move on in two or three years, can afford heroic transformation. The gains show up on their watch; the depreciation shows up on someone else's.

Long-tenure leaders can't do this. Every shortcut catches up with them. Every dependency they create becomes their problem. Every capability they fail to transfer means they're still the bottleneck in year five, year ten, year fifteen.

Jørgen mentored me for six years. The line he gave me was: "Never take shortcuts. Even if you get away with it, you'll know." That's the shadow of the future made personal. Not just strategic calculation — integrity. The refusal to build something that works only while you're watching.

This isn't an argument against mobility. It has implications for how boards think about leadership continuity during transformation. But that's a conversation most governance structures aren't designed to have.

The Departure Test, Applied to Leadership

Here's what I've come to see, and it's not easy to say: the leadership qualities that make transformation feel successful in the moment can actually prevent lasting capability if the leader doesn't deliberately build for their own absence.

A deeply trusted, emotionally intelligent leader who personally holds the system together is, structurally speaking, a single point of failure. The better they are at Question 1, the more invisible the Question 2 gap becomes. Everyone feels the transformation is working. Nobody notices it's working because of one person.

When you leave, not if, but when, what principles did you make explicit enough that someone who never met you could apply them? What capability did you transfer so thoroughly that your team can teach it to people who haven't joined yet?

But there's a harder version of the test. It's not enough to lead this way yourself. The question is whether your direct reports lead this way with their teams. Whether the person two levels down experiences the same discovery, the same space to wrestle with real decisions, even though they've never met you. Because the leader between you and them absorbed these practices as their own.

That's the real departure test. The capability doesn't just survive your absence. It reproduces.

This requires you to systematically reduce your own importance. Every principle you make explicit is one less thing that depends on your judgement. Every capability you transfer is one more step toward making yourself unnecessary. This runs against everything leaders are trained and rewarded for. Organisations promote people who are indispensable.

The departure test doesn't care how brilliant you were. It only asks what you left behind.

Over the past six months, I've built a framework for understanding what makes change last: the diagnostic, the methodology, and now the leadership dimension. Next month, I want to get closer to the ground: what it actually looks like when leaders do this well. Not the theory. The practice.