Why Competent Leaders Accidentally Create Decision Bottlenecks
11 August 2026 | 6 minute read
Decision bottlenecks aren't always caused by controlling leaders. Sometimes they're created by capable leaders responding sensibly to something that went wrong; and never revisiting the response. Here's how one GM lost 11 hours a week to decisions his team could have been making without him.
There is a particular kind of leadership problem that rarely looks like a leadership problem at first. It looks like diligence.
A GM I worked with was in the middle of a restructure. Three site managers reported to him. His executive team wanted weekly certainty. And every variation request over $50,000 landed on his desk for approval.
That was what the delegation matrix said. The problem was the matrix had been designed when the business was half the size.
So the GM was personally reviewing decisions that an experienced site manager could often have made in five minutes.
He knew it, but he also wasn't particularly keen to change it. Not because he was a control freak or because he didn't understand delegation. And certainly not because he needed another leadership course explaining the importance of empowerment.
One of his site managers had previously approved a contractor variation that blew a hole in the quarter.
That event changed something in him. He no longer quite trusted the judgement being exercised without him in the room.
So he kept the control, and the queue kept growing.
When good judgement creates dependency
The site managers adapted. They stopped expecting quick responses and started batching their requests into fortnightly emails because sending them individually wasn't getting decisions any faster. By then, the approval process wasn't simply slowing decisions. It was changing behaviour. People had learned that decisions travelled upwards. The GM had learned that oversight felt safer than delegation, and the organisation had quietly built itself around his availability.
By the time we sat down together, he was spending around 11 hours every week moving approvals through the business. Meanwhile, the restructure; the strategic work that genuinely required his judgement, was happening at 6am before everyone else logged on. This is how competent leaders accidentally become decision bottlenecks. Not because they can't let go but rather that it is often because at some point, holding on made complete sense.
The bottleneck isn't always where you think it is
The obvious response would have been to rewrite the delegation matrix, and yes, the matrix needed attention. But a new document wouldn't have solved the real problem. Because the $50,000 threshold wasn't what was keeping those decisions on the GM's desk. Trust was.
One poor decision had become evidence about decision-making more broadly. Instead of:
That particular judgement was poor. What needs to change?
the leadership response had gradually become:
I need visibility over these decisions.
Understandable but also very expensive.
The breakthrough wasn't a new governance process. It was the GM being able to say, out loud, that the contractor blowout had caused him to distrust judgement generally rather than that particular decision specifically. And now he was paying for that response twice: with his own time and with his team's momentum.
Leadership friction often starts with something sensible
This is what makes leadership friction difficult to spot. It rarely begins with someone doing something obviously ridiculous.
A leader gets copied into an email because something went wrong.
An additional approval is introduced because a risk was missed.
Another meeting is created because communication broke down.
A decision gets escalated because somebody once made the wrong call.
Each response makes sense in isolation but often nobody comes back six months later and asks: do we still need this? And therefore, the temporary safeguard becomes the permanent way of working.
Eventually you have capable people waiting for decisions they should be making themselves, while the most senior people in the organisation spend their days approving work other people are perfectly capable of doing.
Everyone is busy. Governance looks reassuringly robust. Yet execution gets slower.
Before you fix the process, find out what the process is protecting
When I see a senior leader becoming a decision bottleneck, I'm less interested initially in whether they need to delegate more and I'm more interested in why the decision ended up with them in the first place.
What happened that made this level of oversight feel necessary?
What are they worried will happen if they step out?
Is the issue genuinely capability? Or has one failure changed their perception of everyone's capability?
What evidence would they need to trust the decision elsewhere?
And perhaps most importantly:
What work only they can do isn't getting done while they remain involved here?
That last question changes the economics of the conversation. Eleven hours a week moving approvals doesn't just cost eleven hours, it costs whatever wasn't happening during those eleven hours. In this case, that was leadership of a significant restructure.
The goal isn't less leadership. It's leadership in the right place.
There are absolutely decisions senior leaders should own. The ones with high consequence, high ambiguity, enterprise-wide implications. Decisions where experience and judgement genuinely change the quality of the outcome. The problem is when senior involvement becomes the default rather than a deliberate choice. Because every decision a leader unnecessarily pulls upwards does something else: it teaches the organisation accountability only lives with leader, not where the organisational chart says it lives. Where behaviour says it lives.
And once people learn that, telling them to “take more ownership” won't change much. The system has already taught them otherwise. This is why I pay so much attention to leadership friction: the organisational drag between what you've decided needs to happen and what actually happens. Sometimes that friction is obvious. Sometimes it's an extremely capable GM, working at 6am because his day is full of decisions he shouldn't still be making.
Behaviour is evidence.
And occasionally the most useful leadership question isn't: what decision do I need to make?; it's: why does this decision still need me?
Key Takeaways
Decision bottlenecks are often created by capable leaders responding sensibly to something that went wrong, and never revisiting the response.
A single poor decision can quietly shift a leader from trusting judgement to requiring oversight.
When decisions consistently travel upwards, teams learn that accountability sits higher than the organisational chart suggests.
More delegation isn't always the answer; leaders need to understand what their involvement is protecting against.
Temporary safeguards can become permanent leadership friction long after the original risk has passed.
The real cost of unnecessary oversight isn't just the leader's time; it's slower decisions, reduced team ownership and the strategic work only that leader can do being pushed aside.
A useful question for any senior leader is: why does this decision still need me?
Frequently Asked Questions
Why do senior leaders become decision bottlenecks?
Often it isn't because they are unwilling to delegate. Previous mistakes, unclear accountability, outdated governance or concerns about capability can cause decisions to gradually move upwards. Over time, the organisation learns to depend on senior approval even when that involvement is no longer necessary.
How can leaders identify a decision bottleneck?
Look for repeated approvals sitting with the same senior leader, decisions waiting for their availability, teams batching requests, increasing escalation and senior leaders doing strategic work outside normal hours because operational decisions consume their day.
Does fixing decision bottlenecks mean delegating more?
Not necessarily. The first question is why the decision requires senior involvement. Sometimes the answer is capability or genuine risk. In other cases, the process is protecting against a problem that no longer exists. Effective delegation requires clarity about decision rights, capability, risk and trust.
What is leadership friction?
Leadership friction is the organisational drag that develops between intention and execution. It can appear through slow decisions, unnecessary approvals, unclear accountability, repeated conversations, excessive escalation and leadership behaviours that inadvertently make execution harder.
Additional Resources
About Louise
Louise Zawada is an executive coach, change strategist and leadership mentor based in Perth, Western Australia.
She works with senior leaders and executive teams navigating complex organisational change, helping them close the gap between strategy and execution by strengthening executive judgement, reducing leadership friction and improving the quality of conversations that drive performance.
Her work spans mining and resources, government, infrastructure and corporate organisations, where she coaches leaders to make better decisions under pressure, build trust through uncertainty and lead change with greater confidence and clarity.
Louise is the creator of the Leadership Friction framework and writes regularly on executive judgement, organisational legibility and the behavioural evidence that determines whether strategy becomes action.
If you're leading significant change and need a trusted thinking partner, connect with Louise or book a conversation.