Is the supply chain network underneath your strategy one you would design if you were starting from scratch?
Most leadership teams inherit a supply chain and rarely question its design. They didn’t choose it; it came with the business. Evolved over time and shaped by past decisions in a different macro environment.
But the conditions that made these networks workable are rapidly changing. Recent geopolitical tension, tariffs and shifting trade flows, rising input costs, and growingregulatory pressure are making it harder to perform well within networks that were not deliberately designed. What once felt like a stable foundation is starting to hold businesses back.
As a result, supply chain network design has moved into focus for many organisations. This is understandable, but it also points to something more fundamental. These pressures don't create problems so much as reveal them, much in the same way that Covid revealed the lack of resilience and flexibility in many networks. They expose the consequences of networks that evolved reactively, without ever being examined as a whole.
The key question is not just how to respond to today's pressures, but whether the network underneath your strategy is the one you'd design if you were starting from scratch.
One of the more common misconceptions in supply chain is that network design is something you look at when something goes wrong. A response to events such as a cost blowout, a post-acquisition integration, or a lease expiry that forces the question. In that sense, it becomes a standalone project with a beginning and an end, after which things return to normal. However, this framing undersells it significantly.
In any operating environment, how a network is structured plays a central role in shaping what an organisation can do, and at what cost. Every system operates within constraints and every configuration involves trade-offs. Those trade-offs were always being made, but more often by default rather than deliberately.
A review of the supply chain network doesn't change this reality. However, it does is make the trade-offs visible, so decisions are guided by intent and evidence rather than habit or assumption. This reflects disciplined management rather than reactive crisis response.
Most of the discussion around supply chain network design gets caught up in the mechanics of optimisation models, scenario analysis, facility location, and optimal flowpaths. These technical details matter but can also obscure something more important.
The structure of a network determines what a business can actually do. Cost positions, service commitments, growth ambitions, resilience, and capital allocation are all enabled or constrained by the network long before they're debated in a boardroom. In that sense, network design isn't a supply chain question sitting downstream of strategy, it's a strategic question in its own right.
A strategy that the network can't support isn't really a strategy. It's an unrealistic aspiration.
This matters most when strategy is changing. Entering a new market, acquiring a business, shifting a service proposition, responding to margin pressure; each of these has network implications that will either accelerate execution or work against it. The organisations that think about network design in that context, as a mechanism for translating strategic intent into operational reality, tend tomove faster and with fewer surprises than those that treat it as a separate exercise.
Seven-Eleven Japan offers one of the clearest illustrations of what it means to treat a supply chain network as a strategic asset rather than an operational necessity.
When Seven-Eleven entered the Japanese market in 1974, convenience retail was not a well-defined category. What the company built over the following decades was not just a store network, it was a distribution system deliberately designed to make rapid, frequent replenishment economically viable at scale. Rather than optimising for the lowest cost per delivery, the network was designed around a different objective: getting the right product to the right store multiple times a day with minimal inventory held at store level.
The implications of that design choice ran through the entire business. Stores were clustered deliberately and new locations were opened within existing density zones to improve the economics of shared distribution, rather than chasing revenue in isolation. A single distribution centre could serve a dense cluster of stores with high delivery frequency and low per-unit cost. The network structure made the service model possible, and the service model justified the network investment.
Seven-Eleven didn't build a supply chain to support their stores. They built stores in a way that made their supply chain more powerful.
The results speak to what intentional design unlocks. By 2004, Seven-Eleven had grown to over 10,000 stores in Japan alone. Convenience store operations contributed 90% of the parent company’s total operating income from only 48% of revenue. The margin profile was a direct consequence of network efficiency, and that efficiency was a direct consequence of deliberate design choices made decades earlier.
Contrast that with organisations that locate facilities reactively, and the difference in long-run performance is significant. It's not that the reactive decisions were incorrect at the time they were made, but that they accumulate into a network that no longer serves the strategy well, and is very expensive to unwind.
One of the more revealing conversations in a network design review is the one about objectives. Ask a leadership team what they want from their supply chain and you'll often hear something that sounds reasonable but is inherently contradictory e.g. lowest cost, broadest range, fastest delivery, maximum flexibility. All at once.
This isn’t a failure of ambition; it’s a failure of visibility. When the trade-offs between those objectives aren't quantified, they remain abstract, and abstract trade-offs tend to get resolved by whoever argues most persuasively, or whoever has the most urgent problem in front of them.
When you quantify the trade-offs, it changes the quality of the conversation. For example, when you can show that reducing lead times by 40% requires either two additional distribution centres or a 15% increase in freight cost, the discussion shifts. It's no longer about competing preferences but about tangible consequences. Leaders can engage with the evidence, test their assumptions, and make choices with a clearer understanding of what each option implies.
In my experience, this is where supply chain network design creates some of its most immediate value. Not in the final recommendation, but in the process of making trade-offs legible to people who need to make decisions about them. This is something to be built as an organisational capability, not delivered once and forgotten.
In practice, one of the persistent challenges in network design is finding tools that are both rigorous and usable. Simpler approaches (maturity assessments, rule-of-thumb frameworks) are accessible and fast, but they tend to miss structural nuances that can have a material bearing on the outcome. More sophisticated platforms offer depth and precision, but require significant data, time, and specialist capability to run well, and even more to maintain over time.
The result is that many organisations either over-simplify the analysis and make decisions with incomplete information or invest heavily in a study that produces a detailed answer but is difficult to interrogate, explain, or revisit when conditions change.
The more useful consideration isn't about the tool itself, but what the analysis needs to be fit for. A good network design process produces outputs that are decision-ready, clear enough to act on, transparent enough to challenge, and structured in a way that allows the key assumptions to be tested as circumstances evolve.
Even when the analysis is well-constructed and the preferred design is clear, the hardest work often still lies ahead. Network decisions cut across commercial priorities, operational constraints, customer commitments, and capital programmes. The path from preferred design to implemented reality is rarely straightforward.
What tends to separate organisations that realise the value of a network redesign from those that don't is sustained engagement through implementation and the willingness to work through sequencing decisions, manage trade-offs as they surface, and keep the original intent in view as the complexity of execution unfolds. Treating network design as a one-off analytical exercise, rather than a process that extends through to delivery, remains a common and costly mistake.
In any environment, what strengthens organisations over time is not any single model or initiative, but the ability to see clearly, decide deliberately, and follow through. Supply chain network design becomes a powerful lever when it sharpens those capabilities and when it connects strategy to operational feasibility, makes trade-offs visible and comparable, and stays engaged through the difficult reality of implementation.
The organisations that will get the most from out of this process are those that treat it as an ongoing discipline rather than a periodic project. Used consistently rather than in moments of peak pressure, to ensure the network underpinning your strategy remains intentional.
If there’s uncertainty about whether the network you have is truly supporting your strategy, it’s worth exploring deliberately. That’s a conversation we’re always open to.