There’s a version of discipline in project management that looks like discipline and functions as its opposite. Protect the plan. Manage to the baseline. Hold the line on variance.
It sounds rigorous. Often it’s just stubbornness with a governance framework wrapped around it.
Think about when the plan was written. Day one. The moment you knew less about the project than you would at any other point in its life. You hadn’t met the constraints yet. You hadn’t discovered which assumptions were wrong. You hadn’t found out that the integration was harder than anyone said, or that the key stakeholder had a view nobody had asked for.
Every week after that, you learn something. That’s not a failure of planning. That’s what doing the work does to you.
So when someone insists on defending the baseline, ask what they’re actually defending. Frequently it’s the least informed set of decisions anyone on the project will ever make, held up against everything learned since.
I’m not arguing for chaos. Plans matter. They force you to think ahead, to sequence things properly, to notice dependencies before they bite. The act of planning is genuinely useful, and I’d never start something serious without it.
But a plan is a tool. It was never a promise.
The moment it stops serving delivery, it’s costing you. And plenty of projects reach that point without anyone noticing, because changing the plan feels like admitting failure while following it feels responsible, right up until the day the whole thing collapses on schedule.
Here’s a test I use. If a plan hasn’t changed in a month, it’s probably not stable. It’s being ignored. Nobody’s updating it because nobody’s using it, and the real work has moved somewhere else, into people’s heads and side conversations and whatever the team actually agreed on Tuesday.
At the next review, skip the percentage complete theatre and ask one question: what have we learned that the plan doesn’t reflect yet? It’s the same instinct behind refusing to accept a status report at face value. The document is not the project.
Then change it.
That isn’t scope slipping. That’s the plan finally catching up to reality. It also forces the honest conversation about whether the schedule or the budget gives, which is the conversation most projects spend months avoiding.
A plan that reflects reality is worth something. One that doesn’t is just an expensive record of what you used to believe.
Ben Webb is an award-winning project leader and strategist. Named Australian Institute of Project Management Project Manager of the Year in 2022 and nominated for the International Project Management Association’s World Project Manager of the Year in 2023, he writes about delivery, leadership and the difference between managing a project and actually getting it done.
Leave a Reply