Ben Webb on Project Theatre: When Projects Perform Instead of Deliver

Every failing project has a phase where it looks like it’s working. Meetings are full. Dashboards are green. Slide decks multiply. Updates are delivered with confidence. From the outside, the project appears healthy. From the inside, the work that actually matters is being quietly avoided.

This is project theatre — the moment when a project stops delivering and starts performing.

I’ve seen it across infrastructure, hospitality, major events, and government programs. The scale changes, the language shifts, but the behaviour is consistent. Effort is redirected away from solving problems and toward maintaining the appearance of control. The project doesn’t collapse immediately. It drifts. And in that drift, risk compounds.

What project theatre looks like in practice

Project theatre is easy to spot once you know the signs.

Status reports become more polished as progress slows. Meetings focus on storytelling rather than decisions. Risks are “noted” but never closed. Issues are reframed as dependencies. Language softens. Certainty is implied, not earned.

Most telling of all, difficult conversations are postponed in favour of updates that feel safe.

The project becomes a performance for executives, clients, or governance forums. Everyone plays their part. No one wants to be the person who disrupts the narrative. The result is a collective commitment to looking in control rather than being in control.

Why theatre emerges under pressure

Project theatre is not caused by laziness. It’s caused by pressure.

When timelines tighten, scrutiny increases, or reputations are on the line, teams instinctively seek safety. Reporting feels safer than deciding. Alignment feels safer than disagreement. Optimism feels safer than realism.

Theatre offers short-term relief. It reassures stakeholders. It buys time. It protects individuals from blame.

The problem is that time is exactly what projects don’t have.

The longer theatre continues, the harder it becomes to reverse. Gaps widen. Assumptions harden. Eventually, reality forces its way back in — usually late, expensive, and publicly.

Busy is not progress — it’s often avoidance

One of the most dangerous myths in project environments is that busyness equals momentum. Theatre thrives in busy projects. Calendars are full. Emails are constant. Workshops are scheduled. Everyone feels stretched.

And yet, the same unresolved issues appear week after week.

Busyness creates the illusion of effort. Delivery requires resolution.

In theatrical projects, work is redirected toward activities that produce artefacts rather than outcomes. Slides replace decisions. Workshops replace accountability. Reporting replaces action.

It feels productive. It isn’t.

How theatre protects underperformance

Project theatre creates a strange form of collective protection. When everyone participates in the performance, no one stands out. Underperformance is absorbed into the system rather than addressed.

Individuals can point to outputs — reports written, meetings attended, frameworks applied — even as outcomes deteriorate. The project becomes very good at explaining why things haven’t moved rather than making them move.

This is why theatre can persist even in organisations full of capable people. The system rewards participation in the performance more than disruption of it.

Breaking theatre requires someone to be uncomfortable.

The role of leadership in sustaining — or stopping — theatre

Project theatre does not survive without tacit approval from leadership.

Leaders who reward optimistic reporting, discourage bad news, or avoid conflict create the conditions where theatre thrives. Teams learn quickly what is safe to say and what is not.

Conversely, leaders who ask direct questions, demand clarity, and accept discomfort collapse theatre fast.

The most effective leaders I’ve worked with are not the loudest or the most technical. They are the ones willing to pause a meeting and ask: what has actually changed since last week? Or who is accountable for resolving this?

Those questions cut through performance instantly.

What delivery-focused projects do differently

Projects that avoid theatre behave differently in subtle but important ways.

They track decisions, not just actions.
They measure risk reduction, not activity.
They treat unresolved issues as failures, not features.
They value clarity over comfort.

Most importantly, they create environments where telling the truth is safer than maintaining appearances.

This doesn’t make projects calmer. It makes them real.

Why project theatre is so hard to unwind

Once a project slips into theatre, reversing it is uncomfortable. Narratives must be challenged. Optimism must be recalibrated. Decisions that were avoided must finally be made.

This often coincides with resistance. People who were comfortable performing may struggle when delivery is demanded. Tension increases before performance improves.

That discomfort is not a sign something is wrong. It’s a sign reality is reasserting itself.

The cost of staying in performance mode

Projects can survive theatre for a while. Some survive it all the way to completion — at a higher cost, longer duration, and reduced outcome quality.

The real cost is not just financial. It’s cultural. Teams learn that appearance matters more than impact. That lesson carries forward into the next project, and the one after that.

Over time, organisations become excellent performers and poor deliverers.

The simple test that exposes theatre

If you want to know whether a project is delivering or performing, ask one question:

What decision was made this week that reduced risk?

If the answer is unclear, evasive, or theoretical, you’re watching theatre.

Projects don’t fail because people aren’t working hard. They fail because work is redirected toward performance when delivery becomes difficult.

The cure for project theatre is not more reporting. It’s courage — to tell the truth, make decisions, and accept accountability when it’s uncomfortable.

That’s what real delivery looks like.

Comments

Popular posts from this blog

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

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

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