BP-012Grade B25 supporting cases (24 counted), 0 counter-examples
Limit how many things change at once, for the business and for the customer
The practice
Do not change systems, processes, physical operations, price and the customer proposition in one step; separate the changes so each can be absorbed and its effect read.
Why it works
Each change carries its own failure modes, and when several go live together they interact: a new order system meets a new warehouse process at peak volume, or customers face a price rise and a new process in the same month. Simultaneous change also destroys the ability to learn, because when results disappoint nobody can say which change caused it. Separating a technology deadline from the business cutover, and the price change from the process change, keeps each risk containable and each signal readable. This costs time, which is why it is often traded away under schedule pressure.
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
- List every change hitting the same users, customers or sites in the same window.
- Cap the number of new systems, partners and processes that go live together.
- Separate technology deadlines from business cutover dates where possible.
- Do not ask the same customers to absorb a price change and a process change at once.
- Design each change so its effect can be measured separately.
Warning signs
- The launch plan lists price, product, store and system changes in the same quarter.
- Physical capacity is already tight when a systems change is scheduled.
- No control group or sequencing exists to read which change worked.
When it applies
- Retail and consumer launches, ERP and order-to-cash cutovers, and service-model changes.
When it does not
- Where the changes are interdependent and only work together; then rehearse the combination at scale (BP-014).
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
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
J. C. Penney Company, Inc. CS-018
Avon Products, Inc. CS-099
Netflix, Inc. CS-085
Haggen, Inc. (Haggen Food & Pharmacy), owned by the private-equity firm Comvest CS-101
Slater and Gordon Limited CS-109
CD PROJEKT S.A. CS-121
Virgin Australia Holdings (Virgin Australia Group), owned by Bain Capital from November 2020 CS-134
Mizuho Financial Group, Inc. and its banking subsidiary Mizuho Bank, Ltd. (Japan) CS-156
Kenya Revenue Authority (KRA), the national tax administration of Kenya CS-159
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.

