Some leaders are incredibly good at helping.
Sometimes, a little too good.
A team member brings them a problem, so they solve it. Someone gets stuck, so they step in. A customer issue escalates, so they take over. A deadline starts slipping, so they jump in & make sure it gets done.
From the leader’s perspective, this feels responsible. Helpful, even.
The problem is that if you keep rescuing people, you can accidentally train them not to own the problem in the first place.
And that is where accountability starts to disappear.
Rescue Usually Starts With Good Intentions
Most leaders do not step in because they want to create dependence.
They do it because they care about the outcome. They want the customer looked after, the deadline met & the team to succeed. If they already know how to fix something, it can feel inefficient to stand back & watch somebody struggle.
That instinct is understandable.
But there is an important difference between supporting someone & taking the problem back from them.
Support sounds like:
“What do you think needs to happen?”
“What have you tried?”
“What decision do you need from me?”
Rescue sounds like:
“Leave it with me.”
That one phrase can feel efficient in the moment.
Over time, it can become very expensive.
Every Rescue Teaches Something
People learn very quickly how a business really works.
If every difficult problem eventually gets handed back to the founder, they learn that the founder is still the real decision-maker.
If every missed deadline results in a leader stepping in to finish the work, they learn there is a safety net.
If every uncomfortable customer conversation gets escalated upwards, they learn that somebody more senior will eventually carry the difficult part.
You may think you are simply solving a problem.
But you are also teaching a behaviour.
The lesson becomes:
“When this gets hard enough, somebody else will take over.”
That is the opposite of ownership.
Accountability Requires Space
One of the uncomfortable parts of building accountability is giving people enough room to solve things themselves.
That does not mean abandoning them.
It means resisting the urge to answer every question before they have thought it through. It means allowing someone to wrestle with a problem for a little longer. It means giving a leader enough authority to make a decision, even if it is not exactly the decision you would have made.
Sometimes it even means allowing a small mistake to happen because the learning is more valuable than another rescue.
That can be difficult for experienced founders & leaders because they often see the answer quickly.
But just because you can solve the problem faster does not mean you should.
If you always provide the answer, your team gets faster at asking you.
Not at thinking.
The Founder Can Become the Shortcut Around the Structure
This pattern is particularly common in founder-led businesses.
The founder has years of experience, context & knowledge. They know the customers, remember the history & can often cut through a problem faster than anybody else.
That makes them incredibly useful.
It can also make them the shortcut around the structure.
A team member does not need to work through an issue with their manager because they can ask the founder.
A department head does not need to make the decision because the founder will make it.
A customer does not need to trust the team because they know they can go straight to the owner.
Over time, the business develops a strange contradiction.
There is an Accountability Chart® . There are leaders. Roles are defined.
But when something genuinely matters, everybody still looks upwards.
That is not delegation.
It is dependency with an organisational chart around it.
Clear Seats Need Real Authority
If someone owns a seat, they need enough authority to own the outcomes that come with it.
This is where leaders sometimes create an impossible situation.
They tell someone:
“You are accountable for this function.”
Then continue approving every meaningful decision inside it.
The person has accountability without authority.
So they become cautious. They escalate more. The founder gets frustrated because they are still being asked everything, while the team member becomes frustrated because every important decision still requires permission.
Eventually, everybody starts talking about confidence, initiative or leadership capability.
Sometimes the problem is much simpler.
The leader never actually let go.
Real accountability requires clarity around what the person owns, which decisions they can make & when something genuinely needs to come back up.
A Level 10 Meeting® Should Not Become a Rescue Centre
You can see the same pattern in leadership meetings.
Someone brings an issue to the Level 10 Meeting® & immediately looks to the founder or leadership team for the answer.
Ten minutes later, everybody has helped solve a problem that perhaps should have been owned within one seat.
That is not always wrong. Some issues genuinely require the combined thinking of the leadership team.
But if it happens constantly, it is worth asking why.
- Is the person clear about what they own?
- Have they already tried to solve the problem themselves?
- Do they need a leadership-level decision?
- Or are they simply looking for someone else to take responsibility?
The leadership team should use the Issues Solving Track® (IDS®) to solve issues that genuinely belong at leadership level.
It should not become the place where individual leaders regularly hand back problems they were hired to own.
Help People Think Instead of Giving Them the Answer
One of the most useful shifts a leader can make is replacing immediate answers with better questions.
Instead of answering “What should I do?”, ask:
“What do you think we should do?”
Before stepping in, ask:
“What have you already tried?”
If someone wants you to choose for them, ask:
“What are the options?”
And instead of taking ownership of the decision, ask:
“What do you recommend?”
This does two things.
- It forces the person to think before escalating.
- It gives you visibility into how they are thinking.
You may discover they are perfectly capable of making the decision & simply needed confidence.
Or you may uncover a genuine capability gap that needs development.
Either way, you learn much more than you would by simply answering the question for them.
Be Clear About What Should Come Back Up
Healthy delegation does not mean every decision stays at the lowest level forever.
Some things should absolutely be escalated.
There may be financial thresholds, legal or reputational risk, major people decisions, strategic implications or customer issues with significant consequences.
The important thing is clarity.
- What does this person own?
- What decisions can they make without approval?
- When should they ask for input?
- What genuinely needs to come back to the leadership team?
If those boundaries are vague, people tend to do one of two things.
They escalate everything.
Or they make decisions they were never supposed to make.
Neither is particularly useful.
Clear decision rights make accountability much easier.
Stop Rewarding Escalation
There is another subtle behaviour worth watching.
Sometimes leaders complain that their team keeps escalating problems while simultaneously rewarding exactly that behaviour.
Someone arrives with a messy issue & the leader immediately jumps in.
Problem solved.
Everyone feels relieved.
So the next time something similar happens, what do you think that person will do?
Probably escalate it even sooner.
If you want people to take greater ownership, the response to escalation has to change.
Not every time, obviously. Genuine emergencies exist.
But as a general rule, the first response should not be:
“I’ll fix it.”
It should be:
“Talk me through how you’re thinking about it.”
That keeps ownership where it belongs while still giving the person support.
Accountability Is Not the Same as Leaving People Alone
There is an important balance here.
The answer is not to become deliberately unhelpful.
Good leaders coach. They provide context, remove obstacles, give feedback & step in when the stakes genuinely require it.
Accountability is not saying:
“Your problem. Good luck.”
It is helping people build the capability & confidence to own the responsibilities attached to their seat.
The goal is not less support.
It is better support.
Support that strengthens ownership rather than replacing it.
Watch What Happens When You Step Back
One of the quickest ways to see where dependency exists is to stop answering so quickly.
Pause.
Ask the question back.
Send the decision back to the person who owns it.
You may be surprised by what happens.
Some people will step up almost immediately.
Others will become uncomfortable because they have grown used to somebody else making the final call.
That discomfort is useful information.
It may reveal where a seat is unclear, where capability needs strengthening or where the business has become too dependent on one person.
Do not automatically rush in to remove that discomfort.
Sometimes that is exactly where growth starts.
If You Want Ownership, Stop Taking It Back
Every rescue comes with a trade-off.
You may get a faster answer today.
But you may also make yourself more necessary tomorrow.
If your goal is a business where people think, decide & take genuine accountability, they need the opportunity to own problems all the way through.
That means leaders have to become comfortable with not being the answer to every question, not correcting every decision & not stepping in at the first sign of difficulty.
The irony is that many leaders say they want a more accountable team while continuing to behave in ways that make themselves indispensable.
You cannot have both.
So, the next time someone brings you a problem, resist the instinct to solve it immediately.
Ask what they think.
Ask what they have tried.
Ask what they recommend.
Then decide whether they genuinely need your help, or whether your help is about to take ownership away from them.
Because the more you rescue, the less they own.