Skip to content

All best practices

BP-043Grade B42 supporting cases (39 counted), 0 counter-examples

Re-plan openly when the facts change, rather than defending the old timetable

The practice

When the facts change, re-plan openly: change the plan's logic as well as its targets, re-baseline budgets and dates publicly, and price any reversal of the operating model.

Why it works

A plan defended past its assumptions costs more than one changed early: the gap widens, credibility erodes and the eventual re-plan is forced. Re-planning openly keeps the board and investors aligned and lets resources move to what now matters. When a first plan fails, changing only the targets repeats the mistake; the logic of the plan must change. Long-range targets need revising in public when they slip. Reinvention is serial, so leaders should expect each strategy to need a reset. The boundary is BP-032: re-plan on evidence, not on the first bad quarter.

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

  • Set a regular point (for example, semi-annually) to re-test the plan's assumptions.
  • When assumptions fail, present a re-plan that changes the logic, not only the numbers.
  • Re-baseline openly and show the original alongside.
  • Price the reversal of any operating-model choice before it is needed.

Warning signs

  • Targets are restated without any change in the plan behind them.
  • The timetable is defended while the industrial model is unproven.
  • Revisions are disclosed only when forced.

When it applies

  • Long programmes in volatile markets, product development and serial reinvention.

When it does not

  • When the evidence is noise rather than a change in facts (see BP-032).

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. 3 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
Topic (business problem)
  • The commercial engine is failing to convert opportunities
  • Legacy ERP and fragmented systems block execution
  • Supply chain disruption has made the network fragile
  • Inventory is simultaneously excessive and unavailable
  • Operations cannot meet demand efficiently
  • Competing transformation programs overwhelm resources
Function
  • Supply Chain & Logistics
  • Procurement & Strategic Sourcing
  • Manufacturing & Production
Starting situation
  • New initiative
  • In-flight initiative
  • Completed (review)
Industry
  • B2B SaaS and Subscription Software
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Engineering, Construction and EPC
  • Food and Beverage Manufacturing
  • Grocery and Food Retail
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
  • Physician Groups, Practices and MSOs
  • Professional Services: Accounting, Law and Advisory
  • 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.