Skip to content

All best practices

BP-071Grade B23 supporting cases (20 counted), 0 counter-examples

Build the enabling architecture and infrastructure before the applications that depend on it

The practice

Put the data architecture, network, distribution-centre instrumentation and IT operations in place before (or with) the applications and front-end changes that rely on them.

Why it works

Applications and front-end changes deliver value only if the infrastructure beneath them works. Instrumenting the distribution centre before the store, building the architecture before buying applications, and investing in the core network as the platform for digital businesses set the foundation the visible change needs. Bringing IT operations into the new delivery model prevents speed stalling at the infrastructure. Putting new data capture on infrastructure the operation already uses reduces cost and adoption risk.

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

  • Define the target architecture before selecting applications.
  • Instrument upstream operations (warehouses, networks) before downstream ones (stores, apps).
  • Include IT operations and infrastructure teams in the new operating model.
  • Reuse infrastructure the operation already has for new data capture where possible.

Warning signs

  • Applications are bought before the architecture is agreed.
  • Agile teams wait weeks for infrastructure.
  • Front-end launches precede the back-end data they need.

When it applies

  • Digital, RFID, IoT and agile operating-model programmes.

When it does not

  • Small front-end experiments that can run on existing infrastructure.

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
  • T01 Digital
  • T07 Supply chain
  • T10 Market entry and expansion
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Critical skills are missing or becoming obsolete
  • Inventory is simultaneously excessive and unavailable
  • Operations cannot meet demand efficiently
  • Service delivery is too slow, unreliable or expensive
  • Competing transformation programs overwhelm resources
Function
  • Supply Chain & Logistics
  • IT, ERP & Digital
  • Customer Experience & Support
  • Procurement & Strategic Sourcing
  • Manufacturing & Production
  • Data, Analytics & AI
Starting situation
  • New initiative
  • In-flight initiative
Industry
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Grocery and Food Retail
  • Hospitals and Health Systems
  • Industrial Distribution and Wholesale
  • Other (cross-industry)
  • Specialty Retail and Omnichannel Commerce
  • Telecommunications, Broadband and Fiber
Region
  • Africa
  • Central and Eastern Europe
  • East Asia
  • Global
  • Latin America
  • Middle East
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

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.