BP-069Grade B32 supporting cases (31 counted), 0 counter-examples
Diagnose the root cause and the gap to the best before choosing the remedy
The practice
Before cutting or launching a programme, diagnose whether the problem is structural or self-inflicted, measure the gap to the best in the industry, and diagnose the whole operating system before promising growth.
Why it works
Remedies chosen before diagnosis address symptoms: cost cuts for a problem that is really in the customer offer, a partnership for a gap that could be closed alone, or growth promises from an operating system that cannot deliver them. Measuring the gap to the best performer, and changing the benchmark against which ambition is set, show the true scale of the problem. Separating structural decline from self-inflicted damage determines whether the answer is to fix the business or to change it. The KB's view, not a finding in the cases, is that the diagnosis should be time-boxed so it does not become a reason to delay.
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
- Time-box a diagnostic of four to eight weeks before committing to a remedy.
- Classify each problem as structural (market) or self-inflicted (execution).
- Benchmark against the best in the industry, not the average.
- Diagnose the whole operating system (product, supply, channels, systems) before promising growth.
- Consider stand-alone and partnership options on the diagnosed gaps.
Warning signs
- The remedy was announced before the diagnosis was finished.
- Benchmarks are internal or against the average.
- Growth targets precede an operating-system review.
When it applies
- Turnarounds, new-leader starts and strategic reviews.
When it does not
- Acute crises where survival actions cannot wait; diagnose in parallel.
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
Best Buy Co., Inc. CS-072
Marks and Spencer Group plc CS-055
Chrysler Group / Fiat S.p.A. (later Fiat Chrysler Automobiles) CS-042
OCP Group (OCP S.A., formerly Office Chérifien des Phosphates), majority-owned by the Moroccan state CS-136
Waberer's International Nyrt. (Waberer's), listed on the Budapest Stock Exchange CS-141
Ciech S.A. (CIECH Group), Polish chemicals group listed on the Warsaw Stock Exchange CS-142
Eicher Motors Limited (Royal Enfield), part of the Eicher Group, New Delhi CS-151
Cybozu, Inc., Tokyo-listed maker of groupware and the kintone cloud platform CS-157
HCL Technologies Limited (Noida, India), IT services company listed on the Indian exchanges CS-212
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.

