Every project kicks off with the same quiet promise. On time. On budget. As if those two things sit comfortably beside each other, waiting to be delivered together like a matching set.
They don’t. And most people running projects know it, even if they’d never say so in the steering committee.
Time and cost pull against each other. Push hard on one and the other gives. You want it faster, it costs more: more people, more overtime, more paid to compress the same work into less calendar. You want it cheaper, it takes longer, with fewer hands, a slower pace, the timeline stretched to fit the smaller spend. This isn’t a failure of planning. It’s just how the physics of delivery works.
The trouble starts when someone decides both are fixed. The date can’t move. The budget can’t move. Everyone nods, because saying otherwise sounds like weakness. And in that moment, without anyone quite deciding it, a third thing becomes the release valve.
The outcome.
That’s the part nobody puts on a slide. When time and cost are both locked and the work turns out harder than anyone admitted, something has to absorb the pressure. It won’t be the date, because the date’s been promised to someone important. It won’t be the budget, because that’s been signed in blood. So it’s the actual thing you’re building that quietly gets worse. The corner cut that no one flags. The testing shortened. The scope trimmed in ways that don’t show up until the project’s live and someone asks why it doesn’t do the thing it was supposed to do.
I’ve watched this happen more than once. A project defended its schedule and its budget right to the finish line, hit both, and got congratulated for it. On time, on budget, and quietly not very good. The two numbers everyone was watching came in clean. The one thing that mattered, whether it actually worked, whether it delivered, came in compromised. And because the scoreboard only showed time and cost, it counted as a win.
That’s the trap. Time and cost are easy to measure, so they’re what gets managed. The outcome is harder to measure, so it’s what gets sacrificed. You optimise for the things you can see on a dashboard and you lose the thing you can’t.
The better projects I’ve been part of made a choice early, out loud. They decided which of time and cost was allowed to move, and they protected the outcome above both. Sometimes that meant going to a sponsor and saying the date holds but it’ll cost more than we thought. Sometimes it meant the opposite, that we can stay inside budget, but not by the original date. Neither of those is a comfortable conversation. Both are more honest than the alternative, which is pretending both can hold and letting the work silently pay the difference.
This is the same discipline behind knowing the one deadline that doesn’t negotiate. When a date genuinely can’t move, it stops being a source of stress and becomes the sharpest tool you have for deciding what’s really in scope. The projects that use it that way are the ones being managed deliberately rather than hopefully.
Here’s the thing worth sitting with. Deciding which constraint flexes isn’t a sign the project’s in trouble. It’s a sign someone’s actually managing it. The projects that insist nothing can move aren’t more disciplined. They’ve just moved the compromise somewhere no one’s looking. It usually comes back to who actually delivers your project, and whether that person has the standing to make the hard call out loud instead of letting it happen by default.
So the next time you’re handed a project with a fixed date and a fixed budget, ask the question early, before the pressure builds. If this turns out harder than we think, which one gives? Because one of them will. The only choice you get is whether you decide it deliberately, or let the outcome decide it for you.
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