Every System Is Right, but the Answer Is Still Wrong

This is Article 2 of the Connected or Exposed series, which examines why public sector organisations struggle to answer compound operational questions. [Article 1: Sequential Systems. Simultaneous Crises.]

In the time it takes someone in your organisation to assemble a response brief - pulling headcount from HR, deployment status from the scheduling tool, clearance flags from a separate access management system, contractor coverage from procurement records, and consulting a spreadsheet the operations team maintains because it's always more current than the official system- the Strait of Hormuz closed, opened, and closed again. 

The brief was outdated before it was even presented. A photograph of a moment that had already passed. 

The rules of the game are changing in real time. The geopolitical landscape is shifting swiftly. Alliances are being reshaped, trade rules rewritten, and sanctions regimes imposed and lifted frequently. Climate-related disasters are arriving faster and more forcefully. Execution under these simultaneous constraints is getting more fragile. 

What large-scale responses have already taught us

A few years ago, a devastating earthquake caused widespread destruction and loss of lives. It triggered the largest Urban Search and Rescue (USAR) response since the foundation of the International Search and Rescue Advisory Group (INSARAG) decades ago. Teams from over 90 countries mobilised and worked alongside local and national responders.

What followed demonstrated both the strength of international coordination mechanisms and where they reached their limits.

The INSARAG classification system performed as designed for 49 INSARAG External Classification (IEC)-certified teams who deployed. Their capabilities were known before they arrived: which teams could handle structural collapse, which carried heavy rescue equipment, which had medical capacity on board. For those teams, the compound question had a queryable answer.
But at the peak of USAR operations, 199 international rescue teams were on the ground simultaneously. The remaining 150 were unclassified, meaning no standardised capability baseline existed on arrival. No pre-existing bridge connected them; harmonisation had to be created during the response itself.

The unprecedented disaster was a test of emergency response systems- a reflection of what a compound question looks like when it has to be assembled manually.

This is the surge problem. Every operational decision propagates across systems, dependencies, and missions. Leaders aren’t asking “who has the right skills” but “who can I deploy right now, and what’s the impact elsewhere?”
In today’s complex operating environment, downstream impact is rarely avoidable. Do leaders have the multi-dimensional visibility across their workforce and missions to decide what to impact and how severely? The moment the answer has to cross more than one system, the picture degrades, leaving each system’s answer correct, but the collective answer still wrong.

For planned events, the compound question is known years in advance but maintaining operational readiness gets harder as complexity increases.

France had several years to plan the security operation for Paris 2024. It knew it would need 22,000 private security contractors. The sector had a recognised labour shortage of roughly 20,000 people but no single system could tell the planners where certified capacity actually sat. The Interior Ministry conducted about a million administrative investigations into various staff, and the country designed accelerated training programs for new recruits close to the start of the games. 

This year, a much larger event elsewhere will require the mobilisation of teams across security, transportation, borders, and more- under continuous operational tempo and a constantly evolving threat picture. Spread across countries with varying degrees of infrastructure readiness, it will test public systems such as health care, emergency systems and transit.

The situation isn't unique to surge events. It runs through standing forces. 

In one of the world’s largest navies, several large floating assets are projected to spend more than twice the planned proportion of their service lives in maintenance. Delays driven by shortages of skilled tradespeople and parts dependencies can hold a vessel in dry dock for months beyond schedule. The scale then compounds. When a single specialist role is vacant or a specific supplier cannot deliver, an entire ship waits. 

A second navy offers a sharper version of the same failure. Open-source monitoring of one submarine fleet found that it struggled to put more than one of its five attack submarines to sea at a time. The bottleneck is maintenance: overhauls concentrated across a small set of specialist contractors, dependent on nuclear-qualified engineering capacity that the force does not hold in sufficient depth.

When maintenance stalls, the backlog compounds. The operational commitments held by these vessels have to go somewhere else- to ships still at sea, absorbing demand they were not sized for. Or, because attack submarine fleets cannot rotate normally, the deterrent submarines (the boats that must remain continuously at sea) absorb the pressure instead, extending patrols from the intended three to four months to six months or more. The fleet on paper and the fleet deployable in practice are different numbers and the gap between them is invisible until someone tries to move something.

The problem sits in the connections

The earthquake, the sporting event surge, and the readiness struggles are not technology failures but structural problems. The question in each context is compound: geography plus certification plus availability plus dependency plus authority. The organisations that come closest to answering it are those that model how things relate, not just what things are.

A person isn't a record in an HR system. They sit inside a web of skills, certifications, assignments, legal authorities, and operational commitments that together determine what they can do, where, and what breaks downstream if they're moved. Linking that data - in a form that can be acted on - and navigating the web in real time, across organisations, across jurisdictions is what faster mobilisation, reduced cascade disruption, and genuine readiness visibility actually require.

The failure to answer doesn't happen inside a system. It happens between systems, at the seams, in the space no one owns. Neither you nor AI can surge what can’t be seen.
Connected organisations can see what they need to in time for the answer to matter. Exposed ones find out what they were missing when the surge is already underway.