Skip to content

All best practices

BP-013Grade B29 supporting cases (28 counted), 0 counter-examples

Budget the whole-life cost of a core programme, treat budget rises as new decisions, and retire legacy on a dated plan

The practice

Budget for build, stabilisation, run cost, amortisation and the cost of failure; treat any scope-driven budget rise as a new decision with a revised benefits case; and retire legacy platforms on a funded, dated plan.

Why it works

The visible budget of a core-system or store-estate programme is usually the build. Stabilisation, the amortisation tail, the run cost of two platforms in parallel and the cost of a failed go-live are often larger, and they arrive after approval when the decision can no longer be revisited cheaply. When budget and scope collide, cutting the functions that make the system usable saves money on paper and moves cost into operations. Treating a budget rise as a new decision forces the benefits case to be re-tested rather than assumed. Legacy platforms kept alive 'temporarily' become permanent cost and risk unless their retirement is dated and funded. Flyvbjerg and Budzier's data show IT overruns have a fat tail [R4], which supports budgeting for the tail rather than the mean.

KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).

How to apply it

  • Present a whole-life cost: build, stabilisation, parallel run, amortisation, run cost and a contingency sized to the overrun tail.
  • Set a threshold (for example 10% of budget) above which a rise returns to the board with a revised benefits case.
  • When budget and scope collide, escalate; do not cut usability-critical functions silently.
  • Record integration shortcuts as technical debt with a repayment date.
  • Fund and date the decommissioning of each legacy platform in the business case.

Warning signs

  • Contingency is a round percentage unrelated to the risk profile.
  • Two platforms are planned to run in parallel 'for a transition period' with no end date.
  • Run-cost estimates are missing from the business case.
  • Scope cuts are reported as savings.

When it applies

  • Core-system replacements, store-estate and network programmes, and post-merger platform consolidation.

When it does not

  • Small, modular changes whose run cost is trivial and whose failure is reversible.

Evidence grade: Grade B

At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.

Why this grade

Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does (R4 supports the mechanism only, not the practice). 1 supporting case(s) rest only on company-reported claims and are not counted toward the grade.

Where it applies

Transformation type
  • T01 Digital
  • T05 ERP and core systems
  • T07 Supply chain
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Cyber and technology risks threaten continuity
  • Technology spending is growing without business returns
  • Inventory is simultaneously excessive and unavailable
  • Service delivery is too slow, unreliable or expensive
Function
  • Supply Chain & Logistics
  • IT, ERP & Digital
  • Customer Experience & Support
  • Procurement & Strategic Sourcing
  • Risk, Compliance & Internal Audit
Starting situation
  • New initiative
  • In-flight initiative
Industry
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Food and Beverage Manufacturing
  • Hospitals and Health Systems
  • Industrial Distribution and Wholesale
  • Other (cross-industry)
  • Specialty Retail and Omnichannel Commerce
  • Telecommunications, Broadband and Fiber
Region
  • Africa
  • Central and Eastern Europe
  • East Asia
  • Global
  • Latin America
  • Middle East
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

Supporting and counter cases

Research

  • Among 1,471 IT projects, about one in six had an average cost overrun of 200%, against a 27% average.

    Dataset of 1,471 IT projects with a stated method (academic preprint). It measures cost and schedule overruns, not the effect of any practice.

    Why Your IT Project Might Be Riskier Than You Think · Flyvbjerg and Budzier, arXiv, 2013

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.