When IT savings need more than a target
Most large IT cost programs report a familiar pattern: ambitious target at year-zero, confident green status through Q1 and Q2, slippage starting in Q3, and a quiet rollover of the unrealized portion into the following year. The mechanism is rarely failure of intent. It is structural disconnection between financial logic and delivery reality.
Context
Cost reduction programs begin with a top-down target. The number may be correct, but it does not explain how savings will be created, when they will be recognized or what evidence will be accepted. Without translation into specific levers owned by named individuals, the target floats above the operating layer — real on paper, unrealized in the ledger.
What usually goes wrong
Savings are distributed across infrastructure, applications, contracts and operating model changes, but the technical levers are not linked to the financial forecast. Owners are nominal. Milestones are soft. Evidence rules are absent. The program reports savings that IT recognizes and finance does not — and the discrepancy surfaces only at year-end, when replanning has already begun.
Five elements per lever: driver, owner, milestone, technical evidence, financial evidence reconciled to the GL.
Where savings physically live
Real savings come from specific technical moves: decommissioning a legacy server estate, terminating unused software licenses, reducing cloud capacity, automating a manual run process. Each financial target must be mapped to the specific action that produces it. Without that mapping, the saving is a projection.
Demand is the re-inflator
Cost programs that do not control demand growth produce no net saving. Business growth re-inflates the cost base as fast as the technical savings are realized. Demand governance — business cases, charge-back, prioritization gates — must be in scope, not deferred to a separate initiative.
The ledger is the arbiter
Each realized saving must be reconciled to the general ledger by the controller community. If finance and IT cannot agree that a saving has materialized, it has not. Evidence rules must be defined at program design — not negotiated at year-end.
Forums that review by lever — not by colour
If the executive forum reviews savings by category and RAG status, accountability dilutes. If it reviews by lever, owner and evidence — with the technical milestone on the table — the framework holds through slippage and escalation.
"The difference between a savings target and a realized benefit is governance."
— RSV Consult perspective
What works in practice
A value-capture model connects each saving to a driver — decommissioning, capacity reduction, license rationalization, sourcing change, operating model redesign. Each lever has an owner, a dependency chain, a milestone date and a financial evidence rule. Governance reviews by lever and owner, not by category and colour.
Cost transformation succeeds when finance and technology speak the same evidence-based language. If the saving cannot be reconciled to the ledger, it is a forecast — not a saving.