Every project accumulates noise. Frameworks, forums, methodology debates, dashboards, terms of reference, maturity assessments. All of it feels like the work. Very little of it is.
Strip a project back to the bone and one question is left standing.
Did it get delivered?
Not whether you followed the methodology. Not whether the right forums were held. Not whether the reports looked sharp or the register was clean or the RAG status stayed green. Did the thing you set out to do actually happen, and did it work?
Everything else is just how you got there, and it only earns its place if it got you there.
I’ve watched people win every process argument in the building and still fail to deliver. The governance was textbook. The plans were immaculate. The status reporting was genuinely beautiful, the sort of thing you’d put in a case study. And the project didn’t land.
Nobody remembers the process a year later. They remember whether it got done, whether it worked, whether it made the difference it promised. The frameworks evaporate from memory. The outcome doesn’t.
This is why I keep coming back to a single question when a project gets loud with activity: is this actually getting us closer to delivery, or just closer to looking organised?
It’s a surprisingly clarifying thing to ask out loud in a meeting. Sometimes the honest answer is that the activity is real and necessary, that the governance is doing its job and the reporting is telling the truth. Good. Carry on.
Often it’s that everyone is busy performing control while the actual work waits its turn. The meeting about the meeting. The report nobody reads that takes a day to produce. The gate that adds three weeks and catches nothing.
If it isn’t moving the outcome, it’s theatre. And theatre never delivered anything.
None of this is an argument for recklessness. Plans matter. Governance matters. Risk management matters. I’d never run a serious project without them. The argument is about what they’re for. Every one of them is a means to delivery, and the moment any of them starts competing with delivery for time and attention, it has stopped doing its job. That’s when you have to be honest about who actually delivers your project.
So keep asking the question. In the steering committee, in the status meeting, in the moment you’re about to spend a day building a slide pack.
Is this getting the thing delivered?
If the answer is no, you already know what to do about it.
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