BP-011Grade B32 supporting cases (30 counted), 0 counter-examples
Simplify what you sell and the rules you run before you automate or scale them
The practice
Cut the product range, brand portfolio, pay or business rules and management measures to what is needed before building systems or scaling operations around them.
Why it works
Complexity is multiplied, not removed, by automation: every product variant, award rule or exception becomes configuration, test cases and failure modes. Simplifying first shrinks the build, the test surface and the training load, and it exposes which complexity customers actually value. The same logic applies to the range: a pruned line restores the signature products, frees working capital and makes the operation easier to run. Simplification is hardest when it is attempted after the system has failed, because by then the rules are embedded in code and contracts. Rules that engineers or designers can apply at the design stage keep complexity from returning.
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
- Inventory the products, brands, rules and measures in scope and their revenue or cost contribution.
- Retire or merge the long tail before design starts; set a target count for each.
- Scope rule-heavy domains (pay, pricing, claims) by their rules, not by analogy with a simpler implementation.
- Give designers explicit complexity rules (component counts, approved variants) they can apply themselves.
- Re-measure complexity at each gate; growth is an escalation item.
Warning signs
- Requirements are being gathered by copying every current rule into the new system.
- Variant or SKU counts rise during a cost programme.
- No one owns the rulebook being automated.
When it applies
- Payroll, billing, pricing and product-configuration systems.
- Turnarounds and brand repositioning where the range has sprawled.
When it does not
- Where variety is the proposition and the operation is built to deliver it profitably.
- Regulated rules the company cannot change; simplify the process around them instead.
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. 2 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
Queensland Health (State of Queensland), with IBM as prime contractor CS-003
Government of Canada (Public Services and Procurement Canada) CS-038
Lenovo Group CS-049
Apple Computer, Inc. CS-086
Burberry Group plc CS-074
The LEGO Group CS-007
Singapore Airlines Limited CS-056
The Procter & Gamble Company CS-046
Avianca Holdings S.A., reorganised as Avianca Group International Limited CS-126
TOTVS S.A. CS-127
Bancolombia S.A. (Grupo Bancolombia, renamed Grupo Cibest) and its digital platform Nequi CS-129
Thai Airways International Public Company Limited (THAI) CS-131
Virgin Australia Holdings (Virgin Australia Group), owned by Bain Capital from November 2020 CS-134
MonotaRO Co., Ltd. (Tokyo Stock Exchange), majority-owned by W.W. Grainger, Inc. since 2009 CS-143
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.

