The Leaders Who Last Aren't the Ones Who Know

Early in my career, a leader I respected told me I was too polite.

The specifics were small. When I asked my team to do things, I said "please." To me this was basic courtesy. I'm a Finn, but I'd spent enough time in the UK by then that "please" was automatic. To this leader, who was Nordic, it was something else. Saying "please" turned an instruction into a request. It opened the door to discussion. It signalled that the team could say no. And in their view, that was a failure of leadership before you'd even started.

I understood the logic. If your model of leadership is that the leader decides and the team executes, then "please" is noise. It muddies the authority. It slows things down.

But I kept saying it, more on instinct than principle. Something about the alternative felt wrong for the team I was working with. These were smart, experienced people. A directive approach wouldn't have energised them. It would have shrunk them. They'd have done what they were told and stopped bringing what they actually knew.

What I was reaching for, without having the language for it yet, was partnership. It wasn't a flat hierarchy; I was still the leader, still accountable. But the stance underneath said: I trust you to think, and I want that thinking. My job was to create the conditions where it actually mattered.

The result was a team that stepped up, because they didn't want to let each other down.

I've thought about that conversation for twenty years. It stung, and that faded. What stayed was the line it drew between two fundamentally different ideas about what leadership is for.

From Framework to Floor

Last month I wrote about what lasting transformation demands of leaders: four dimensions that aren't personality traits but structural requirements.

1. Discovery over direction.
2. Protecting space.
3. Staying in tune.
4. Never done.

I meant every word. But frameworks describe the architecture. They don't tell you what it feels like to live inside it.

This piece is the companion. Same four dimensions, but seen from the ground, in daily choices, where nobody's writing a case study about you. Discovery as a leadership stance. Protecting space when it costs you something. Staying open when your experience screams otherwise. And the quiet proof that it's working.

Discovery as Partnership

The "please" conversation was my first brush with what I'd later call discovery over direction, before I had any framework to put it in.

Discovery, as a leadership practice, sounds like it's about asking questions. It is. But behind the questions is a stance: I need your judgement as much as your output. That stance shapes everything the team is willing to bring.

I've watched this play out dozens of times with strategy rollouts. A strategy gets set. Clear objectives, sound logic, well-governed execution plan. It cascades through the company. People get their briefs, their deliverables, their KPIs. They execute.

But nobody below the room where the strategy was made understands why it looks the way it does. They know what they're delivering. They don't know what was debated, traded off, weighed and rejected. So when something changes (the market shifts, a new constraint appears, an opportunity arrives that doesn't fit the brief), they escalate. They can execute the plan. They can't think with it.

Now compare what happens when the same team is involved in building the strategy. When they've wrestled with the trade-offs, heard the reasoning, tested it. Those people adapt without waiting for permission, because they understand the logic well enough to know what bending is acceptable and what would break something important.

The signal it's working? Someone disagrees with you because they've grasped the thinking well enough to see a flaw you missed. That's capability showing up as disagreement.

And the cost when it's missing isn't just frustration. A team that complies but doesn't think is a team that can't adapt when the world changes faster than the plan. At scale, that's a company that needs permission from the top to respond to what's happening on the ground. I've watched organisations lose months to that gap.

Different situations demand different approaches. Crisis needs direction, ambiguity needs exploration. But the default matters enormously.

What Protecting Space Actually Costs

If discovery is the stance, protecting space is what sustains it. And it's the dimension most likely to go wrong.

I once watched a leader try to protect their team the wrong way. They absorbed pressure from above. They deflected organisational noise, the politics, the posturing, the meeting about the meeting. The team operated in what felt like a bubble of calm.

But absorbing everything comes at a cost. Over time, the weight turned inward. The leader became resentful, and the target was the team, not the company above them. When progress was slower than expected, the frustration leaked out. Small comments. Implications that the team didn't understand how much pressure existed above them. Snipes at individual work that felt disproportionate.

The trust collapsed quickly. Team members started second-guessing themselves, presenting work with caveats and apologies before anyone had said a word. Two years of confidence, dismantled in a few months of doubt.

That collapse had a cost beyond the human toll. The team's best people started leaving, quietly updating their profiles and taking calls. The ones who stayed became risk-averse, checking everything with the leader they no longer trusted. Decisions that used to take a day took three weeks. A transformation that had been running ahead of schedule stalled, then slipped, then got quietly downgraded in the next board review. The budget wasn't cut. The ambition was, which is worse.

The leaders I've watched do this well make a different move. They sort the pressure instead of swallowing all of it. The politics and interference get filtered out. But the real challenges, the hard decisions, the problems the team actually needs to work through — those get let in. Deliberately. Because that's where judgement develops.

And then comes the part that's hardest to teach: not stepping in when you could. Watching someone head toward a mistake and holding your nerve. Not because you don't care. Because you care about what they'll be able to do next time, when you're not there.

The systems thinker Donella Meadows spent her life mapping how complex things work, and closed her best-known book on a quieter note: you can't control a system like that. You can only learn its rhythm and stop fighting it. She warned against being an unthinking intervenor. She isn't telling leaders to do nothing. The point is subtler: the urge to fix is often the thing that breaks.

Nicolai Tangen, who runs Norway's sovereign wealth fund, set his teams a hard mandate, then did the harder thing. He left them to find their own way there. That took more nerve than stepping in. Restraint with a spine. The direction was fixed. The route was theirs, and so was the learning.

When Experience Works Against Staying in Tune

Discovery and protected space create the conditions for thinking. But there's a trap that waits for leaders who've been sustaining those conditions for a long time, and it strikes at the third dimension, staying in tune.

You've seen a lot. You've been right often enough that your pattern recognition is fast and usually accurate. Someone brings you a problem and you can see the answer before they've finished describing it. Three times out of four, you're right.

So you stop listening early. You jump to the answer. You save everyone time by cutting to what you already know.

Here's the problem: the three times you're right, you've saved twenty minutes. The one time you're wrong, you've missed something that mattered, and nobody tells you, because you didn't create space for it. Your speed signals that the conversation is over before it started.

I've caught myself doing this. It's the moment when experience flips from asset to liability, when the thing that made you effective starts preventing you from seeing what's actually in front of you.

Last month I described staying in tune as building a self-correcting system: an organisation that calibrates whether or not a particular leader is asking. That's the structural goal.

The cost of getting this wrong goes beyond bad decisions. When the most experienced person in the room stops genuinely listening, the organisation loses its early warning system. The meetings still happen. The updates still flow. But the thinking moves out of the room, and the signals that something is changing reach the top last, not first.

The Quiet Proof

The fourth dimension, never done, is the hardest to write about, because when it's working you barely notice.

It doesn't look like a transformation. It looks unremarkable. That's the point.

A meeting where you haven't spoken in twenty minutes, and the conversation is sharper than anything you would have steered. Someone making a call you wouldn't have made, well-reasoned, and you leave it alone. A team member coaching a newer colleague not just on the task but on the thinking behind it: why we do it this way, what "good" looks like here.

The biggest signal? When you're not needed for something you used to be needed for. When a decision gets made in your absence and it's sound. When the principles you've spent years making explicit show up in someone's work who you've never directly managed.

That's proof of transfer, not lost control.

It happens gradually. There isn't a moment when you hand over the keys. There's a slow realisation that the capability isn't attached to you anymore. It's embedded in how they work.

That's the "never done" dimension made visible. The team absorbed it, and kept going. The leader never announced it.

If someone asked you "what is your team becoming?" this is what the answer looks like when it's working. Not a strategy document. Not a capability matrix. A room full of people making good calls without you in it.

What "Too Polite" Was Really About

The leader who told me I was too polite was solving for speed: a clean line between decision and execution. In contexts where that matters, they were right.

But I was solving for something else, even if I couldn't have said it then. A team that would still be working well after any one of us left. People who would think with me and own the reasoning. Capability that would compound rather than deplete.

That's the hardest thing leadership asks. And it's the only thing that lasts.

Last month I explored what transformation demands of leaders. This month I've tried to get closer to the ground. Next month, I turn the question outward: how a brand can hit every number and still lose the people who used to care, long before anything shows up on a dashboard.

Sources

• Donella Meadows, Thinking in Systems (2008): the closing "Living in A World of Systems" chapter, on why a complex system can't be controlled, only tuned. The root of the restraint argument here. (link)
• Amy Edmondson, The Fearless Organization: the conditions for honest challenge this piece treats as necessary but not sufficient. (link)
• Aswath Damodaran, "An Ode to Restraint: Lessons from the Tim Cook Legacy at Apple." (link)
• Tony Fadell on manufactured constraints (General Magic). (link)
• Nicolai Tangen, Norges Bank Investment Management: a fixed mandate, then autonomous teams left to deliver it. (link)