The Difference Between Being Needed and Being a Good Leader

There is a sensation that arrives when your phone rings and it is the third person this week who cannot proceed without you, and the sensation is not entirely unpleasant. It confirms something. You are load-bearing. The thing would not hold without you in it, and the evidence arrives daily, and after a few years of this it becomes difficult to distinguish from doing the job well.

It is not the same thing. In many cases it is the opposite, and the distinction is worth drawing carefully because the two conditions feel identical from the inside.

Being needed means that work stops without you. Leading well means that work continues. Those are different states of an organization and only one of them is an accomplishment.

How the confusion develops

Nobody sets out to become a bottleneck. The condition accumulates through a series of decisions that are individually correct and collectively ruinous.

Early on you are the person who knows how things work, and answering the question yourself is genuinely faster than explaining it. You do that a few hundred times, and each instance saves twenty minutes, and none of them builds anyone's capacity to answer the question without you. The efficiency is real in the moment and it is borrowed against the future, and the interest compounds quietly.

Then there is quality. You care about the work, the version someone else produces is not the version you would have produced, and revising it yourself is faster than sending it back with an explanation of what is wrong. This is the most defensible-sounding of the mechanisms and the most damaging, because it teaches the person that her draft is a first pass you will fix rather than a deliverable she owns.

And there is the part nobody says out loud. Being needed is affirming, particularly for women who spent years being overlooked and now find themselves central to something. The affirmation is real and it is a bad guide to decision-making, because the behaviors that maximize how needed you are and the behaviors that maximize what your team can do point in opposite directions.

What it costs

The costs land on three parties and only one of them is you.

Your people stop developing. A person who has never made a decision without checking has not learned to make decisions, and after three years in that position she is less capable than when she arrived, which is not a failure of her ability. Development requires the possibility of being wrong, and a manager who removes that possibility has removed the mechanism.

The organization accumulates risk it cannot see. Everything routed through one person is a single point of failure, and the failure mode is not usually dramatic. It is a manager on vacation and four decisions waiting, then a manager ill for two weeks and a quarter slipping, then a manager departing and a year of institutional knowledge leaving with her. Organizations rarely price this until it materializes.

And you pay, though usually last. A woman who is needed for everything cannot take a real holiday, cannot be ill without consequence, cannot take a role that would require her to leave her current one intact behind her. That last constraint is the one that ends careers quietly. She cannot be promoted because she cannot be replaced, which is presented to her as evidence of her value and functions as a ceiling.

The distinction in practice

The useful test is what happens in your absence, and most people have the data and have not looked at it.

Think about the last time you were away for a week. Did decisions wait for your return, or did they get made? Did anything go wrong, and if so was it a genuine error of judgment or was it that nobody felt permitted to act? Did you return to a backlog of things that required you specifically, or to a backlog of things that required someone and you were the default?

The second version of each question describes a permission problem rather than a capability problem, and permission problems are entirely the manager's to solve. People who are capable and not permitted look exactly like people who are not capable, which is why so many managers conclude their teams cannot handle things when what they have actually built is a team that is not allowed to.

What to change

The correction is slower than the diagnosis and it is mostly a matter of tolerating worse outcomes for a period.

Decide what decisions genuinely require you and write the list down. It will be shorter than your current behavior implies, and most managers doing this exercise discover that they are involved in a category of decisions where their involvement adds nothing except delay. Announce the list, which converts it from an intention into something people can hold you to.

Then let things be done less well than you would do them. This is the actual work and it is uncomfortable in proportion to how much you care. A person who produces something at seventy percent of your standard and owns it will reach ninety within a year. A person whose work you rewrite stays at seventy permanently, because she has never received the information that would move her.

Change what you respond to. When someone brings you a problem, the default response should be a question about what she thinks rather than an answer. This is slower on each occasion and it is the entire mechanism by which judgment gets built. Most managers know this and abandon it under time pressure, which is when it matters most.

And be deliberately unavailable sometimes. Not as a test, and not punitively, but because a team that has never had to proceed without you has never had the chance to discover that it can. Take the holiday, do not check the messages, and see what the organization does. Whatever happens is information you needed.

What good looks like

The clearest description I know of effective leadership is that it produces an organization that performs well when the leader is not present. Not one that performs adequately, and not one that survives, but one that operates at standard because the judgment has been distributed rather than concentrated.

This is difficult to measure and invisible to most reward systems, which continue to favor the manager who is visibly essential over the one whose team functions smoothly without her. That is a real problem with how organizations evaluate leadership, and it is not a reason to manage badly, particularly since the smoothly functioning version is what eventually makes the woman running it promotable.

There is a version of the sensation I described at the start that is worth having. It is quieter and it arrives less often. It is the week you were away and nothing broke, and the decision you would have made was made by someone else, and made well, and she did not need to tell you about it afterward because it was hers.

That feels like considerably less than being needed. It is what you were trying to build.