Skip to content
The Future Explorerby Benjamin Talin
Enablerstructural

Interoperability

Standards & Interoperability

Agreed specifications that let things built by different makers work together: the shape of a plug, the size of a shipping container, the format of a bank transfer. When they work they are invisible; when they are missing, everything needs custom fixes. Banks around the world spent two and a half years switching to one new message format, and now a bank that has not switched cannot send money abroad. Whoever writes a standard decides whose products already fit.

Maturity

3/ 5
measured
BasisMature where the standard already won - payments, networking, containers - and thin at every frontier. Where a dominant vendor gains from the absence, it takes a regulator to produce interoperability: the Commission had to tell Apple which nine iPhone features to open.SourceE-134 (Farrell & Newman, International Security 44(1), 2019); Swift (20 Mar 2023; 25 Nov 2025); Connectivity Standards Alliance (23 Oct 2023; 8 May 2024); European Commission (19 Mar 2025; 28 Dec 2024); National Standardization Development Outline (10 Oct 2021, CSET translation)Vintage2019–2025
ReadinessCapability 4Deployment 3Absorption 3Bound byincentivesTrendflat

Where it feeds in

7 megatrends in 4 forcesweakest link

Where you have already met this

On 22 November 2025 the old message format stopped working. A bank that had not moved to ISO 20022 could no longer send a cross-border payment instruction through Swift. The changeover had been running since 20 March 2023 - two and a half years of coexistence for one file format. A format nobody outside banking can name is now the condition for sending money abroad.

If this moved

If interoperability reached the frontier layers - model interfaces, immersive environments, data portability - immersive and spatial computing would lose one of the two enablers holding it at 3. Headsets hold it at the same level, so the reading would stay where it is. Platform power versus state power sits at 3 with payment rails beside this entry.

What to watch for

Certifications counted by the body that runs the standard, not products announced by vendors. Regulators specifying interoperability in detail rather than in principle - the Commission's two decisions telling Apple which iPhone features to open are the live test.

Not to be confused with

Compatibility. A product can be compatible with one host and still shut everything else out. Interoperability means two independently built systems exchange data in both directions, without either side's permission.

What it is

Agreed specifications that let independently built things work together. Standards are boring, invisible when they work, and decisive when they are missing - and whoever writes them exercises a form of power that rarely appears in a power analysis.

How it works

  1. 01Someone drafts the specificationEngineers from competing firms and institutions write down the interfaces, data structures and security baseline in a working group.
  2. 02Members argue and ballotObjections are filed and resolved under the body's own rules. Whoever's existing design is closest to the draft has the least work to do afterwards, which is why this stage is where the money is.
  3. 03The body publishes a versionThe specification is issued with a version number. Matter 1.3 arrived on 8 May 2024, adding energy reporting, EV charging and appliances.
  4. 04Independent labs certify implementationsProducts are tested against the specification and certified. Certification counts are the honest adoption measure; press releases are not.
  5. 05Products ship, and a second implementation decides itA standard with one implementation is a product. It becomes a standard when someone else's version also works.
  6. 06Where it does not happen, a regulator can force itThe EU mandated one charging port; the Commission told Apple which nine iOS connectivity features to open to other devices. Interoperability at the frontier now mostly arrives this way.

State of play

  • Swift's migration of cross-border payment messaging to ISO 20022 began on 20 March 2023, and the coexistence period with the old MT messages ended on 22 November 2025 (Swift, 20 Mar 2023 and 25 Nov 2025).
  • One year after Matter's launch, the Connectivity Standards Alliance reported 1,214 certifications and more than 24,600 downloads of the specification (Connectivity Standards Alliance, 23 Oct 2023).
  • Matter 1.3 was published on 8 May 2024, adding energy reporting, electric vehicle charging, water management and major appliances (Connectivity Standards Alliance, 8 May 2024).
  • EU common charger rules have applied to phones, tablets, cameras, headphones and consoles since 28 December 2024, and to laptops since 28 April 2026 (European Commission, 28 Dec 2024).
  • The Commission adopted two specification decisions on 19 March 2025 requiring Apple to open nine iOS connectivity features - including notifications and pairing - to third-party smartwatches, headphones and televisions (European Commission, 19 Mar 2025).
  • China's Central Committee and State Council issued the National Standardization Development Outline on 10 October 2021, making standard-setting an explicit instrument of national policy (CSET translation of the Outline, 8 Nov 2021).

Why it matters

It converts a set of products into a system. Without agreed interfaces, every combination is a bespoke integration, cost scales with connections rather than with nodes, and the network effect that makes a megatrend steepen never arrives. Interoperability is the enabler most frequently underestimated in a conjunction problem: it was one of the metaverse's shallowest layers, and it is not a technical difficulty but a coordination one.

  • It is one of the two enablers holding immersive and spatial computing at 3, and one of the two holding platform power versus state power at 3. In both cases the other one is not a technology either.
  • It is the enabler most often assumed rather than checked. The metaverse's missing layer was not graphics; it was that no two environments had a reason to agree.
  • Whoever writes the specification decides whose products are compliant by default. That is why a standards body is a venue for state power and not only for engineers.

What holds it back

Lock-in pays

A dominant vendor earns more from switching costs than from interoperability. Absence is then a strategy, not a delay.

Consensus is slow by construction

Everyone has to move at once. Changing one payment message format took two and a half years of running both.

One implementation is not a standard

Until a second, independent implementation works against the same specification, what exists is a product with documentation.

Standard-setting is contested between states

Standards decide whose products fit by default, so the venues are used accordingly - China's 2021 Outline says so in its own words.

Terms

De jure standard
A specification formally approved by a recognised body such as ISO, IEC or the ITU.
De facto standard
A specification that wins through market adoption rather than approval, and can be withdrawn by its owner.
Conformance certification
Independent testing that a product actually implements the specification it claims.
Chokepoint effect
The power a state gains over a network it hosts, by cutting others off from it (Farrell & Newman, 2019).
Panopticon effect
The power a state gains over a network it hosts, by seeing what passes through it (Farrell & Newman, 2019).
Interoperability
Two independently built systems exchanging data in both directions and working together, without a translation layer in between.

Steepens

The gradient behaves like a sticky rubber band: it is pulled hardest toward the weakest enabler. Marginal links are shown but do not pull.

If this moved one step

Computed from the map as it stands: this score raised from 3 to 4, every other score unchanged. It is arithmetic, not a forecast.

Raised one step on its own, it lifts no megatrend's weakest link; each gradient it feeds still rises a little.

Tied as the weakest link

Here it shares the weakest spot with other enablers. Raising it alone leaves the weakest link where it is and lifts the gradient a little; the enablers it is tied with must move too.

What if it moved?

What would change the gradient

Conditional, not predictive. No dates, no probabilities.

  1. 01A regulator mandating portability where a dominant vendor benefits from its absence
  2. 02Public procurement requiring an open specification, which is the cheapest standards lever a state has
  3. 03A credible second implementation - a standard with one implementation is a product

Common misconception

That standards follow adoption. They frequently gate it - and where a dominant vendor benefits from their absence, the absence is a strategy rather than a delay.

Talin, B. (2026). Standards & Interoperability. The Future Explorer, dataset v0.4.0 (2026-11-16). https://explorer.talin.digital/e/standards/