BP-016Grade C13 supporting cases (12 counted), 0 counter-examples
Own the technology that differentiates you, and rebuild the technology organisation before expecting speed
The practice
Build or own outright the technology where it touches the customer or defines the operating model, rebuild the technology organisation and its leadership to deliver it, and rent the rest.
Why it works
Where technology is the source of advantage (ordering, inventory visibility, digital banking, industrial software), outsourcing it hands the advantage and the learning to a vendor and slows the cycle of change. An in-house engineering capability, with authority over IT, shortens delivery and keeps the knowledge after the programme ends. Buying or owning strategic software outright avoids dependence on a partner whose priorities may diverge. The capability takes time to build, which is why several cases rebuilt the technology organisation and its leadership first. The boundary is commodity infrastructure, which is usually better rented unless geography or a rival's control makes renting a constraint.
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
- Classify technology into differentiating, enabling and commodity; own the first, partner for the second, rent the third.
- Rebuild the technology organisation (leaders, engineering skills, ways of working) before committing to speed targets.
- Give the internal technology team authority over IT architecture.
- Own infrastructure only where geography or a rival's control makes renting it a constraint.
- Plan how in-house capability will outlast the programme.
Warning signs
- The customer-facing stack is owned by a vendor on a long contract.
- Delivery speed targets are set before engineering capacity exists.
- Key architectural decisions are made by the system integrator.
When it applies
- Retail, banking, restaurant and industrial companies where digital is part of the proposition.
When it does not
- Where technology is genuinely commodity and scale economies favour specialist providers (see BP-017).
Evidence grade: Grade C
Anything below B. Plausible, but not yet tested in the KB at the B bar.
Why this grade
Grade C by schema 4.10 route: below the B bar of 14 counted cases across 4 primary regions (6 per 100 cases in the knowledgebase, 235 cases). B needs at least 14 counted supporting cases across at least 4 primary regions; this practice has 12 counted case(s) across 6 region(s). 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.

