Global stability is dead. Your savings model should reflect that.
Procurement teams still get measured like stability is the default: unit price down, year-on-year savings up, supplier count rationalised. That scorecard worked when disruption was occasional. Now disruption is the baseline—geopolitical volatility, export controls, sanctions risk, port constraints, cyber incidents, and sudden demand swings don’t arrive as “events.” They overlap.
The uncomfortable implication: the cheapest award can be the most expensive decision. Not because risk is new, but because the frequency and correlation of disruptions changes the maths. If a category is exposed to repeated shocks, the right procurement question stops being “What’s the best price?” and becomes “What’s the cheapest way to keep operating?” That’s resilience by design.
Reactive crisis management is a cost centre. Continuous risk orchestration is an operating capability.
Most organisations still run supplier risk like a smoke alarm: it’s quiet until it isn’t. A crisis hits, a war room forms, spreadsheets fly around, and someone asks for a supplier list that should have existed yesterday. After the fire is out, the organisation slowly forgets—until the next one.
Continuous risk orchestration is different. It treats supply risk like credit risk in a bank: monitored continuously, modelled, and acted on through defined triggers. Veriscape’s emerging resilience themes point in this direction—moving from periodic assessments to always-on visibility and response. Inverto (BCG) has been equally blunt in its work on geopolitical volatility: companies need structured playbooks and diversified supply strategies, not ad-hoc heroics.
What changes in practice
Instead of quarterly supplier reviews, you run a live risk posture per critical supply node: what’s happening in the supplier’s region, what routes are constrained, which sub-tier materials are brittle, and where you have contractual or logistical options. The output isn’t a report; it’s decisions—reroute, rebalance volumes, pre-buy, qualify alternates, or accept the risk with eyes open.
Risk signals are tied to actions (not dashboards): e.g., a sanctions update triggers an immediate sub-tier exposure check and a volume reallocation rule.
Categories are segmented by “time-to-recover” and “time-to-survive,” not just spend and supplier count.
Supplier performance includes responsiveness and recovery behaviour under stress, not only OTIF in calm periods.
Contracts are written for optionality: volume flex, defined lead-time bands, and pre-agreed substitution pathways where compliance allows.
Digital twins: useful when they’re boring, dangerous when they’re theatre
Digital twins are getting pitched as a magic mirror: model your supply chain, simulate disruption, pick the best move. The value is real—if you keep the scope tight and the data honest. The trap is building a beautiful model that can’t be maintained, or worse, a model that assumes away the messy parts (sub-tier opacity, capacity constraints, real lead-time variability).
A pragmatic twin for procurement starts with a handful of flows that can actually stop the business: a critical component family, a constrained raw material, a single-source packaging format, a region-specific service capability. Model the decisions you will actually make: how fast can you shift 30% of volume, what does it do to unit cost, what happens to working capital, what lead-time penalty is tolerable, and which compliance gates block substitution.
Where digital twins pay off fastest
What-if scenarios you can’t spreadsheet: port closure plus carrier capacity reduction plus demand spike—combined effects matter more than single-variable analysis.
Allocation rules across suppliers: shifting volume is rarely linear; capacity, MOQ, and ramp rates create step changes.
Inventory strategy tied to disruption probability: not “add safety stock,” but “hold targeted buffers where recovery time is longest.”
Supplier development prioritisation: the twin shows which constraint is worth funding—tooling, test capacity, dual-qualification, or logistics redesign.
Nearshoring isn’t a patriotic slogan. It’s a lead-time and control strategy—with a price tag.
Nearshoring is often sold as a simple fix: move closer, reduce risk. The reality is more nuanced. You can reduce transit risk, shorten replenishment cycles, and gain better oversight. You can also pay more per unit, face tighter labour markets, or discover that the nearshore region depends on the same upstream inputs you were trying to escape.
The most defensible use of nearshoring is selective: apply it where lead-time is your enemy and where demand variability punishes long pipelines. Nearshore for responsiveness and continuity, keep some farshore volume for cost efficiency, and design the split so you can swing volume when disruption hits. That’s resilience by design: you’re buying options, not just capacity.
Multi-sourcing ecosystems beat “dual sourcing” when sub-tiers are the real bottleneck
Dual sourcing is often procurement’s comfort blanket: two suppliers, problem solved. Except many disruptions don’t happen at tier one. They happen at the shared sub-tier: the same pigment producer, the same chip fab, the same casting foundry, the same logistics choke point. Two logos on a slide can still be one point of failure.
A multi-sourcing ecosystem approach looks beyond supplier count and focuses on independence: different geographies, different sub-tier inputs, different production technologies, and different routes to market. It’s harder work—qualification effort, engineering involvement, more complex SRM—but it creates genuine redundancy.
A practical independence test for your “backup” supplier
Do they rely on the same sub-tier for the critical input or process step?
Do they ship through the same ports, carriers, or border crossings?
Are they exposed to the same regulatory regime (export controls, sanctions, data residency, local content rules)?
Is their capacity actually available, or is it theoretical unless you pre-book it?
Can you switch without revalidation, recertification, or customer approval—and how long does that really take?
Resilience by design changes the savings conversation (and that’s the point)
Traditional savings can be easy to audit and easy to celebrate. Resilience value is harder: it’s the cost you didn’t incur, the revenue you didn’t lose, the customer you didn’t disappoint. That makes it tempting to underinvest—until disruption makes the invoice visible.
My view: procurement should stop apologising for resilience spend and start pricing the alternative. If you can’t estimate the cost of a two-week outage in a critical category, you don’t have a savings baseline—you have a hope. The best teams quantify exposure ranges (not fake precision), agree risk appetite with leadership, and then treat optionality as a managed portfolio.
How to make it measurable without pretending you can predict everything
Define “critical supply” in operational terms: what stops shipment, what stops production, what breaches regulatory commitments.
Track time-to-switch and time-to-recover per category, then fund the biggest gaps (qualification, tooling, inventory, logistics).
Create a resilience P&L view: incremental unit cost, incremental working capital, and the estimated outage exposure they reduce.
Write resilience into sourcing decisions: award criteria include independence, ramp capacity, and disruption responsiveness—not just price and OTIF.
Run quarterly disruption drills on the top categories: not tabletop theatre—actual supplier calls, actual allocation decisions, actual lead-time verification.
The procurement operating model that fits the new baseline
If disruption is constant, resilience can’t live as a side project in risk management. It has to sit inside category strategy, supplier management, and S&OP/IBP rhythms. That means clear ownership (who pulls the trigger on volume shifts), clean data pathways (what signal is trusted), and pre-agreed trade-offs (when cost gives way to continuity).
You don’t need to predict the next shock. You need a supply network designed to absorb shocks routinely—through digital twins that inform real decisions, nearshoring used surgically, and multi-sourcing ecosystems that aren’t secretly single-sourced underneath. That’s why resilience by design isn’t a nice-to-have. It’s the only savings metric that still makes sense when stability is no longer the default.