BP-045Grade B39 supporting cases (36 counted), 0 counter-examples
Fix the core product and operation before amplifying the channel or scaling the new strategy
The practice
Repair the core product, reliability, operating model or decision structure before, or alongside, investing in new channels, features, megaprojects or portfolio moves.
Why it works
Amplifying a weak product or an unreliable service multiplies its weakness: digital channels bring more customers to a product they do not like, new features sit on an app that fails, a megaproject absorbs attention while the existing fleet decays. Fixing the core first, or at least alongside, means new investment works on a sound base. It also earns credibility, because visible operational fixes show staff and customers that the change is real. The decision structure and operating model are part of the core: reshaping the portfolio or cost base through a broken structure repeats the failure in each new unit.
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
- Diagnose the core: product quality, reliability, maintenance backlog, decision structure.
- Set a reliability or quality threshold the core must meet before new features or channels are scaled.
- Fund maintenance of the existing asset base before or alongside megaprojects.
- Remove the main reason customers leave before asking them to stay.
- Fix the operating model before scaling the strategy.
Warning signs
- Marketing spend rises while product complaints are unresolved.
- Feature releases continue on an unstable platform.
- Maintenance budgets are cut to fund new capacity.
When it applies
- Digital channel launches, service turnarounds, utility and infrastructure programmes, portfolio reshaping.
When it does not
- When the core is in structural decline and the new business must start in parallel (BP-055).
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
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Domino's Pizza, Inc. CS-071
State Bank of India CS-075
Eskom Holdings SOC Ltd CS-062
Airbus (EADS) CS-065
Magazine Luiza S.A. (Magalu) CS-022
Best Buy Co., Inc. CS-072
T-Mobile US, Inc. CS-073
Slater and Gordon Limited CS-109
Arabtec Holding PJSC CS-113
CD PROJEKT S.A. CS-121
OCP Group (OCP S.A., formerly Office Chérifien des Phosphates), majority-owned by the Moroccan state CS-136
Hikma Pharmaceuticals PLC (established in Amman, Jordan, in 1978; listed in London from 2005) CS-140
Waberer's International Nyrt. (Waberer's), listed on the Budapest Stock Exchange CS-141
Eicher Motors Limited (Royal Enfield), part of the Eicher Group, New Delhi CS-151
Kenya Revenue Authority (KRA), the national tax administration of Kenya CS-159
Marimekko Corporation (Marimekko Oyj), Helsinki-based design house listed on Nasdaq Helsinki CS-164
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.

