Being Needed Is Not the Same as Being Effective

By Fred Bean
Founder & CEO, HotelPORT

There is a particular kind of satisfaction in being the person everyone needs. The difficult customer wants to speak with you. The team needs your approval. The partner trusts your judgment. When something gets complicated, someone inevitably says, “Let’s ask the boss.”

For a founder or executive, that can feel like evidence that you are doing your job. Sometimes it is. Experience matters, judgment has value, and leadership includes accepting responsibility for decisions other people should not have to carry. But there is a point at which being needed for everything becomes a problem. The organization’s capacity begins to depend on your personal availability, and your importance becomes difficult to distinguish from its dependence.

Being needed is not the same as being effective. A leader’s value should include how much the organization can accomplish without waiting for that leader.

The Reward for Solving Everything

The habit often begins for good reasons. In the early days of a business, the founder may hold most of the context, own the customer relationships, understand the product, and carry the financial risk. Getting involved is necessary. There may be no one else available to do the work, much less someone prepared to make the decision.

The trouble comes when the business grows but the operating habits remain the same. More people join, more customers arrive, and more opportunities emerge, yet decisions continue flowing toward the same person. What once allowed the company to move quickly starts limiting how quickly it can move.

This pattern can reinforce itself. When a leader steps in and solves a problem, the immediate situation improves. A customer gets an answer, a proposal goes out, or a stalled project moves forward. Everyone feels the relief. There is less immediate recognition for the slower work of teaching someone how to evaluate the problem, clarifying who has authority, or making sure the relevant information is available next time.

Over time, the organization can become very good at bringing problems to the leader. The leader, meanwhile, becomes increasingly convinced that personal involvement is what keeps everything working. Both may be responding rationally to a system they have helped create.

Judgment or Permission?

One of the most useful questions a leader can ask is simple:

Does this decision require my judgment, or does it merely require my permission?

Those are different needs. A major commitment, a sensitive personnel matter, or a decision that could materially change the company’s direction may deserve direct executive involvement. Other decisions reach the leader because authority has never been clearly assigned, boundaries remain vague, or employees have learned that making a reasonable choice is riskier than asking first.

A team can have capable people and still behave cautiously when the consequences of independent action are unpredictable. If a leader encourages ownership but routinely reverses decisions based on preferences no one could have known, people will adapt. They will seek approval earlier, offer fewer recommendations, and wait for instructions.

What looks like a lack of initiative may be a sensible response to the way leadership operates. Before asking why people will not take ownership, it is worth examining what happens when they do.

Delegation Requires More Than an Assignment

Handing someone a task does not automatically give them the ability to own the result. They also need to understand the objective, the constraints, the resources available, and the decisions they are authorized to make. Without that context, delegation can become a guessing exercise followed by a review of everything they guessed incorrectly.

Useful delegation makes the reasoning visible. Why does this customer matter? What tradeoffs are acceptable? Which commitments can we make? What would require escalation? What does a good outcome actually look like?

That takes time, particularly at the beginning. Explaining a decision may take longer than making it yourself, and allowing someone else to work through a problem can feel inefficient when you already see a solution. But if the same question keeps returning to your desk, the speed of your individual answer is a poor measure of progress. The more valuable result is someone becoming able to handle the next situation with sound judgment.

There will be mistakes. The goal is to create enough clarity that people can act responsibly, recognize their limits, and learn without turning every ordinary decision into an executive event.

The Business Cannot Live Entirely in Your Head

Dependence also develops when essential knowledge remains personal. A customer’s expectations, the history behind a pricing decision, an unwritten promise to a partner, or the reason a process works a certain way may be obvious to the founder and invisible to everyone else.

That information can feel too familiar to explain until someone makes a decision without it. Then the leader concludes that no one understands the business well enough to act independently. Yet understanding cannot spread if the context never leaves the person who holds it.

Documentation helps, but the objective is shared understanding. People need access to the reasoning behind the work, opportunities to participate in important conversations, and enough visibility to connect their decisions to the larger business.

Relationships need similar attention. A founder may remain central to a major customer or partner, while deliberately bringing others into the relationship. Over time, trust can extend to the team and the institution. That makes the relationship more durable and gives the customer more than one person who can help.

What Happens When You Are Unavailable?

A useful test is to examine where work stops when you are unavailable. Which customers cannot get an answer? Which commitments remain unresolved? Which projects pause? Which decisions sit untouched until you return?

Some of those delays will be appropriate. Others will reveal authority that was never assigned, information that was never shared, or confidence that was never developed. The purpose of the exercise is to identify where the organization needs to become more capable.

This also requires the leader to tolerate different methods. If every acceptable result must be achieved exactly as you would achieve it, the organization will remain limited by your habits as well as your time. Standards should be clear, particularly where quality, integrity, financial exposure, or customer commitments are involved. Within those standards, people need room to exercise judgment and improve how the work gets done.

A team that can only reproduce the leader’s preferences has limited room to surprise the leader with something better.

Build Beyond Your Personal Capacity

There is a personal adjustment here that deserves honesty. Becoming less necessary to daily operations can feel unsettling when solving problems has been central to your identity. The full inbox, constant calls, and stream of urgent questions can provide reassurance that you matter, even while making it difficult to do the work the organization increasingly needs from you.

As a business develops, leadership has to develop with it. More of the job becomes choosing direction, allocating resources, developing people, and addressing problems that cross the organization. That work requires attention, and attention is difficult to protect when every routine decision still needs your involvement.

In Contribute More Than You Consume, I argued that leadership should be measured in part by what becomes possible for others because someone occupied the seat. This is one practical test of that idea. Are people becoming more capable? Is judgment spreading? Can the organization respond, deliver, and improve with greater confidence?

There will always be decisions that belong to you and moments when leadership requires stepping directly into the problem. The discipline is recognizing which moments those are, while steadily reducing the number that exist only because everything has always come through you.

Being needed can be gratifying. Building something that can grow beyond your personal capacity is a more demanding achievement.

The next time someone says, “We need you to make this decision,” answer the immediate question if necessary. Then ask what would allow them to make the next