A cost reduction is real only once the structure behind the activity leaves the P&L. Companies rationalize products, consolidate suppliers, and simplify networks every year, and the business case often books the savings immediately. Two years later, the planner still shows up, the shift still runs, the warehouse lease still renews, and the complexity has simply moved. Finance ends up asking why the cost base came back. The problem is that reducing activity isn't the same as removing structural cost. Unless the people, assets, and infrastructure that supported that complexity change too, much of the expected savings never reaches the P&L.
Why savings grow back: Most supply chain cost doesn’t move in a straight line
Many cost programs model savings as if supply chain cost moves proportionally with activity. It does not. Remove 10% of variants and you rarely remove 10% of planners, warehouse space, shifts, or production lines. The operating burden may fall, but cash only leaves when the reduction crosses a threshold that allows a structural element to come out.
Released capacity and realized savings are not the same thing. Changeover time becomes cash when it enables a shift or line to disappear. Warehouse simplification becomes cash when space, labor, or a lease is removed. Planning simplification becomes cash when the work and role design change. Remove the complexity and leave the structure intact, and you’ve created idle capacity. The business case needs to name the structural action, the owner, and the timing before it can call the number a saving.
Two kinds of complexity require different decisions
Supply chain cost programs struggle to maintain savings over the long term for one primary reason: complexity that has either been added intentionally to create protective redundancy or allowed to persist past its point of productivity as organizational structures shifted.
Within many companies, there are two different types of complexity present at any given moment: underwritten and inert. Both, under the right conditions, cause significant structural and financial drag.
INERT COMPLEXITYComplexity that once supported real work but no longer does. The product, supplier, node, or process changed; the headcount, systems, space, and planning burden did not. What remains is stranded cost. | UNDERWRITTEN COMPLEXITYComplexity the company deliberately bought as insurance: alternate suppliers, extra nodes, buffer inventory, redundant capacity, or diversified lanes. It may still be valuable, but its premium and the exposure it protects must be explicit. |
Inert complexity: Stranded costs and idle capacity
Rationalize low-volume products and the business case will show a large number coming out of the cost base. Look at the P&L two years later and most of it is still there.
Here’s inert complexity in a nutshell: You cut a product, a supplier, or a node, and it’s gone. But the headcount that managed it, the warehouse that received it, and the planning process built around it remain. It has no work to do, but it still has a budget line. These are stranded costs: infrastructure that has lost its purpose or value.
This is the threshold problem in practice. The product, supplier, or node disappeared, but the line, the lease, and the planning role never crossed the point where they could come out too. Remove the complexity and leave the structure intact, and you’ve created idle capacity.