Ben Webb: Why Project Governance Fails Before Projects Even Start

 

Governance is usually blamed last. When projects fail, attention goes first to budgets, schedules, contractors, or market conditions. Governance is treated as a background function — important, but passive. In reality, governance is often the original fault line. Most major project failures don’t begin on site or during delivery. They begin quietly, upstream, when authority is blurred, decision rights are unclear, and governance structures are designed to look impressive rather than work under pressure.

I’ve stepped into enough troubled projects to recognise the pattern early. The paperwork is usually immaculate. The committees are well staffed. The reporting cadence is relentless. And yet, when you ask a simple question — who can actually decide this? — the room goes quiet.

That silence is the sound of governance failure.

Governance theatre versus governance reality

Many projects suffer from what I call governance theatre. On the surface, everything looks robust. There are steering committees, subcommittees, working groups, escalation pathways, and assurance processes layered on top of one another. Slide decks are produced. Minutes are taken. Decisions are “noted”.

What’s missing is authority.

Real governance is not about how many people attend meetings. It’s about who has the mandate to make decisions when trade-offs are required. Governance theatre focuses on optics. Governance reality focuses on outcomes.

The danger with theatre is that it creates confidence without capability. Senior leaders believe the project is controlled because governance artefacts exist. Delivery teams believe decisions are coming because escalation paths are documented. In practice, no one is empowered to act decisively without consensus — and consensus is rare when risk is high.

Committees without authority are just delays with agendas

Committees are not inherently bad. Used properly, they bring perspective, oversight, and challenge. Used poorly, they become decision laundromats — places where responsibility is washed until it emerges diluted and unrecognisable.

I’ve seen committees that can review, recommend, endorse, and comment — but not decide. Every outcome must be socialised, deferred, or escalated again. The result is predictable: delivery slows, risk accumulates, and frustration grows.

The irony is that these structures are often created to manage risk. In reality, they amplify it.

When no one owns the final call, decisions default to the safest, slowest option. Opportunities are missed. Issues linger. Teams learn quickly that momentum is punished and caution is rewarded.

That is not governance. That is avoidance.

Escalation paths that don’t work when you need them

Most governance frameworks include escalation pathways. On paper, they are logical and orderly. In practice, they are often unusable at the moments that matter most.

Escalation assumes:

  • People are willing to escalate

  • Senior forums are available when needed

  • Decisions will be made quickly once escalated

Those assumptions rarely hold under pressure.

In politically sensitive or high-visibility projects, escalation carries personal risk. People hesitate. Issues are softened. Language is moderated. By the time something reaches the top, it’s often stripped of urgency or context.

Effective governance reduces the need for escalation by pushing authority closer to the point of impact. Weak governance centralises power but delays action.

Governance fails when it’s designed for reporting, not delivery

A common mistake is designing governance structures around reporting cycles rather than delivery needs. Monthly meetings, quarterly reviews, and stage-gate approvals feel orderly, but projects don’t experience risk on neat schedules.

Delivery requires:

  • Fast decisions when conditions change

  • Clear authority when trade-offs emerge

  • Confidence that decisions will be backed, not revisited endlessly

Governance that can’t keep pace with delivery becomes a constraint rather than a control.

Some of the most effective projects I’ve worked on had surprisingly simple governance models. Few forums. Clear mandates. Direct access between decision-makers and delivery leads. Less documentation, more clarity.

The sophistication was in the judgment, not the structure.

The hidden cost of weak governance: erosion of trust

When governance fails, trust erodes long before schedules slip or budgets blow out.

Delivery teams lose confidence that decisions will be made in time. Executives lose faith in reporting because issues keep reappearing. Stakeholders become frustrated by repetition without resolution.

Eventually, behaviour changes. Teams stop raising issues early because nothing happens. Problems are worked around rather than resolved. Risk is managed informally, outside the governance framework entirely.

At that point, governance still exists — but only as ceremony.

What effective governance actually looks like

On projects where governance works, you can feel it.

  • Decisions are clear.
  • Authority is visible.
  • Escalation is rare but effective.
  • Meetings end with outcomes, not actions.

Effective governance has a few consistent characteristics:

  • Decision rights are explicit and personal, not role-based abstractions

  • Forums exist to decide, not just to review

  • Delivery leaders have direct access to decision-makers

  • Once decisions are made, they are held — not endlessly reopened

Most importantly, effective governance is designed with the expectation that things will go wrong. It anticipates pressure rather than being overwhelmed by it.

Governance is a leadership issue, not a structural one

It’s tempting to treat governance as a design problem — something that can be fixed with better frameworks, clearer diagrams, or additional assurance layers.

In my experience, governance failures are rarely structural. They are leadership failures.

Structures don’t make decisions. People do.

Strong leaders use governance to enable delivery. Weak leaders use governance to avoid ownership. The difference is subtle on paper and obvious in practice.

Why this matters before a project even starts

By the time a project is underway, governance failure is hard to correct. Behaviours are set. Expectations are formed. Authority — or the lack of it — is already understood.

That’s why governance matters most before delivery begins.

If authority is unclear at the start, it will not magically appear later. If accountability is blurred early, it will not sharpen under pressure. Governance doesn’t fail suddenly. It fails quietly, early, and predictably.

Projects don’t collapse because governance breaks. They collapse because governance was never fit for purpose in the first place.

Comments

Post a Comment

Popular posts from this blog

Ben Webb on Project Management: The Moment Projects Are Actually Won or Lost

  Projects are rarely won at handover. They’re won much earlier — often before construction starts, before systems are built, before the first dollar is spent. They’re won (or lost) in the first set of decisions . Early decisions carry disproportionate weight The earliest choices lock in: Risk exposure Delivery flexibility Commercial leverage Stakeholder alignment Once those decisions are made — or avoided — everything downstream becomes harder to change. Late-stage heroics get attention. Early-stage clarity saves projects. Why early decisions get delayed At the start, everything feels possible. There’s optimism. Optionality. A desire not to “close doors”. So teams delay commitment. They keep options open. They push decisions downstream. What they’re really doing is exporting risk to the future , where it’s more expensive, more visible, and harder to manage. What experienced delivery leaders do They accept a simple truth: You never have perfect information. So they: Decide with wha...
Read more

Ben Webb on Project Management: Why Most Projects Don’t Fail — They Drift

Image
  Projects rarely explode. They don’t collapse in a single moment of chaos. They  drift . I’m Ben Webb, an Australian project manager who has delivered complex infrastructure, tourism and public-facing projects under intense scrutiny — including Sydney Zoo, ICC Sydney and Sydney Harbour BridgeClimb. What I’ve seen repeatedly is this: Projects don’t fail because people don’t care. They fail because  no one forces decisions early enough . Drift is the most expensive risk in projects Drift shows up quietly: Decisions deferred “until the next meeting” Risks acknowledged but not owned Interfaces assumed instead of resolved Governance present on paper, absent in reality Schedules still exist. Reports still get written. But control slowly disappears. By the time leadership reacts, the cost isn’t time — it’s credibility. Planning doesn’t stop drift. Decisions do. Most teams respond to uncertainty by adding process : More reporting More reviews More layers of approval None of that...
Read more

Ben Webb on Project Management: Busy Is Not the Same as Progress

  Every project has that moment. The calendar is full. The inbox is overflowing. Meetings run back-to-back. And yet — nothing meaningful is moving. I’ve seen this on projects worth millions, sometimes billions. Teams working flat out, exhausted, committed… and completely stuck. Because activity is easy . Progress is not. Why projects love to stay busy Busyness creates comfort. It looks like effort. It feels like momentum. But it often hides the truth: Decisions aren’t being made Risks aren’t being confronted Accountability is blurred Direction is assumed, not agreed When progress stalls, teams instinctively add more : More workshops. More reporting. More coordination meetings. Very rarely do they stop and ask the uncomfortable question: What decision are we avoiding right now? Progress always looks quieter than you expect Real progress doesn’t announce itself. It looks like: One hard decision made early One scope line drawn clearly One risk owned, not “noted” One escalation done pr...
Read more