The Cost That Came Back: Why Savings Programmes Rarely Stay Saved
Most cost reduction programmes hit their number. Rather fewer keep it. Eighteen months on, the cost base has crept back and nothing obviously went wrong — because taking out cost is not the same as taking out work.
Most cost reduction programmes hit their number. Rather fewer of them keep it.
Eighteen months on, the cost base has crept back to somewhere near where it started. Headcount is lower and contractor spend is higher. Overtime has risen, and there is a backlog nobody had a line for.
Nothing obviously went wrong. The money simply returned.
1. Cost Is a Consequence, Not a Cause
A cost base is the sum of decisions about what work gets done, how often, to what standard, and how many people check it.
Attack the number directly and you remove the capacity. The decisions stay exactly where they were.
The work does not disappear because the budget did. It moves — to the people who remain, to a supplier, to a queue, or to the customer.
2. The Percentage Target Is a Refusal to Decide
Most savings programmes open with a figure. Take fifteen per cent out, cascaded to every function, each leader asked to find their share.
It looks like rigour. It is closer to the opposite — a uniform target says the organisation has not decided which activities matter more than others, and has asked everyone to work it out locally instead.
The pain is distributed evenly. The damage is not. Functions carrying slack absorb it comfortably, functions already stretched quietly break, and it takes two quarters before anyone can tell which was which.
3. The Work the Organisation Creates for Itself
A large share of activity in any sizeable organisation exists to deal with something that went wrong earlier — rework, chasing, re-checking, exceptions, complaints about the last mistake.
It carries real cost and produces nothing. It is also close to invisible in a budget, because it has no cost code of its own — it sits inside teams doing what looks like ordinary work.
Remove the people who handle the exceptions and the exceptions carry on arriving. All that has changed is the length of the queue.
4. Where the Cost Goes After You Take It Out
The interesting period is the two quarters after a savings programme closes.
What Gets Approved
A contractor is engaged to cover a gap. Overtime is approved to clear a backlog. A temporary resource line appears in an operational budget rather than a change one. A service level slips — and something is put in place to manage the escalations.
What It Adds Up To
Each of those is approved separately, by somebody entitled to approve it, and each is reasonable on its own terms. Together they are the original cost, reassembled under different headings.
5. The Cheaper Question
There are two ways to ask what an activity costs.
The Unit Question
What does it cost to perform — per transaction, per case, per call? That leads to efficiency work, and efficiency work has a floor.
The Volume Question
Why does the activity happen as often as it does? That leads to the volume, and the volume is where the money actually sits. It is also much harder to answer, because volume belongs to nobody in particular.
6. Standards Nobody Consciously Set
A good deal of operational cost is fixed by service standards that were never really chosen.
- Two approvals rather than one.
- A monthly report that four people read.
- A response time set during a bad year and never revisited.
- A check introduced after an incident a decade ago — still running, still costing.
None of those was a decision at the moment it mattered. Each is a decision now, and reviewing them is slower and considerably less impressive than announcing a reduction.
7. Questions Worth Asking Before the Target Is Set
Four questions change the shape of the conversation:
- What work will stop, specifically, and who has agreed to stop it?
- What proportion of this activity exists because something upstream went wrong?
- Which standards are we choosing to lower, and who signs that off?
- Where will this cost reappear if we are wrong, and who is watching for it?
The last one earns its place. A savings programme with no plan to look for the rebound is not a savings programme — it is a forecast.
8. Why This Sits With the Executive
Finance can size the prize and say where the money currently sits. It cannot decide what the organisation should stop doing, because that is a question about purpose rather than expenditure.
That decision belongs to the people who own the outcomes — and it is uncomfortable, because it means saying out loud that something the organisation values is worth less than it costs.
Very few savings programmes fail because the finance was wrong. They fail because that conversation was never held, and the number was delivered anyway.
The cost did not come back because the programme failed. It came back because the work never left.