DEV Community: Ben Webb

Decision Latency Is the Real Risk in Projects

Ben Webb — Tue, 27 Jan 2026 21:33:37 +0000

**Most projects don’t fail because the plan was wrong.

They fail because critical decisions take too long.

Not because no one knows what needs to be done.
Not because the data is missing.
But because the decision keeps getting delayed, softened, or deferred.

A week becomes a sprint.
A sprint becomes a phase.
A phase becomes “we’ll deal with it later.”

On paper, the project is still moving.
In reality, momentum is leaking out through indecision.

This is what I mean by decision latency.

It’s the time between when a decision becomes necessary and when someone is willing to own it. That gap is where most project risk is created.

What makes it dangerous is that it usually looks reasonable.

“We just need one more data point.”
“Let’s see how it trends.”
“We’ll take that offline.”
“We’ll re-baseline next cycle.”

Each of those sounds sensible in isolation. Together, they quietly stall the project.

Tools don’t fix this.

Dashboards, frameworks, and AI can improve visibility and analysis, but they don’t reduce decision latency. In some cases, they make it worse by giving people more reasons to wait.

More data.
More scenarios.
More options.

But no decision.

I’ve written before about why AI struggles with real project work. This is a big part of it. AI can tell you what usually happens next. It can’t tell you which trade-off you’re prepared to live with when the information is incomplete and the pressure is real.

That choice isn’t analytical.
It’s accountable.

Decision latency also hides behind good governance.

Steering committees meet. Papers are circulated. Risks are noted. Actions are captured. And still, the core decision gets deferred because no one wants to be the one who makes it too early.

The longer that goes on, the fewer options remain. By the time the decision is forced, the project has already paid the price.

Experienced project managers learn to recognise this early. They stop asking, “Do we have enough information?” and start asking a harder question:

“What happens if we don’t decide now?”

That’s usually when the real risk becomes visible.

Projects don’t need perfect information.
They need timely decisions with clear ownership.

Everything else is support.

Good Governance Can Still Produce Bad Projects

Ben Webb — Thu, 22 Jan 2026 23:42:06 +0000

Governance is supposed to protect projects.

Clear roles.
Defined forums.
Escalation pathways.

And yet, some of the most tightly governed projects deliver the worst outcomes.

Not because governance is wrong — but because it’s often mistaken for leadership.

I’ve seen projects with impeccable governance structures:

Steering committees that meet on schedule
Papers that are thorough and well-written
Decisions that are formally minuted

And still, everyone leaves the room knowing the real issue wasn’t addressed.

The problem isn’t the absence of governance.
It’s governance without consequence.

When decisions are spread across committees, subcommittees, and working groups, accountability becomes abstract. Everyone contributes. No one owns the outcome.

That’s how difficult decisions get reframed as:

“Let’s take this offline”
“We’ll note the risk”
“We’ll revisit next meeting”

On paper, the project is being governed.
In reality, it’s being deferred.

This is the same pattern I described when writing about how risk accumulates after plans are approved — not because people are careless, but because responsibility becomes diluted.

Good governance should sharpen decisions.
Instead, it often cushions them.

Experienced project managers recognise this early. They don’t try to remove governance — they re-anchor it.

They ask uncomfortable questions in the room:

Who is accountable for the outcome of this decision?

What happens if we’re wrong?

What decision are we avoiding because it will create friction?

Those questions don’t always make meetings smoother.
They do make projects more honest.

Because governance that protects people from discomfort rarely protects the project.

And the projects that succeed aren’t the ones with the most governance artefacts — they’re the ones where someone is clearly accountable when it matters.

Ben Webb — Project Manager
AIPM Australian Project Manager of the Year (2022)
https://benwebb.au

Green Status Is Not Control

Ben Webb — Wed, 14 Jan 2026 20:25:36 +0000

One of the most dangerous phrases in project delivery is:

“The project is green.”

Green status usually means reporting is compliant.
It rarely means the project is under control.

I’ve seen projects where:

Schedules were technically achievable
Risks were documented and reviewed
Governance forums met religiously

And yet — everyone in the room knew something wasn’t right.

The problem wasn’t visibility.
It was ownership.

On complex, public-facing projects, reporting often becomes a shield. It reassures stakeholders while quietly disconnecting them from the decisions that actually matter.

I’ve written before about why projects don’t fail quietly, and how hesitation compounds under pressure.

Green reporting can delay discomfort — but it doesn’t remove risk. It just defers it.

By the time status turns amber or red, options are usually gone. What follows is recovery theatre: workshops, re-baselines, and explanations that arrive too late to matter.

That’s why experienced project managers stop asking:
“What’s the status?”

And start asking:
“What decision are we avoiding because it will turn the status amber?”

Control shows up early:

When scope is confronted, not deferred
When risk is acted on, not logged
When someone is willing to own an uncomfortable call before it’s forced

Green status keeps everyone calm today.
Control is what keeps the project standing tomorrow.

Ben Webb — Project Manager
AIPM Australian Project Manager of the Year (2022)
https://benwebb.au

Most Project Risk Is Created After the Plan Is Approved

Ben Webb — Mon, 12 Jan 2026 09:18:44 +0000

There’s a comforting moment in most projects when the plan is signed off.

The schedule is locked.
The budget is agreed.
Governance is in place.

Everyone exhales.

That’s usually when the real risk begins.

Most project risk isn’t born in planning. It’s created later — in the small, reasonable decisions that slowly move the project away from what was approved.

A scope change here that “won’t affect the critical path.”
A sequencing tweak there to “help the contractor.”
A risk accepted because “we’ll manage it operationally.”

None of these decisions feel reckless in isolation. In fact, most are well intentioned. The problem is that they rarely come with a re-alignment of accountability.

I’ve written before about how green reporting can mask control, and how projects drift while everything still looks compliant.
👉 (INTERNAL LINK to “Green Status Is Not Control”)

The danger isn’t change itself.
Projects have to adapt.

The danger is change without ownership.

When plans evolve but accountability doesn’t, risk compounds quietly. The baseline still exists, but no one is truly managing to it anymore. The project hasn’t failed — it’s just no longer being actively controlled.

This is where experienced project managers behave differently.

They don’t treat the approved plan as a historical artefact.
They treat it as a live contract with reality.

Every deviation triggers a question:
Who owns the consequence of this change — not just the action, but the outcome?

That mindset is what separates adaptation from drift.

Because most projects don’t blow up suddenly.
They unravel slowly, decision by decision, after everyone thought the hard part was over.

Ben Webb — Project Manager
AIPM Australian Project Manager of the Year (2022)
https://benwebb.au

Where do you see accountability break down first on complex projects — governance, sponsorship, or delivery?

Ben Webb — Wed, 07 Jan 2026 22:34:52 +0000

Why Projects Don’t Fail Quietly

Ben Webb — Wed, 07 Jan 2026 22:32:48 +0000

There’s something different about delivering projects.

They don’t fail in private.
They don’t drift unnoticed.
And they rarely give you the luxury of “learning lessons” quietly at the end.

Projects fail in public.

Whether it’s IT, infrastructure, events, hospitality, or public-facing assets, the environment is unforgiving. Timelines are fixed. Interfaces are dense. Stakeholders are vocal. Media interest is never far away.

That changes how projects behave.

You can’t hide behind reporting for long.
You can’t rely on optimism.
And you definitely can’t defer hard decisions without consequences.

I’ve seen plenty of projects in Sydney where governance existed, but decision rights were unclear. Reporting was frequent, but control was weak. Risk registers were immaculate, but risk was unmanaged.

This is something I’ve written about before when discussing project management in Sydney and why “best practice” often collapses under pressure →
👉 https://dev.to/ben_webb_projectmanager/ben-webb-sydney-project-management-1061

The issue is rarely capability. It’s timing.

Decisions that should be made early get delayed because they’re uncomfortable, political, or inconvenient. By the time they’re unavoidable, options are gone and recovery becomes theatre.

In cities like Sydney, delivery rewards early clarity over late perfection. Accountability over consensus. Judgement over process.

I’ve seen the same pattern repeat across Sydney-based projects — from infrastructure to live events — where everyone knows a decision is needed, but no one wants to own it yet.

That hesitation is usually what decides the outcome.

It’s why experienced project managers eventually stop asking “what framework should we use?” and start asking a more uncomfortable question:

Who is accountable for this decision today — not eventually?

For more writing on project delivery, governance, and accountability, see:
https://dev.to/ben_webb_projectmanager

Ben Webb — Project Manager (Sydney)
AIPM Australian Project Manager of the Year (2022)
https://benwebb.au

Ben Webb - Sydney - project Management

Ben Webb — Sun, 04 Jan 2026 20:48:46 +0000

Writing and publishing on modern project delivery, governance, and accountability—focused on Sydney-based infrastructure, events, and high-risk environments.

Why Experienced Project Managers Stop Believing in “Best Practice”

Ben Webb — Thu, 01 Jan 2026 00:49:40 +0000

After a certain point in your career, “best practice” stops being reassuring.

Not because it’s wrong — but because it’s incomplete.

Most project failures I’ve been called into weren’t caused by a lack of frameworks. They failed because decision-making collapsed under pressure.

Governance existed on paper. Reporting was immaculate. The schedule looked convincing.

And yet — everyone knew the truth.

The hard decisions were being avoided.

Real projects don’t fail because people don’t know what to do. They fail because accountability gets diluted across committees, dashboards, and optimism.

In high-risk environments — infrastructure, live events, tourism, public-facing assets — there is no hiding place. Something either works on day one, or it doesn’t.

That’s why experienced project managers eventually stop asking:
“What’s the framework?”

And start asking:
“Who is actually accountable for this decision — right now?”

Because delivery doesn’t respond to intention.

It responds to decisions.

And the projects that succeed are rarely the most sophisticated.

They’re the ones where someone was willing to be uncomfortable early — so everyone else didn’t have to be later.

Ben Webb — Project Manager
AIPM Australian Project Manager of the Year (2022)
https://benwebb.au