Skip to content

All best practices

BP-014Grade B19 supporting cases (17 counted), 0 counter-examples

Sequence customer-facing cutovers last, rehearse failure at full scale, and make resilience a programme outcome

The practice

Put the riskiest customer-facing cutover last, rehearse it and the recovery from its failure at the scale you could actually face, and set resilience measures as programme deliverables.

Why it works

Back-office conversions fail quietly; customer-facing ones fail in public, so integrating low-touchpoint businesses first lets the team learn before the stakes are highest. Compressing each cutover into a short, rehearsed window reduces the period in which two systems are half-live. Planning for cutover failure, rather than assuming success, means the rollback and recovery have been tested before they are needed. As the speed of change rises (agile delivery, cloud, online services), operations and security become part of the product, so resilience has to scale with it. Measuring resilience in time-to-know and time-to-recover makes it reportable.

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

  • Order integration and migration waves by customer exposure, with the branch, store or customer-account cutover last.
  • Rehearse each cutover end to end, including rollback, in a production-like environment.
  • Run a failure-and-recovery exercise at the volume of a bad day, not an average day.
  • Define resilience measures (time-to-detect, time-to-recover, change failure rate) as programme deliverables.
  • Scale change-control and incident response as release frequency rises.

Warning signs

  • The rollback plan has never been executed.
  • The customer-facing cutover is scheduled first because it is 'the big one'.
  • Resilience is handed to operations after go-live.
  • Release frequency rises while incident counts are not tracked.

When it applies

  • Bank and airline mergers, core-banking migrations, cloud re-platforming and online-service launches.

When it does not

  • Where regulators or a deal require a single cutover date; then rehearsal and fallback carry the whole load.

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. 2 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
  • T08 Culture and change
Topic (business problem)
  • Customer churn and dissatisfaction are accelerating
  • 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
  • Service delivery is too slow, unreliable or expensive
Function
  • Operations & Service Delivery
  • IT, ERP & Digital
  • Customer Experience & Support
  • Data, Analytics & AI
  • Risk, Compliance & Internal Audit
Starting situation
  • New initiative
  • In-flight initiative
Industry
  • B2B SaaS and Subscription Software
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Food and Beverage Manufacturing
  • Industrial Distribution and Wholesale
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
Region
  • Africa
  • East Asia
  • Global
  • Latin America
  • Middle East
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

Supporting and counter cases

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.