Ben Webb | Project Manager

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.