After a difficult go live there’s a certain kind of story that often gets told. It usually goes something like this: “The team pulled together, worked through the weekend, and got it over the line”  It’s usually told with pride, and often it should be. People stepped up because they cared enough to make it work.

But I’ve started to notice how often that story repeats itself, and what it might be telling us if it does.

If a programme only succeeds when someone works late, escalates any issues almost secretly, or quietly handles a problem that should have been noticed weeks earlier, that’s more a story about a delivery culture that has come to depend on that behaviour rather than a story about commitment. 

Firefighting Becomes The Culture, Not The Exception

Of course no organisation sets out to build a culture of firefighting. It just has a tendency to happen, one deadline at a time.

The first time a team pulls off a rescue, it looks like “resilience.” The second time, it looks like “capability.” But by the third or fourth time, nobody questions it anymore, because it’s just become how things get done.

The trouble is that heroics are hard to plan for and even harder to sustain. What starts as an exceptional response to an unusual problem can quickly become the expected response to a normal one. And once that shift happens, it’s difficult to reverse, because the organisation has already learned that the fix always arrives in the end.

Pressure Changes Behaviour Before It Changes Outcomes

One of the more uncomfortable truths about pressure is that it tends to change how people behave long before it shows up in results.

Under pressure, people cut corners. Testing gets compressed, or worse, left. And a concern that would normally be raised in a steering group gets mentioned informally instead, because there isn’t time to add it to the agenda. Eventually, you find that decisions that would have previously involved three people are being made by one, because waiting for the others feels like a luxury they can’t afford.

None of this looks too dramatic while it’s happening, because each choice seems small and reasonable given the circumstances. It’s only when you step back and look at the pattern that you can see how far the ways of working have drifted from what anyone would have signed off on if asked directly.

Governance Is Usually The First Thing To Soften

Governance exists to slow things down just enough to catch what the sense of urgency would make us miss. Which is exactly why it’s often the first thing to give way when a launch date is close.

Meetings get shorter, because nobody wants to be the person raising a difficult question three weeks before go-live. Escalation routes still technically exist, but using them starts to feel like an admission of failure rather than a normal part of delivery.

I’ve seen this happen in programmes that had perfectly good governance on paper. The structures were never removed, they just stopped being used the way they were designed to be used, at exactly the point they were needed most.

“Getting Over The Line” Is Not The Same As Sustainable Delivery

There’s a real difference between a programme that reaches its milestone by any means necessary, and a programme that reaches it in a way that could be repeated.

Getting over the line answers one question: did it launch? It doesn’t answer the more useful ones. 

Did the team get there in a way that’s still working three months later? 

Did the fixes introduce any risks that haven’t surfaced yet? 

Did the people involved absorb something they shouldn’t have had to, and would they be willing to do it again next time?

Organisations that only measure whether the deadline was hit will keep getting the answer they’re looking for, right up until the point they don’t. By then, the underlying pattern is usually ingrained, and much harder to unpick than it would have been earlier.

Why Realistic Prioritisation Matters More Than It Sounds

A lot of unsustainable delivery starts with a scope that was never realistic in the first place.

It often happens because of an accumulation of small changes and decisions that each seemed reasonable in isolation, alongside a reluctance to say that something else would need to give way in return. Everything stays on the plan. Nothing gets formally deprioritised, and the gap between what’s been committed to and what’s actually achievable gets filled, eventually, by people working harder rather than by anyone rethinking the scope.

Realistic prioritisation isn’t about doing less. It’s about being honest, early, about what the timeline and the resource actually allow, so that the difference doesn’t have to be made up later under pressure.

Healthy Organisations Make It Safe To Raise Concerns Early

The organisations that navigate this well tend to share one thing in common: it’s genuinely acceptable to say that something isn’t on track.

That sounds straightforward, but it depends on how concerns are received in practice, not just in policy. If raising a risk gets treated as a delay or a lack of commitment, people will stop raising it, and the organisation will lose visibility of problems at exactly the stage they’re still easy to solve.

Creating that kind of space isn’t really a communications exercise; it’s a leadership one. It means responding to bad news calmly, rewarding the person who flagged the problem in month two rather than only celebrating the team that rescued it in month six, and being willing to move a date when the evidence says it should move.

What This Means In Practice

None of this is an argument against effort, commitment, or the occasional genuine push to meet a deadline that matters. Those things are a normal part of delivery, and sometimes necessary.

The distinction worth holding onto is between a team that occasionally rises to a real challenge, and a programme that has come to rely on someone rising to it every time. The first is resilience; the second is a warning sign, disguised as a success story.

The programmes that hold up well over time aren’t usually the ones with the Hollywood style recovery stories. They’re the ones where concerns surface early enough that no one has to be a hero at all.