A problem gets fixed. The immediate pressure drops and the meeting that used to happen every morning becomes weekly again.
But somebody is still spending two hours every Thursday reconciling the numbers by hand. A team has quietly picked up an extra approval step. Or the customer issue has disappeared because Operations now checks every case before it reaches the customer.
The problem has gone, but the cost has not. It has moved somewhere else.
That distinction matters because organisations are usually much better at seeing the cost attached to a recognised problem than the cost absorbed after it has apparently been solved.
A project delay is visible; the workaround that prevents another delay may not be. A service failure is visible, while the additional checking introduced to stop it happening again can simply become part of the job. The missed deadline gets attention, but the management time subsequently spent making sure the next one holds rarely gets accounted for in quite the same way.
Nothing necessarily looks wrong. In fact, things can look better.
That is precisely why cost can already be forming before visible failure gives anyone a reason to look more closely.
What this usually looks like in practice
There is rarely a line in a report saying that £40,000 of cost has moved from one part of the organisation to another.
It appears in smaller, more ordinary ways. Someone starts checking something that used to need no checking. A weekly meeting becomes two because the first no longer produces enough confidence. A manager gets pulled into decisions that previously sat comfortably one level below, or a spreadsheet appears alongside a system because the system cannot quite provide what people now need.
Sometimes a team simply takes on an additional step because doing so is quicker than waiting for another team to resolve the underlying issue.
None of those things necessarily constitutes failure. Individually, they can be perfectly sensible responses. The difficulty comes when the response remains after the immediate problem has passed.
What started as an exception becomes part of normal delivery. Capacity is consumed, but no longer recognised as the cost of the original issue.
This is where the commercial signal becomes harder to ignore: cost is increasing before problems are visible, and the visible work no longer gives leaders enough confidence to assume progress is holding.
The organisation may still be delivering and meeting the commitment that mattered. It is simply paying more to do it.
Solving the visible problem does not necessarily remove its consequences
This is where apparently successful interventions can be misleading.
Suppose a programme has repeatedly missed a critical handoff. The immediate response is sensible: introduce an additional review three days before the handoff.
The misses stop. Problem solved.
Except the review requires six people, preparation from three teams and perhaps an hour of management time every week. That may still be the right trade, but it is a trade.
If nobody subsequently asks whether that review is still necessary, its cost becomes part of the operating environment.
The same thing happens outside large programmes. A business owner resolves repeated customer errors by checking every significant order personally. Complaints fall, customers are happier and the intervention has worked.
But the constraint has not necessarily disappeared. Some of its cost is now sitting in the owner’s diary.
This is why cost displacement is easy to miss. The intervention can produce exactly the result intended while creating hidden effort elsewhere.
The question is not whether the fix worked, but whether the organisation knows what it is now paying to keep it working.
Hidden cost is often paid in capacity before it is paid in cash
Not every displaced cost appears in a budget. Often the first thing consumed is capacity.
It might be another ten minutes spent checking something, another review, someone copied into correspondence because they know the history, or a senior person joining a call because their presence makes a decision more likely to hold.
Each addition is too small to attract much attention. Collectively, they change how much work the organisation can absorb.
This is one reason a team can become increasingly busy without any obvious increase in demand: existing work has acquired more handling. Because that handling has accumulated gradually, the organisation may explain the resulting capacity strain by looking somewhere else entirely.
Perhaps it needs another person. Perhaps the team needs to be more productive, the process needs automating or the project needs more resource.
Any of those may eventually be true. But they are different questions from asking how much effort is now being spent compensating for things that were supposedly fixed.
That distinction becomes commercially important when margin pressure appears, delivery takes longer than expected or revenue is delayed because capacity that should have supported new work is being used to protect existing work.
The cash cost may arrive later. The capacity cost is already there.
The most expensive workaround is often the one everybody has stopped noticing
Temporary workarounds announce themselves as temporary. People know they are inconvenient, talk about removing them and tolerate them because there is a reason.
Established workarounds are different.
They acquire owners, templates, meetings and calendar invitations. People joining the organisation learn how to do them without necessarily learning why they exist. Eventually, the workaround stops feeling like a workaround and becomes simply how the work gets done.
At that point, the cost is harder to challenge because removing it can appear to introduce risk.
Why stop the review when the review is one of the reasons nothing has gone wrong? Why remove the additional approval when there have been no recent control failures? And why give the manager their time back when their involvement is helping everything run smoothly?
There may be good answers to each of those questions. But there is an important difference between deliberately funding a control because its value exceeds its cost and continuing to fund one because nobody remembers the condition that created it.
Left alone, the condition does not usually stabilise. It becomes absorbed into the way work is being managed.
Once that happens, the workaround itself becomes difficult to distinguish from the work.
The commercial impact appears somewhere eventually
Displaced cost can remain operationally invisible for quite a while. Commercially, it tends to surface eventually.
It can appear as margin compression during delivery because more effort is required to deliver the same work, or as the commercial impact of delivery delay because decisions and handoffs now carry additional steps. It may show up as revenue timing risk because scarce capacity is protecting current delivery rather than enabling the next piece of work.
Sometimes it is less precise: a persistent sense that the organisation is spending too much effort for too little return.
This is why looking only at the original problem gives an incomplete picture. A reduction in incidents does not show the cost of preventing those incidents. A project returning to plan does not show how much additional management attention is now keeping it there. A customer process becoming reliable does not show whether people are compensating for weaknesses behind it.
The visible outcome may have improved while the commercial position is changing.
That does not make the intervention wrong. It makes the second question necessary:
What did solving this move somewhere else?
A useful place to look is where effort no longer produces an equivalent return
The clearest signal is often not the original problem at all. It is the area that now feels disproportionately difficult.
A team needs more coordination than its workload seems to justify. A manager has less capacity despite having delegated more. Delivery requires increasing reassurance even though the underlying metrics look acceptable. A business is growing, but each additional piece of work seems harder to absorb than the last.
Those conditions do not prove that cost has been displaced, but they are reasons to look.
In particular, they are reasons to examine where effort is no longer converting into equivalent results.
That is often where the history of an apparently solved problem is still visible — not in the original symptom, but in the work now required to stop it returning.
The result can be value leakage without an obvious new failure. More time, handling and management attention are being consumed while the outcome itself has barely changed.
The longer that continues, the more the workaround, cost or assumption becomes embedded, and the harder it becomes to separate what the organisation genuinely needs to do from what it has simply learned to do.
The useful question is not whether the problem was fixed
It probably was.
The more useful question is what changed elsewhere in order for it to stay fixed.
What additional effort is now being absorbed? What takes longer? Who is involved who was not involved before, and what capacity has quietly disappeared? Perhaps most importantly, what assumption or workaround would now be difficult to remove?
Those questions do not start from the assumption that the previous decision was wrong. They establish what the decision actually costs now.
Once the original issue has disappeared, the displaced cost is easy to treat as somebody else’s inefficiency, a resource problem or simply the normal cost of doing business.
Sometimes it is.
Sometimes the organisation is still paying for a problem everyone thinks it solved.
Where is this already showing up, and what is it costing in attention, confidence or capacity?
For business owners, that distinction is particularly useful when apparently healthy activity is consuming more time, attention or capacity than expected. The broader question is not simply where to cut cost, but where the business is absorbing work that no longer produces equivalent value.
Explore the Ibcrus perspective for business owners.
Related Observations
When Delivery Keeps Moving But Results Do Not
Useful where activity remains high but the cumulative return from that activity has weakened
The Cost Did Not Disappear. It Moved
A related observation on what happens when an apparent improvement transfers pressure rather than removing it.
We Fixed One Problem and Accidentally Created Three More
Useful where an intervention resolves the original symptom but introduces consequences elsewhere in the system.