Ben Webb | Project Manager

 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 substan...

Project drift doesn’t announce itself. There’s no crisis meeting. No dramatic failure. No single moment where everything goes wrong. Drift is what happens when decisions are continuously deferred — politely, rationally, and with the best intentions. Drift is rarely caused by incompetence Most drifting projects are run by capable people. They have plans. They have governance. They have regular meetings. What they lack is decision pressure . Issues are noted, but not resolved. Options are discussed, but not chosen. Risks are acknowledged, but not owned. Over time, momentum erodes. Why drift feels reasonable at first Drift is comfortable because it feels responsible: “Let’s wait for more information” “We don’t want to rush this” “We’ll revisit it next meeting” Each delay seems minor. Collectively, they hollow out delivery. By the time the consequences surface, no single decision can be blamed — which is exactly why drift survives for so long. What stops drift in practice Drift ends the m...

Early-career project managers are taught to be helpful. Say yes. Be flexible. Accommodate requests. Senior project managers learn something different. Every yes has a cost Saying yes: Commits resources Introduces risk Changes priorities Creates expectations Uncontrolled yes's don’t create progress. They create overload. What experience teaches Experienced leaders: Protect focus Defend scope Say no early Explain why clearly Not to be difficult — but to keep delivery viable. Final thought Projects fail less often from refusal. They fail more often from agreement without consequence. 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.

Many project failures start with good intentions. Being reasonable. Being patient. Giving things time. Reasonableness has its place. But prolonged reasonableness often becomes avoidance. When patience turns into exposure Leaders wait because: They don’t want conflict They trust things will improve They hope issues resolve organically Sometimes they do. Often they don’t — and the cost compounds quietly. What senior leaders learn There’s a point where being reasonable stops being constructive. Strong leaders recognise that moment and act: Escalate Reset expectations Change direction Draw boundaries That’s not aggression. It’s responsibility. Final thought Projects don’t need endless patience. They need timely courage. 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 managem...

Early in projects, agreement is easy. Everyone nods. Everyone supports the direction. Everyone is aligned. Until a real decision appears. Agreement without consequence is meaningless True alignment only reveals itself when: Trade-offs are required Someone loses Risk is accepted Accountability becomes visible That’s when consensus often dissolves. What experienced leaders look for Not harmony. Clarity. They don’t ask: “Does everyone agree?” They ask: “Does everyone understand the decision — and their role in it?” That’s alignment that holds under pressure. Final thought Projects don’t stall because people disagree. They stall because disagreement isn’t resolved decisively.

 People often mistake calm projects for easy ones. They’re not. They’re usually the hardest — just well-led. Calm is the result, not the condition Calm projects still face: Complexity Pressure Competing interests Uncertainty The difference is that chaos is absorbed by leadership, not passed down. Decisions are made. Issues are surfaced early. Teams aren’t left guessing. What creates calm delivery environments It’s rarely the plan. It’s: Clear decision rights Predictable escalation Leaders who don’t perform panic Confidence grounded in experience Calm doesn’t mean passive. It means controlled. Final thought If your project feels constantly tense, the issue isn’t workload. It’s leadership stability. 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, infrastruc...

  Projects love early certainty. Clear dates. Fixed scopes. Confident forecasts. They look reassuring. They’re often wrong. Why certainty shows up too early Early in a project, information is thin but optimism is high. This creates a dangerous combination: Confidence without evidence Commitment without flexibility Promises that harden too soon By the time reality catches up, the narrative is already locked. What experienced leaders do instead They trade false certainty for: Direction with flexibility Guardrails instead of guarantees Decisions that can adapt This isn’t indecision. It’s maturity. Final thought Certainty feels comforting. But in complex projects, flexibility is what actually protects outcomes.

 Projects don’t usually lie -  They edit . Status gets softened. Language becomes careful. Risks are “monitored” instead of addressed. This shift doesn’t happen because teams are dishonest. It happens because telling the full truth starts to feel unsafe. How truth erodes in delivery environments It begins subtly: Bad news is delayed Assumptions are left unchallenged Optimism replaces evidence Eventually, reporting stops reflecting reality and starts reflecting what feels acceptable . At that point, governance still exists — but insight doesn’t. Why leaders should worry about “good news” projects Projects that only report positives are rarely healthy. Strong delivery environments surface: Tension Uncertainty Disagreement Inconvenient facts When teams stop raising issues, it’s not because problems disappeared. It’s because honesty no longer feels welcome. Final thought If your project always sounds fine, ask what isn’t being said. Silence is rarely reassurance.

  A lot has been made of AI in project management.  Every conference, platform, and consultancy seems to have a view on how artificial intelligence will “transform delivery.” Dashboards will think for us. Schedules will self-correct. Risks will be predicted before they appear. Project managers, we’re told, will finally be freed from the grind. There’s some truth in that. There’s also a lot of exaggeration. After working across complex infrastructure, tourism, events, and high-risk delivery environments, I’ve learned to be cautious of anything promising transformation without accountability. AI is a powerful tool. It is not a substitute for judgment, leadership, or decision-making under pressure. And in project environments, those are the things that matter most. What AI is actually good at in project management AI excels at pattern recognition. It can process volumes of data that humans simply can’t. In the right environments, it can surface trends, highlight anomalies, an...

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...

  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...

  Ask a project team who is accountable for a decision and you’ll often get silence, a job title, or a steering committee. Rarely do you get a name. That gap — between responsibility and accountability — is where most projects quietly unravel. Plans don’t fail because they’re wrong. They fail because no one owns the hard calls when the pressure arrives. I’ve seen beautifully documented projects collapse in slow motion, not because the strategy was flawed, the budget unrealistic, or the schedule aggressive — but because accountability was diluted to the point where it effectively disappeared. Everyone was “involved”. Everyone was “consulted”. Everyone was “across it”. No one was accountable. And when things went wrong — as they always do — the project had nowhere to go. Responsibility is comfortable. Accountability is not. Most project environments are very good at assigning responsibility. Roles are defined. Org charts are polished. Position descriptions are clear. On paper, it...

  One of the quiet myths in project management is that certainty is the goal. It isn’t. Certainty rarely exists — especially on complex, high-risk projects. What matters more is confidence . Confidence changes how teams behave When leaders project confidence: Teams act decisively Issues surface earlier Risk conversations improve Delivery stabilises When leaders wait for certainty: Decisions stall Responsibility blurs Momentum evaporates Problems grow quietly Confidence doesn’t mean recklessness. It means clarity about direction — even while details evolve. Where confidence really comes from Not optimism. Not bravado. Not perfect plans. Confidence comes from: Experience Pattern recognition Knowing where flexibility exists Knowing where it doesn’t It’s earned, not manufactured. Final thought Projects don’t need leaders who know everything. They need leaders who can say: “This is the direction. We’ll adjust — but we’re moving.” That’s how complex work actually gets done. About the aut...

  “Stakeholder alignment” is one of the most overused phrases in projects. Everyone agrees it’s important. Few define what it actually means. And even fewer are honest when it doesn’t exist. Alignment isn’t agreement This is where projects get confused. Alignment doesn’t mean: Everyone is happy Everyone supports the decision Everyone got what they wanted It means: Everyone understands the decision Everyone knows why it was made Everyone knows what happens next Everyone knows what they’re accountable for You can have alignment without harmony. The cost of pretending alignment exists I’ve seen projects say they’re aligned while: Departments quietly resist Partners hedge their commitments Decisions are re-litigated Messaging fractures The result isn’t conflict — it’s drift. Nothing stalls delivery faster than false consensus. What real alignment looks like Real alignment is visible: Clear decisions Documented trade-offs Known dissent Locked next steps It’s not always comfortable. But ...

  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...