Are You Helping or Carrying What Isn’t Yours?

Why good leaders can become the bottleneck without realising it

Being helpful is usually a good thing.

Someone has a problem, so you help solve it. Something isn’t getting done, so you step in. A team member is struggling, so you take a little pressure off them.

No problem, right? It keeps things moving.

And if you’re capable, experienced and care about the result, there’s a fair chance you can sort it out faster yourself anyway.

But there’s a question worth asking:

At what point does helping become carrying?

There’s a subtle leadership trap here. The more capable you are at solving other people’s problems, the easier it is to become responsible for things that were never really yours to carry.

It usually starts with good intentions

Most leaders I work with who fall into this pattern aren’t trying to control everything.

Quite the opposite.

They care about their people. They don’t want someone struggling unnecessarily. They have standards they want maintained. And when the pressure is on, getting involved can seem like the most practical thing to do.

So they answer the question, fix the mistake and take the task back.

They have the conversation someone else should be having, follow up because nobody else has. Shall I go on?

Once or twice, that’s probably just being helpful.

But repeat it often enough and something interesting happens.

Your team gets very good at bringing problems to you.

And you get very good at carrying them.

A conversation from the coaching room

I see versions of this regularly.

A manager tells me they’re frustrated because people aren’t taking enough ownership.

They’re constantly answering questions, checking work, following things up and reminding people what needs to happen.

So I’ll often ask:

“What happens when they don’t take ownership?”

Quite often, the answer is that the manager eventually steps in.

Which makes sense. The work still has to get done.

But it also creates a pattern.

Someone drops the ball. The leader picks it up.

The team isn’t clear about what to do. The leader tells them.

Follow through isn’t hitting the mark. The leader quietly sorts it out.

Then we wonder why the person hasn’t developed greater ownership.

The uncomfortable question becomes:

Have they learned not to take ownership, or have we accidentally taught them that we eventually will?

That doesn’t mean leaving people to fail.

It means becoming much clearer about the difference between supporting someone to take responsibility and taking responsibility from them.

The bottleneck might be you

This is where good intentions can become expensive.

If every difficult decision needs you, every problem eventually comes back to you and every piece of work needs your final intervention, the team can only move as quickly as you do.

You become busy. They become dependent.

And interestingly, both sides can become frustrated with the other.

The leader thinks:

Why can’t they just take ownership?

The team may be thinking:

I’ll check with them before I do anything.

Neither usually intended to create that situation.

But leadership isn’t only about what we intend.

It’s also about the patterns our behaviour reinforces.

Sometimes the most useful thing you can do as a leader isn’t provide the answer, it’s handing the responsibility back.

Try one more question

The next time somebody brings you a problem, notice your first instinct.

Do you immediately start solving it?

Before you do, ask:

“What do you think we should do?”

Or:

“What’s your next step?”

Or perhaps:

“What do you need from me to move this forward?”

These aren’t magic coaching questions, and sometimes you absolutely should give someone direction.

The point is to notice whether you’re choosing to step in because that’s what the person needs or simply because stepping in has become your default.

There is a big difference.

Own one moment