Infrastructure Resilience – A Leadership Lens for 2026
In our recent article, When Infrastructure Resilience Becomes the Battlefield, we explored a shift that is no longer theoretical. Infrastructure has moved from background utility to a point of leverage, shaping how organisations operate, compete, and deliver.
The response to that piece reinforced a simple truth. Most organisations recognise that the environment has changed. Far fewer have translated that awareness into a clear, shared way of thinking about resilience.
That is where the A to Z of Infrastructure Resilience sits.
This is not a glossary, and it is not a framework in the traditional sense. It is a leadership lens. This is not intended to be exhaustive. It is intended to be useful. A way of naming the concepts, pressures, and trade-offs that now define infrastructure resilience in 2026.
Each element is deliberately simple in isolation. Taken together, they form a more complete picture of how organisations hold, or break, under pressure. Used well, this is not something to read once. It is something to return to. To test assumptions, challenge thinking, and shape better decisions over time.
Infrastructure resilience is no longer a technical conversation, but a leadership one.
All examples in this A to Z of Infrastructure Resilience are fictitious but plausible scenarios set in 2025–early 2026. They are designed to illustrate each concept in a concrete, relatable way while remaining entirely fictional.
A — Access
Description
Access is no longer just about availability. It is about whether critical infrastructure, systems, or resources are available to you when it matters, and on what terms.
Insight
In 2026, access has become a strategic variable. Systems may be operational, but that does not guarantee your organisation can use them. Prioritisation, restriction, and external control are now part of the equation.
Example
In Q1 2026, a major European manufacturer lost access to its primary cloud region during a geopolitical flare-up. The systems remained fully operational, but the provider prioritised government and defence workloads, throttling the company for 11 days. Revenue impact: €47m. The infrastructure didn’t fail; access was deliberately restricted.
Leadership Question
Where could our access to critical infrastructure be restricted, even if the system itself remains operational?
Pitfalls / Red Flags
- Assuming availability equals access
- No visibility of allocation or priority rules
- Over-reliance on single providers or regions
B — Buffers
Description
Buffers are the deliberate reserves built into systems to absorb disruption.
Insight
Many organisations rebuilt buffers post-pandemic, then quietly removed them as cost pressures returned. This resilience relapse has reintroduced fragility exactly where it hurts most.
Example
A global logistics firm rebuilt inventory buffers after the 2022–23 crises, then cut them by 40 % in 2025 to hit quarterly cost targets. When a key Asian port strike hit in February 2026, the firm had no slack and missed 3,200 container deliveries in the first week. Customer penalties exceeded the savings made the previous year.
Leadership Question
Where have we removed buffers, and what risks did we reintroduce?
Pitfalls / Red Flags
- Treating buffers purely as cost
- No record of what was removed
- Efficiency decisions made without risk context
C — Choke Points
Description
Choke points are narrow parts of a system where disruption has a disproportionate impact.
Insight
Risk is rarely distributed. It is concentrated. Disruption tends to occur at pressure points, not across entire systems.
Example
A Tier-1 automotive supplier mapped only its direct vendors until a 2026 Red Sea disruption took out a second-tier rare-earth processor in Malaysia. The part was invisible on their risk register. Production lines stopped for 19 days. The company later admitted it had no idea the choke point existed beyond Tier 1.
Leadership Question
Where are the choke points in our operating model?
Pitfalls / Red Flags
- Mapping suppliers but not routes
- Assuming diversification without testing
- No scenario planning around specific failures
D — Dependencies
Description – Dependencies are the external systems and infrastructure your organisation relies on.
Insight – Most organisations underestimate both the number and criticality of their dependencies. They are known in parts, but rarely understood as a whole.
Example – A leading UK fintech discovered in a 2026 stress test that 87 % of its real-time transaction processing depended on three obscure US-based API providers it had never listed as critical. When one provider suffered a six-hour outage triggered by a regulatory audit, the fintech’s entire payment rail went dark across Europe.
Leadership Question – Do we have a single, shared view of our critical dependencies?
Pitfalls / Red Flags
- Assumed understanding across teams
- Fragmented ownership
- No unified mapping
E — Energy
Description
Energy underpins physical and digital operations.
Insight
Energy is no longer just a cost line. It is a constraint, a risk, and a lever. Even energy transition strategies introduce new dependencies and single points of failure.
Example
A data-centre operator in Ireland hit its renewable energy cap under new grid rules in late 2025. Even though it held long-term “green” Power Purchase Agreements, the grid operator curtailed supply during winter peaks. The operator was forced to buy expensive diesel backup or risk breaching SLAs with hyperscale clients — turning a sustainability win into an operational liability.
Leadership Question
How exposed are we to disruption in energy availability, not just price?
Pitfalls / Red Flags
- Treating energy as procurement only
- No contingency beyond pricing
- Hidden dependencies in “green” initiatives
F — Fragility
Description
Fragility is the hidden weakness created by over-optimisation.
Insight
Efficiency often removes the very slack needed to absorb disruption. Fragility is rarely visible until failure occurs.
Example
A precision-engineering group had optimised its European plants to 98 % capacity utilisation for three straight years. When a single supplier’s cyber incident halted a specialised alloy in March 2026, the entire network lost 14 days of output because there was literally no spare capacity anywhere in the system.
Leadership Question
Where have we optimised ourselves into vulnerability?
Pitfalls / Red Flags
- Zero tolerance for inefficiency
- No stress testing
- Overconfidence in stable conditions
G — Governance
Description – Governance defines how decisions are made, escalated, and owned.
Insight – In disruption, speed matters, but clarity matters more. Weak governance slows response or creates confusion.
Example – During a 2026 cyber-induced port closure, a global retailer’s crisis team spent 48 hours debating who had authority to activate the pre-approved contingency contract. By the time the decision was made, perishable stock worth £18m had already spoiled in holding yards.
Leadership Question – Can we make and execute critical decisions quickly under pressure?
Pitfalls / Red Flags
- Decision paralysis in crises
- Unclear ownership
- Overly complex escalation
H — Hedging
Description
Hedging is the use of financial or contractual tools to manage risk.
Insight
Financial hedging can manage price volatility but does little to address physical disruption or access constraints.
Example
A North American airline had locked in jet-fuel prices through sophisticated financial hedges for 2026. When a major Gulf refinery was taken offline by a missile strike, physical fuel simply wasn’t available at any price. The hedges protected the balance sheet but could not keep aircraft flying.
Leadership Question
Where are we relying on financial protection to solve operational risk?
Pitfalls / Red Flags
- Overconfidence in financial instruments
- No operational fallback
- Confusing cost protection with resilience
I — Infrastructure
Description
Infrastructure is the foundation on which operations depend.
Insight
Infrastructure has shifted from passive utility to active leverage. It can now be constrained, controlled, or disrupted intentionally.
Example
A mid-sized German chemical producer relied on a single undersea fibre cable for 100 % of its transatlantic SCADA traffic. In January 2026 the cable was severed by an anchor incident; the company’s entire European control network went blind for 39 hours because it had never treated the cable as strategic infrastructure.
Leadership Question
How exposed are we to infrastructure we do not control?
Pitfalls / Red Flags
- Treating infrastructure as “given”
- No strategic view of dependencies
- Ignoring external control dynamics
J — Just-in-Time
Description
Just-in-time is a model designed to minimise inventory and maximise efficiency.
Insight
It no longer holds in isolation. Without buffers or alternatives, it creates systemic vulnerability.
Example
A mid-sized German chemical producer relied on a single undersea fibre cable for 100 % of its transatlantic SCADA traffic. In January 2026 the cable was severed by an anchor incident; the company’s entire European control network went blind for 39 hours because it had never treated the cable as strategic infrastructure.
Leadership Question
Where are we still relying on just-in-time assumptions?
Pitfalls / Red Flags
- No fallback capacity
- Over-reliance on speed
- Ignoring disruption scenarios
K — Knowledge
Description – Knowledge is the organisation’s understanding of its own system.
Insight – Many organisations operate with partial or outdated knowledge of how they truly function under stress.
Example – A global bank’s operational-risk team conducted its annual review in late 2025 using documentation that had not been updated since the 2023 cloud migration. When a critical database cluster failed in February 2026, no one in the response room knew the manual failover procedure still worked — because the person who wrote it had left two years earlier.
Leadership Question – Do we understand how our organisation actually operates under disruption?
Pitfalls / Red Flags
- No cross-functional visibility
- Assumed knowledge
- Outdated documentation
L — Leverage
Description
Leverage is the ability for external forces to influence your operations.
Insight
In 2026, leverage sits outside the organisation. Others may control the systems you depend on.
Example
A Scandinavian food retailer discovered in 2026 that its largest logistics partner could unilaterally raise access fees by 300 % after a new EU regulation changed cabotage rules. The partner exercised that leverage within 48 hours, forcing the retailer to absorb the cost or lose shelf availability in three key markets.
Leadership Question
Who has leverage over our ability to operate?
Pitfalls / Red Flags
- Ignoring external control
- No awareness of dependency power dynamics
- Overconfidence in contracts
M — Mapping
Description
Mapping is the process of understanding dependencies and relationships.
Insight
Without mapping, organisations rely on assumptions. With mapping, they see exposure clearly.
Example
A major Australian mining company had “mapped” its supply chain at the corporate level but never below Tier 2. When a small Chilean lithium processor declared force majeure in early 2026, the company realised too late that 62 % of its future battery-grade supply flowed through that single facility.
Leadership Question
Have we mapped our dependencies beyond surface level?
Pitfalls / Red Flags
- High-level mapping only
- No ownership
- No updates over time
N — Net Zero
Description
Net Zero strategies aim to reduce carbon impact.
Insight
They often introduce new dependencies in supply chains, materials, and technologies — sometimes creating fragility in the name of sustainability.
Example
A European steelmaker accelerated its switch to hydrogen DRI in 2025 to meet net-zero targets. When electrolyser-grade nickel supply tightened in Q1 2026, the company faced a six-month production shortfall. The green transformation had created a new, narrower dependency than the coal it replaced.
Leadership Question
Are our sustainability strategies creating new risks?
Pitfalls / Red Flags
- Blind faith in green solutions
- Ignoring supply chain exposure
- No diversification
O — Operational Autonomy
Description – Operational autonomy is the ability to function independently.
Insight – True autonomy is rare. Most organisations rely heavily on external systems and permission to operate.
Example – A Singapore-based pharma logistics firm assumed it could operate independently until a 2026 government directive required all cold-chain operators to use a new national digital tracking platform. Refusal meant loss of operating licences. Autonomy evaporated overnight.
Leadership Question – Where do we depend on external permission to operate?
Pitfalls / Red Flags
- Ignoring jurisdictional risk
- Assumed control
- No contingency
P — Procurement
Description
Procurement governs how organisations select suppliers.
Insight
Resilience is now a selection criterion. Weak suppliers are filtered out early.
Example
A US semiconductor fabricator chose its lowest-cost Asian substrate supplier in late 2025 after a price-only tender. When that supplier was hit by export controls in March 2026, the fabricator faced a 14-week lead-time gap and had to pay 400 % spot-market premiums because no resilience criteria had been applied in procurement.
Leadership Question
Would we pass a rigorous procurement risk assessment today?
Pitfalls / Red Flags
- Focus on cost only
- No resilience proof
- Weak supplier positioning
Q — Questions
Description
Questions define the quality of leadership thinking.
Insight
The right questions surface risk early. The wrong ones hide it.
Example
The board of a European utility spent an entire strategy offsite in 2025 asking only “How do we reduce costs by 12 %?” rather than “Where could our access to critical grid infrastructure be restricted?” Six months later a regulatory order limited their draw on the high-voltage network during peak winter demand — a scenario they had never surfaced.
Leadership Question
Are we asking the questions that expose risk, or the ones that let us avoid it?
Pitfalls / Red Flags
- Surface-level discussions
- Avoiding uncomfortable topics
- Overconfidence in answers
R — Resilience
Description
Resilience is the ability to absorb and adapt to disruption.
Insight
It is not a plan. It is a capability embedded in decisions and systems.
Example
A global shipping line had a 180-page resilience plan updated quarterly. When a 2026 cyber attack disabled its vessel-tracking system, the plan sat untouched on a SharePoint site while captains improvised for 72 hours. Resilience was documented but not embedded in how the organisation actually operated.
Leadership Question
Is resilience built into how we operate, or documented separately?
Pitfalls / Red Flags
- Treating resilience as compliance
- No integration into strategy
- Over-reliance on plans
S — Supply Chains
Description – Supply chains connect inputs to outputs.
Insight – They are now exposed, extended, and vulnerable to disruption at multiple points.
Example – A major consumer electronics firm had full visibility to Tier 1 suppliers but assumed Tier 2 and 3 were stable. In Q2 2026 a factory fire at a Tier-3 capacitor manufacturer in Vietnam (unknown to them) halted production of a key component. The firm lost 8 weeks of flagship product output because the dependency chain was never fully mapped.
Leadership Question – How resilient is our supply chain beyond Tier 1 suppliers? When was the last time we reviewed our infrastructure resilience?
Pitfalls / Red Flags
- Over-reliance on key routes
- Limited visibility
- No diversification
T — Trust
Description
Trust is the confidence customers place in your ability to deliver.
Insight
Trust is built through consistency and lost through disruption to infrastructure resilience.
Example
A UK grocery chain promised same-day delivery as a point of competitive differentiation. When a 2026 heatwave caused widespread refrigeration failures across its third-party logistics network, 42,000 orders were cancelled or delayed. Social-media sentiment turned negative within hours and same-day sales dropped 31 % for the following quarter.
Leadership Question
What happens to customer trust when we fail?
Pitfalls / Red Flags
- Ignoring customer perception
- No communication strategy
- Reactive responses
U — Uncertainty
Description
Uncertainty is the unknown element of disruption.
Insight
Not everything can be predicted, but much can be prepared for.
Example
A North Sea oil operator treated geopolitical risk as “unpredictable” and therefore not worth detailed planning. When new sanctions were announced in February 2026, the team had no pre-agreed playbooks. Three weeks of internal debate delayed a critical platform shutdown decision, exposing the company to regulatory fines.
Leadership Question
Where are we mistaking uncertainty for unpredictability?
Pitfalls / Red Flags
- No scenario planning
- Over-reliance on forecasts
- Lack of preparation
V — Visibility
Description
Visibility is the ability to see issues early.
Insight
Delayed visibility leads to delayed response and increased impact.
Example
A major Asian electronics contract manufacturer relied on weekly supplier reports for component health. When a key Taiwanese chip foundry experienced a covert ransomware attack in early 2026, the manufacturer only learned of the issue 11 days later — after customer orders had already been missed.
Leadership Question
How quickly can we detect disruption?
Pitfalls / Red Flags
- Lagging indicators
- Siloed data
- Poor monitoring
W — Workforce
Description
Workforce resilience reflects people’s ability to operate under pressure.
Insight
Human factors are often overlooked but critical in disruption.
Example
A European airport operator had optimised staffing to 92 % utilisation across its ground-handling teams. When a 2026 labour dispute triggered simultaneous sick-outs at two major hubs, the operator could not maintain turnaround times. 217 flights were cancelled in the first 48 hours and passenger compensation claims exceeded €9m.
Leadership Question
How resilient is our workforce under sustained pressure?
Pitfalls / Red Flags
- Burnout
- Lack of contingency
- No flexibility
X — Exposure
Description Exposure is the degree to which your organisation is at risk.
Insight Exposure is often hidden and underestimated.
Example
A global cloud software provider believed its exposure was limited because 95 % of revenue came from enterprise contracts. In March 2026 a new data-sovereignty law in its largest market required local data residency within 90 days. The provider suddenly faced a €240m unplanned capex bill it had never modelled.
Leadership Question Where is our true exposure?
Pitfalls / Red Flags
- Misjudged risk
- Overconfidence
- Lack of data
Y — Yield
Description
Yield is the output achieved under pressure.
Insight
High activity does not equal high outcome. Under disruption, many organisations mistake effort for impact.
Example
A high-volume e-commerce fulfilment centre reported record throughput during a 2026 cyber-induced supplier disruption — teams were working 24/7 to clear backlogs. Yet net order fulfilment dropped 18 % because the extra activity was spent expediting partial shipments rather than complete customer orders.
Leadership Question
Are we measuring effort or actual impact?
Pitfalls / Red Flags
- Activity bias
- No outcome tracking
- Misaligned metrics
Z — Zero Illusions
Description
Zero Illusions is the commitment to see reality clearly.
Insight Resilience starts with honesty.
Example
The executive team of a mid-sized industrial group repeatedly told investors that “our diversified supplier base protects us.” A 2026 single-point failure in a shared European rail hub exposed that 73 % of their critical raw materials moved on the same corridor. The illusion held until the moment it didn’t.
Leadership Question
Where are we telling ourselves a story that is not true?
Pitfalls / Red Flags
- Denial
- Overconfidence
- Avoiding hard truths
Final Reflection on Infrastructure Resilience
Across these twenty-six elements, a consistent pattern emerges. Infrastructure resilience is not defined by any single factor. It is shaped by the interaction between dependencies, decisions, and behaviour under pressure.
Most organisations do not lack intelligence, capability, or intent. What they often lack is clarity. A clear view of what they depend on, where they are exposed, and how those exposures translate into customer impact. That gap matters.
In 2026, infrastructure resilience is no longer judged internally. It is judged externally; by stakeholders, customers, by partners, and increasingly by procurement and risk functions that are actively filtering out organisations that cannot demonstrate stability.
The shift is subtle but significant. Infrastructure resilience is no longer about recovery or about efficiency. It is about continuity and access, and it is no longer something that can be delegated. It sits firmly with leadership.
The organisations that thrive in this environment will not be the ones with the most detailed plans or the most sophisticated models. They will be the ones that have made deliberate decisions about what they depend on, what they control, and what they are willing to risk.
Everything else follows.