Change programmes: the quiet cost of going too fast

Almost every transformation programme we've been called into shares the same origin story. A decision was made — usually for good reasons, usually under time pressure — to move faster than the organisation could comfortably absorb. Eighteen months later, the programme is behind schedule, over budget, and quietly losing the support of the people it depends on.

The interesting thing is that the technology is almost never the problem. The technology usually works. The cost of going too fast shows up elsewhere.

The four quiet costs

When leaders accelerate a change programme, they usually account for the visible costs: additional headcount, extended timelines, contingency budget. What they often miss are four quieter costs that compound over time.

1. The cost of exhausted senior sponsors

Every transformation programme depends on a small number of senior people to make decisions, unblock issues, and model the new behaviours. If those people are also expected to run their day jobs at full tilt, they will burn out — usually quietly, usually three months before the programme notices.

By the time sponsorship starts to slip, the programme has often already lost three or four critical decisions. Those decisions then get made by default, badly, lower down the organisation.

2. The cost of change fatigue

Organisations have a finite capacity for change in any given period. Exceed it and you don't get faster progress — you get slower progress plus rising resistance.

We've seen this most clearly in manufacturing and care settings, where the frontline workforce is expected to absorb new systems, new processes, and new reporting requirements simultaneously. The result is not resistance so much as disengagement: people comply on the surface and continue working around the system beneath it.

"The technology is almost never the problem. The technology usually works. The cost of going too fast shows up elsewhere."

3. The cost of deferred decision-making

When a programme is running fast, difficult decisions get deferred. Not because anyone is being lazy — because there isn't time to make them properly, and the working group hopes the decision will become obvious later.

It rarely does. It becomes more expensive instead. Options that were available at month two are usually gone by month six. What was a two-day conversation becomes a two-week remediation.

4. The cost of lost institutional knowledge

Change programmes often involve the departure — voluntary or otherwise — of people who have deep knowledge of how the business actually works. If they leave before their knowledge has been captured, the programme inherits a version of the organisation that doesn't exist.

Six months later, the new system has been designed around a process that nobody follows anymore, and the people who knew why are gone.

The warning signs

In our experience, the following are reliable early indicators that a change programme is running too fast:

• Sponsors are routinely absent from programme meetings, or send delegates.
• Steering group meetings are used to report progress rather than to make decisions.
• Working groups are asked to "bring recommendations" that they have no authority to make.
• Operational staff describe the programme as something being done to them, not with them.
• Escalations have become routine rather than exceptional.
• The programme plan assumes productivity improvements that haven't yet been evidenced.

What to do about it

The good news is that "too fast" is usually recoverable. The bad news is that recovering it requires the same thing that caused the problem: a difficult decision, made deliberately.

In practice, three interventions help most:

• Re-baseline the programme. Reset scope, timeline and expected benefits based on what has actually been learned, not what was originally assumed.
• Protect senior sponsorship. Carve out real time from the sponsors' diaries and hold it. Cancel other things instead.
• Re-engage the frontline. Not with surveys, but with involvement: ask people what would make this work for them, and be prepared to change the design accordingly.

The honest conclusion

Speed matters. In some situations, going faster is exactly the right call — particularly when the alternative is stasis. But speed has costs, and if those costs aren't named in advance, they will be paid later, less visibly, and usually by people who had no part in the original decision.

The most reliable predictor of a successful transformation we've seen is not the ambition of its aims, or the sophistication of its technology. It's whether the leadership team was honest, at the start, about how fast the organisation could actually move.