BP-017Grade B23 supporting cases (20 counted), 0 counter-examples
Outsource only what does not differentiate, and keep the capability to specify, integrate and replace partners
The practice
Outsource work that must scale but does not differentiate, pay partners for output, split work to keep competitive tension, and retain enough in-house engineering to specify, integrate and, if needed, take the work back.
Why it works
Outsourcing transfers work, but rarely the accountability for the outcome. When the buyer loses the engineering depth to specify and oversee what partners do, integration problems surface late and cannot be fixed in-house. Risk transfer on paper is not risk transfer in fact: partners who lack the capacity to carry their share of risk pass it back when it materialises. Contracts that pay for the output sold, split work across vendors and keep a way back preserve leverage. Innovation partnerships need the same discipline as projects: scope, milestones and payment against delivery.
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
- Decide make-or-buy on capability and integration risk, not on return on net assets alone.
- Keep an in-house team able to specify, integrate and replace each critical partner.
- Check each partner's financial and engineering capacity before transferring risk to it.
- Pay for outputs the business sells (capacity delivered, service levels), not inputs.
- Stage the outsourcing of any core capability and keep a documented route back.
Warning signs
- The prime contractor cannot explain a partner's design.
- A single vendor holds most of a critical capability.
- Partner problems are first visible in schedule slips.
- Partnership contracts have no milestones or exit terms.
When it applies
- Network, IT and manufacturing outsourcing; aerospace and engineering supply chains; technology partnerships.
When it does not
- Where the partner's scale and specialisation clearly exceed what the buyer could ever build, and the work is easily re-sourced.
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
The Boeing Company CS-040
Bharti Airtel Limited (formerly Bharti Tele-Ventures) CS-057
The LEGO Group CS-007
County of Marin, California CS-105
Shoprite Holdings Ltd CS-115
Eicher Motors Limited (Royal Enfield), part of the Eicher Group, New Delhi CS-151
Mizuho Financial Group, Inc. and its banking subsidiary Mizuho Bank, Ltd. (Japan) CS-156
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.

