Skip to content

All best practices

BP-006Grade B47 supporting cases (46 counted), 1 counter-example

Roll out operational and system change in waves, each proven before the next

The practice

Roll out systems and operating changes in waves sized to what people, data and the supply chain can absorb, starting with a pilot site or small market, and expand only when the wave's measures are met.

Why it works

A wave limits how far a defect can spread and turns each release into evidence for the next gate. Starting small, for example with the smallest region or a few product lines, lets the method be learned where failure is survivable. Proving each release before the next starts stops defects compounding across releases. The pace should be published, so pressure to accelerate has to argue against a stated plan. Waves cost time and can leave two systems running in parallel, which is a real cost (see BP-013). Staging also does not guarantee viability: it contains damage, it does not fix a flawed design.

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

  • Choose a first wave that is representative but small enough that its failure is survivable.
  • Define exit measures for each wave (service level, error rate, user adoption) before it starts.
  • Make training completion a hard gate before users get access.
  • Put independent review on each release, and start the next only when the previous one is stable.
  • Publish the rollout pace and treat any compression as a board decision.

Warning signs

  • Waves overlap because the schedule slipped.
  • The pilot site is atypically easy (best-staffed, simplest product mix).
  • Exit measures are changed after the wave has started.
  • Pressure to 'go faster now that it works' after one good wave.

When it applies

  • Multi-site or multi-country system and process rollouts.
  • Product-development or operating-method changes across many units.

When it does not

  • Network-effect products that need national scale from day one (CS-014 counter-example).
  • Operating-model redesigns where a pilot pocket would be blocked by the surrounding old structure (CS-012 counter-example).

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. 1 supporting case(s) rest only on company-reported claims and are not counted toward the grade.

Where it applies

Transformation type
  • T05 ERP and core systems
  • T07 Supply chain
  • T10 Market entry and expansion
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Technology spending is growing without business returns
  • Supply chain disruption has made the network fragile
  • Inventory is simultaneously excessive and unavailable
  • Operations cannot meet demand efficiently
Function
  • Operations & Service Delivery
  • Supply Chain & Logistics
  • IT, ERP & Digital
  • Data, Analytics & AI
Starting situation
  • New initiative
  • In-flight initiative
Industry
  • B2B SaaS and Subscription Software
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Food and Beverage Manufacturing
  • Grocery and Food Retail
  • Hospitals and Health Systems
  • IT Services and ERP Systems Integrators
  • Industrial Distribution and Wholesale
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
  • Professional Services: Accounting, Law and Advisory
  • Renewable Fuels, Fueling Infrastructure and Credits
  • 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

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.