Indispensable is a diagnosis, not a compliment

I have held a version of this as a rule for some time.

If an operator cannot leave for ninety days, they may have built a demanding job for themselves. They have not yet built a company that can operate without them.

That sounds like a delegation problem. Often it is not.

It is a decision problem.

A leader can delegate tasks while remaining the place where every meaningful decision eventually lands. The team prepares. The team recommends. The team waits. The leader approves.

From the outside, this can look like commitment. The founder is close to everything. Nothing important escapes their attention. People describe them as indispensable, usually as a compliment.

I have started to hear it as a diagnosis.

If the leader must be in every room, every decision path runs through one person. The capacity of the organization is then limited by the capacity of that person.

Add revenue. Add people. Add markets. The constraint does not move.

The symptoms are easy to misread. A full calendar looks like importance. A queue of people waiting for answers looks like authority. Long working hours look like ownership.

But the organization is not moving at the speed of the team. It is moving at the speed of the person everybody needs.

One useful way to see this is to count how often an outcome has to pass through the founder before it can be completed.

How many approvals?

How many meetings?

How many decisions return to the center because nobody is certain they are allowed to make them?

That number is a visible proxy for the decision tax inside the company. It rarely appears in the accounts, but everyone pays it.

The team pays by waiting.

Customers pay through slower responses.

The founder pays by becoming the bottleneck they are working hardest to overcome.

It is tempting to blame the people around the leader. They should take more ownership. They should be more decisive. They should stop escalating everything.

Sometimes that criticism is deserved.

Often, though, the team is responding accurately to the system around it.

Making a decision without the founder carries a visible cost if the decision goes badly. Waiting for the founder carries a quieter cost that is spread across the organization.

One person can be blamed for a wrong decision. Almost nobody is blamed for waiting.

Given those incentives, waiting is rational.

That is why delegation alone does not fix the problem. Delegating work without changing decision rights produces the same dependency with more steps.

The harder move is to make two things true at the same time.

Waiting must have a visible cost.

Being wrong after making a reasonable decision must be survivable.

Without the first, decisions keep traveling upward. Without the second, no encouragement to “take ownership” will change much.

This is also why the ninety-day test matters.

The question is not whether the company survives while the founder is away. Most companies can postpone enough decisions to survive an absence.

The better question is whether decisions continue to be made, at a comparable standard, without waiting for the founder to return.

That is a much less flattering test.

It reveals whether judgment exists throughout the organization or has been concentrated in one person. It reveals whether people have genuine authority or merely permission to prepare recommendations. It reveals whether the founder has built capability around them or dependence on them.

Being needed can feel like proof that you have built something valuable.

Sometimes it is proof that you have built something unable to move without you.

#DhandheKaFunda: Indispensable is a diagnosis, not a compliment.