Bottleneck or Backbone? The Leadership Question We Should All Ask

There is a compliment we give people that I think deserves a little more scrutiny.

I don't know what we'd do without you.

We say it to brilliant colleagues. Dedicated managers. The person who always knows the answer, fixes the problem, remembers the detail and somehow keeps everything moving.

It sounds wonderful, doesn't it?

But I've been thinking about something.

What if being indispensable isn't always a sign of good leadership?

What if, sometimes, it's a warning?

I recently spoke about a question that has stayed with me:

Are you a bottleneck or a backbone?

Because the difference matters more than we might realise.

They can look remarkably similar

A bottleneck and a backbone can look almost identical from the outside.

Both are central to an organisation. Both are relied upon. Both appear essential.

But one makes progress possible.

The other makes progress dependent.

Think about the manager who needs to approve absolutely everything.

The team cannot make a decision without consulting them. Every document must pass through their hands. Every problem lands on their desk.

They are exhausted.

Their team is frustrated.

And everyone agrees that the organisation simply couldn't function without them.

But perhaps that is precisely the problem.

Somewhere along the way, being responsible for the work became being responsible for every decision.

And leadership quietly became control.

The danger of being needed

I think many of us enjoy being needed.

There is something reassuring about knowing that people depend on us. It makes us feel valuable. Capable. Important.

And there is nothing inherently wrong with that.

The problem begins when we start measuring our value by how difficult we are to replace.

We stop sharing knowledge because nobody else will do it quite like us.

We struggle to delegate because explaining the task feels harder than doing it ourselves.

We become frustrated when people make mistakes, forgetting that we developed our own expertise by being allowed to make some.

Eventually, the people around us stop taking initiative.

Not necessarily because they lack ability.

Sometimes because we have unintentionally taught them that initiative isn't welcome.

And then we complain that nobody can do anything without us.

Funny how that works.

A backbone does something different

Think about the human backbone.

It supports. It connects. It allows movement.

It does not need to perform every function of the body.

A good leader understands something similar.

Their job is not to be the cleverest person in every conversation.

It is to create an environment where other people can think.

Not to make every decision.

But to help people develop the judgement to make good decisions themselves.

Not to collect all the credit.

But to recognise the contributions that made success possible.

And certainly not to become so central that everything collapses when they take a holiday.

A backbone strengthens what surrounds it. A bottleneck restricts what passes through it.

That is a very different understanding of leadership.

But sometimes the system creates the bottleneck

There is another side to this conversation.

Not every bottleneck is caused by an individual who refuses to let go.

Sometimes organisations create them.

They give one person too much responsibility, too few resources and insufficient authority to distribute the work.

They fail to develop successors.

They reward people for constantly rescuing failing processes rather than fixing those processes.

Then, when everything becomes dependent on one exhausted employee, they call that person a problem.

That isn't fair.

If you want people to delegate, you must give them people who have the time, training and authority to take responsibility.

If you want managers to empower their teams, you must create a culture where reasonable mistakes are treated as opportunities to learn rather than reasons to punish.

And if you want resilience, you must stop building systems that depend on individual heroics.

A strong organisation should not need a hero every Monday morning.

There is a difference between supporting and carrying

This question also extends beyond formal leadership.

Many people become the backbone of their families, communities and workplaces.

They are the reliable ones.

The ones who organise, remember, anticipate, comfort, resolve and quietly absorb whatever everyone else cannot manage.

Women, in particular, can find themselves praised for carrying extraordinary amounts of invisible responsibility.

But being a backbone should not mean breaking your back.

There is a difference between supporting people and carrying responsibilities that properly belong to them.

Sometimes the most useful thing we can do is stop rescuing someone long enough for them to discover what they are capable of.

That is not unkindness.

It can be an extraordinary act of faith in another person's ability.

So, here's the question

If you are responsible for other people, formally or informally, consider this:

What happens when you are not there?

Do people feel confident making decisions?

Do they understand the purpose behind the work?

Have you shared what you know?

Can someone challenge your thinking without fearing your reaction?

Are the people around you becoming more capable because of your presence?

Or simply more dependent on it?

I don't think any of us gets this right all the time.

There are moments when I am sure we have all been the bottleneck.

The important thing is whether we recognise it.

Because leadership isn't simply about what we can achieve.

It is also about what becomes possible for other people because we were there.

And perhaps that is the real test.

If everything stops when you leave the room, you may be important. But if people become stronger because you were in the room, you have led.

So, I'll leave you with the question.

Are you the bottleneck or the backbone?

And perhaps more importantly:

What are you doing to make sure you know the difference?