The Trade-Off Nobody Names When Leaders Demand Speed
Every leader eventually asks the same question: how do we increase our speed of delivery? It’s a fair question. It’s also the one most likely to be answered dishonestly — not because anyone lies outright, but because most of the ways to go faster get quietly relabelled as improvements when they’re actually trade-offs.
There are really two families of answer.
The first is legitimate. Add more resources — labour, funds. Automate what can be automated. Outsource to someone who already knows how to do it faster than you do. Partner with others instead of building everything yourself. Break the dependencies in your plan so tasks can run in parallel instead of queuing behind each other. These are real levers. They cost money, or coordination effort, or both — but the cost is visible and it’s paid up front.
The second family is where most organisations actually go, because it’s cheaper and faster to reach for. Lower the quality standard. Eliminate scope. Postpone scope and call it a phase two. Redefine “done” so the bar drops without anyone voting on it. And, quietly, the most corrosive one of all: manage the psychology of the person watching. Distract them. Entertain them. Deflect the question. Let them lose track of time so they stop noticing the gap between what was promised and what shipped.
None of these get announced as what they are. Nobody puts “we lowered the quality bar” on a status report. It shows up as green, on schedule, on track — because the definition of on-track moved, not because the work got faster.
This is the same pattern I see in every ERP program I’ve ever sat inside, on either side of the table. A steering committee demands pace. Someone under pressure to deliver pace finds it — not by adding capacity, but by narrowing what counts as complete, or by managing what the sponsor notices rather than what actually happened. The report stays green. The program is not actually faster. It has just redefined finished.
Speed always comes at a cost. That’s not a criticism, it’s a fact of the work — there is no version of “faster” that is free. The failure isn’t choosing speed. The failure is not knowing, and not naming, what you paid for it.
So the discipline isn’t “never trade off quality or scope for speed.” Sometimes that’s exactly the right call — a deadline is real, a market window is closing, a council needs a decision before the next meeting. The discipline is understanding the trade-off before you announce the speed increase, not after. Know, specifically, what the organisation had to give up to go faster — and say it out loud to the people who are relying on the outcome, before they find out on their own.
Leaders who skip that step aren’t buying speed. They’re borrowing it, from a standard they haven’t told anyone they’ve lowered — and the bill comes due later, usually at go-live, usually as a surprise, usually to someone who wasn’t in the room when the trade-off was made.
