BP-064Grade B30 supporting cases (29 counted), 0 counter-examples
Map critical dependencies several tiers deep, buffer what cannot be re-sourced, and decide who pays for resilience
The practice
Map supply and other critical dependencies (sub-tier suppliers, a seller's transitional services, a rival's software, feedstock) before a crisis, hold deliberate buffers for what cannot be re-sourced quickly, and agree explicitly who bears the cost.
Why it works
Supply chains often hide concentration: many direct suppliers can share one sub-tier source, and a disruption there stops everything. Mapping several tiers deep before a crisis turns hidden concentration into known risk. Lean does not mean zero stock everywhere; buffers for parts that cannot be re-sourced quickly buy time to act, though not protection against a long shock. Dependencies on a seller after an acquisition, or on a rival, need the same treatment, settled in writing for a fixed term. In feedstock-constrained businesses, securing supply comes before building capacity. Resilience has a cost, and deciding explicitly who pays prevents it from being cut in the next cost round.
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
- Map critical inputs to sub-tier sources and identify single points of failure.
- Hold buffers sized to re-sourcing time for parts that cannot be dual-sourced.
- Settle transitional and rival dependencies in written, fixed-term agreements.
- Secure feedstock or critical inputs before committing capacity.
- Agree who pays for resilience (company, supplier, customer) and record it.
Warning signs
- Supplier maps stop at tier one.
- Buffers are removed in a working-capital drive without risk review.
- Critical services are provided by a seller with no exit date.
When it applies
- Manufacturing, automotive, electronics, renewable fuels and post-acquisition transitions.
When it does not
- Commodity inputs with deep, liquid markets.
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
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.

