When Strength Becomes a Liability

When my oldest was a newborn, I was the one who knew everything.

I knew what each cry meant, which positions worked, which routines helped, which interventions did not. I had figured it out through exhaustion, trial and error, and the particular attentiveness that comes from being the person who is always there.

The problem was that knowing everything made it very hard to let anyone else help.

Not because the help wasn't available. Because by the time someone else offered, I had usually already done it. Or I could do it faster than explaining it. Or I had figured out the right way, which was really just the way I had figured out, and anyone else's version looked inefficient by comparison.

So I kept doing everything. Everyone around me kept not learning how to do it. And I kept being the person who knew everything, did everything, and couldn't understand why I was so tired.

That is not really a parenting story. It is a leadership story.

I have watched versions of this play out in boardrooms, executive teams, and founder-led companies for years.

The person at the center is usually genuinely excellent. They know the business. They see problems quickly. They care about the quality of the work. They have often built their career by being the person who could figure it out and get it done.

That competence is real. It is also often exactly what got them promoted.

But eventually the job changes.

At some point, leadership is no longer mostly about producing the answer yourself. It is about building the judgment, capability, and systems that allow good answers to exist without you being personally responsible for every one of them.

That is where a real strength can quietly get the wrong assignment.

You were rewarded for being indispensable, so indispensability starts to feel like evidence that you are leading well.

But being needed and being effective are not the same thing.

The current Near Enemies framework names this pattern Leadership → Indispensability.

Leadership has jurisdiction over stewardship, direction, standards, and capability-building. It does not have jurisdiction to prove its own value by remaining necessary to every decision.

That distinction matters because indispensability is seductive. It looks like dedication. It looks like high standards. It looks like caring more than everyone else about getting it right.

And for a while, it can work beautifully.

The work gets done. The results are real. The leader can point to everything they are carrying as evidence of contribution.

Until the organization stops scaling because too much still has to pass through one person.

The leader who knows everything becomes the bottleneck. The executive who can do it better than everyone else becomes the reason no one else learns to do it. The founder whose judgment built the company becomes the limit on how much judgment the company can develop anywhere else.

The strength didn't disappear. It just started doing a job that didn't belong to it.

This is one of the places where my thinking about Near Enemies has changed.

I used to describe the framework mostly as what happens when a strength gets overused. Something good gets turned up too high until it starts producing an outcome you didn't intend.

That still happens. But I increasingly think the more useful question is not only whether the strength is being used too much. It is whether you are asking it to answer a question it cannot actually answer.

In this case, competence starts answering a question about leadership effectiveness. Being the person who can always solve the problem starts standing in for the harder work of building an organization that can solve problems without you.

That is a jurisdiction error.

The competence still belongs. The standards still belong. The experience still belongs. What has to change is what they are being asked to prove.

Back in the newborn years, the shift was painfully ordinary: letting someone else do it their way.

Not my way. A perfectly workable way.

That was harder than wanting help. I absolutely wanted help. What I had trouble tolerating was the learning curve that came with actually allowing someone else to get good at it.

My efficiency had become the standard. Any deviation from it felt like lowering the bar rather than building capacity.

Leaders do this all the time.

We say we want people to take ownership, then intervene before they can. We say we want stronger teams, then measure quality against the exact way we would have done the work. We say we want to scale, while continuing to derive part of our identity from being the person everyone still needs.

The corrective is not to become less capable. It is to restore jurisdiction.

Leadership should make the system stronger, not make the leader harder to remove from it.

So the question is not whether you are excellent at what you do.

It is whether your excellence is building capability around you, or quietly making you more indispensable.

What are you still personally excellent at that the people around you need the room to learn?