The Three Anchors That Keep Leaders Stuck

A few years ago I sat across from a COO, who hadn't taken an uninterrupted holiday in almost 3 years. He was brilliant. His business respected him. And he was tired in a way sleep no longer fixed.

I asked him one question: "What happens if you go dark for a week?"

He laughed, then went quiet, then said the thing I have since heard, in some form, from dozens of capable leaders. "It would fall apart. Not because the team isn't good. Because everything still runs through me."

He said it almost with pride. And that was the moment I understood the problem. He wasn't describing a failure. He was describing a virtue — and the virtue was the trap.

So I asked him the obvious question. "You've just told me everything runs through you. Do you know why that dependency exists?"

He thought about it properly. "I suppose I have context no one else has. I've earned the management's trust, so things land on my desk. And the team is good — but they're not ready to carry it on their own yet." Context, competence, trust. It was a tidy answer, and every word of it was true.

"What else?" I asked.

He looked at me, and for the first time the easy answers ran out. "I don't know," he said. "Isn't that enough?"

It wasn't. So instead of explaining, I told him a story.

I once knew a leader who wanted, more than anything, to be indispensable. He would never have said it that way — no one ever does — but everything he built quietly pointed at it. And if you watched him long enough, you could see his indispensability resting on three anchors he didn't know he'd dropped.

The Need to Know. He had to know everything before anything could move. Every decision waited for his read, his blessing, his nod. He told himself he was protecting quality. He was protecting his centrality. Information had become power — and he wasn't about to share the one thing that kept him at the centre of the room.

The Need to Solve. Every problem that walked in walked back out as his. He thought this made him generous, the leader who always had the answer. But the leader who defines his worth by the problems he fixes isn't building capacity. He's consuming it — drawing every difficulty toward himself and leaving his people a little smaller each time.

The Need to Be Present. He had to be in the room, on the call, copied on the thread. Visibility had become his definition of leadership. And here was the cruel mathematics of it: because he insisted on being everywhere, nothing ever learned to function without him. So on the rare day he stepped away, things wobbled — which he took, every time, as proof that he was needed. He had built an organisation that proved him correct by failing in his absence.

I stopped there. The COO was quiet for a long moment. Then he said, almost under his breath, "You're describing my last three years."

That was the aha. Not a fact he learned — a mirror he finally looked into. He had walked in believing his dependency was a sign of how much he was trusted. He walked out seeing it for what it was: a structure he had built, brick by brick, that could not run without him by design.

Here is what makes these three anchors so dangerous: each one feels like a virtue. The need to know feels like diligence. The need to solve feels like service. The need to be present feels like commitment. No one ever pulls a capable leader aside to warn him that his diligence has become a chokepoint. We reward all three — right up to the moment the leader becomes the single most reliable reason his organisation can't move without him.

"So what do I do?" Rajeev asked.

Not what he expected to hear. You cannot motivate your way out of a bottleneck you're proud of. Telling a leader to "delegate more" or "trust the team" is like telling someone to relax — it names the symptom and changes nothing. The fix is structural, not motivational.

"Let's take them one at a time," I said. "The need to know. You wait to bless every decision. What's the structural fix — not the resolution to trust people more, the actual mechanism?"

He sat with it. "I suppose... I'd have to decide in advance which decisions don't need me. Write them down. So nobody's waiting on my nod, because the rule already says they don't have to."

"That's it. You're not being generous. You're removing yourself from the path on purpose. What about the need to solve?"

This one took him longer. "That's harder, because solving is the part I actually enjoy." He paused. "Maybe the rule is — when someone brings me a problem, I don't get to answer first. They have to bring me their answer before I'm allowed to give mine."

"So you stop being the source of solutions," I said, "and become the editor of theirs."

He smiled at that. "I'd have to bite my tongue a lot."

"That's the discipline. And the last one — the need to be present?"

He already knew where this was going. "Someone owns the meeting. One name, not mine. And then I..." he hesitated, "...I actually leave the room."

"Not as a gesture," I said. "As a test. A system that only works while you're watching isn't a system. It's a performance — and you're the one audience it can't afford to lose."

He was quiet. He'd built all three fixes himself in under ten minutes. They weren't complicated. They had simply been unavailable to him as long as he believed the dependency was a compliment rather than a construction.

The leaders who break free are rarely the ones who tried hardest to let go. They are the ones who rebuilt the structure so that holding on was no longer possible.

 Lead less, by design. Build more, by structure. The goal was never a leader who works less because he cares less. It is an organisation that finally stops waiting for you — and a leader who, for the first time in years, can go dark for a week and come back to find everything still standing. It Is What It Is