Ben Webb on Project Management: Project Theatre and the Illusion of Control

 Project theatre looks impressive.

  • There are dashboards.
  • Weekly decks.
  • Steering committees.
  • Colour-coded risk registers.

Everyone is busy.
Everyone is reporting.
Everyone appears in control.

And yet — delivery quietly deteriorates.

What project theatre actually is

Project theatre is the performance of project management rather than the practice of it.

It’s when:

  • Reporting replaces decision-making

  • Meetings substitute for leadership

  • Governance exists to be seen, not used

  • Activity is mistaken for progress

The project looks healthy on paper while reality diverges underneath.

Nothing is technically wrong — until suddenly everything is.

Why organisations fall into project theatre

Project theatre is rarely deliberate.

It emerges when:

  • Leaders want reassurance more than truth

  • Bad news feels unwelcome

  • Accountability is diffused

  • Process is safer than judgement

In these environments, teams learn quickly what is rewarded:

  • Confidence over accuracy

  • Optimism over realism

  • Presentation over substance

So the performance improves — while outcomes decline.

The danger of polished reporting

The most dangerous projects I’ve seen were not chaotic.

They were calm.
Well-presented.
Professionally reported.

By the time reality broke through the narrative:

  • Options were gone

  • Trust was eroded

  • Reputations were already damaged

Project theatre doesn’t prevent failure.
It delays recognition of it.

What real control looks like

Real control is quieter than theatre.

It shows up as:

  • Decisions made early

  • Risks owned by name

  • Escalations that are timely, not theatrical

  • Fewer slides and harder conversations

Strong delivery environments don’t look impressive every week.

They look honest.

Final thought

If your project feels heavily governed but strangely fragile, ask a simple question:

Are we managing the work — or performing management?

Because projects don’t fail from lack of reporting.

They fail when performance replaces leadership.

For deeper insight into real-world project delivery, leadership under pressure, and the lessons that only come from experience, visit https://benwebb.au and https://benwebb.blog, where Sydney-based project manager Ben Webb publishes long-form commentary on project management, infrastructure, and complex delivery environments.

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