Projects Don’t Fail Because of Complexity — They Fail Because Decisions Are Avoided
Ben Webb - Project Manager
I’m Ben Webb — an award-winning Australian Project Manager working across infrastructure, tourism, hospitality, major events and complex public-facing projects. I’ve delivered nationally significant programs including Aseet AI, Smart Parking, Park and Pay, Sydney Zoo, ICC Sydney, the Northern Beaches B-Line, Sydney Harbour Bridge tourism operations, and high-risk televised events involving Heads of State. I write about why projects really fail, decision-making under pressure, delivery accountability, and what happens when theory meets reality.
There’s a comforting myth in project delivery that failure comes from complexity.
Too many stakeholders.
Too much scope.
Too many dependencies.
Too many unknowns.
It’s neat. It’s defensible. And it’s usually wrong.
Most projects don’t fail because they’re complex. They fail because the people responsible for them avoid decisions when decisions are hardest to make.
Complexity is predictable. Avoidance is not.
Complexity can be planned for.
It can be modelled, staged, governed, and managed.
What can’t be managed is hesitation disguised as process.
I’ve watched projects stall for months not because the solution wasn’t known, but because no one wanted to be accountable for choosing it.
Instead, we get:
Another workshop
Another paper
Another review
Another “alignment session”
All in the name of diligence.
All quietly postponing the same decision everyone knows is coming.
The most dangerous phrase in a project
“There’s no rush — let’s get more information.”
On the surface, it sounds responsible.
In reality, it’s often a signal that leadership has stepped back from ownership.
Information is rarely the blocker.
Conviction is.
By the time a project reaches delivery, there is almost always enough data to choose a direction. What’s missing is the willingness to accept the consequences of that choice.
So the project drifts.
Schedules slide.
Costs creep.
Risk compounds quietly in the background.
And when things eventually unravel, complexity gets blamed — not indecision.
Governance doesn’t replace leadership
Strong governance is essential.
But governance is not a substitute for decision-making.
Frameworks don’t deliver projects.
Steering committees don’t deliver projects.
Reporting doesn’t deliver projects.
People do.
The best governance structures I’ve worked within had one thing in common: clarity about who decides, when they decide, and what happens if they don’t.
Where that clarity doesn’t exist, governance becomes a shield.
A way to diffuse responsibility instead of exercising it.
Projects move when someone chooses
Every successful project I’ve been part of had moments where certainty was impossible.
Incomplete information.
Competing interests.
Real risk.
Progress only happened when someone was prepared to say:
“This is the call. We’ll manage the consequences.”
Not perfectly.
Not comfortably.
But decisively.
That’s not recklessness — it’s leadership.
The real question every project leader should ask
When a project stalls, the most honest question isn’t:
“What’s changed?”
It’s:
“What decision are we avoiding?”
Answer that, and progress usually follows very quickly.
Avoid it, and no amount of process will save the project.
If you want to connect or read more about project delivery, governance, and accountability under pressure:
Website: https://benwebb.au
Blog: https://benwebb.blog
LinkedIn: https://linkedin.com/in/bmwebb