The Infrastructure We Didn’t Decide : Digital Sovereignty, or: The Quiet Assumption Beneath Our Platforms - Governance and Digital Sovereignty 2
A curious story slipped out of Europe recently.
France has begun moving civil servants away from tools such as Microsoft Teams and Zoom toward a domestically controlled collaboration platform. Denmark, meanwhile, is experimenting with replacing parts of its Microsoft stack with Linux and open-source alternatives.
If you read the headlines you might assume this is about software.
It isn’t.
It’s about governance.
Or, more precisely, about something that sits beneath governance: the assumptions that quietly shape our decisions long before anyone notices them.
The quiet layer beneath digital transformation
Over the last decade public organisations have been encouraged to treat digital infrastructure like electricity. Something you simply plug into.
Platforms such as Microsoft Azure or Amazon Web Services promise exactly that. Scale, resilience and someone else worrying about the machinery.
From a delivery perspective the proposition is irresistible. Particularly in the public sector where ageing systems and shrinking technical capacity sit in permanent tension.
But something subtle happens when this model spreads across an organisation.
A tool becomes a platform.
The platform becomes an ecosystem.
And before long the organisation is not simply using technology.
It is operating inside a technological environment designed by someone else.
Nothing breaks. In fact things usually work better.
Yet a new question quietly appears.
Who actually controls the rules of the system?
The fiction of control
In another piece I wrote recently, The Fiction of Control, I suggested that organisations often confuse visibility with control.
If we can see the decisions we assume we control the system.
But structural change rarely arrives through a single visible decision. It accumulates slowly across dozens of sensible ones.
Digital infrastructure follows exactly the same pattern.
A team adopts a platform because it solves an immediate operational problem. Procurement signs off. Users like it. Integration spreads. Data structures align themselves with the platform’s logic.
Years later the organisation discovers something important.
Leaving the platform would be extraordinarily difficult.
No project ever proposed “platform dependence” as a strategic objective. Yet the dependency now governs what the organisation can realistically do next.
Which makes digital sovereignty less of a technology debate and more of a governance visibility problem.
The machine reorganises the worker
Part of the difficulty is that modern infrastructure hides its structure.
Earlier generations of IT made control obvious. Servers lived in buildings. Ownership was physical. Responsibility was visible.
Cloud systems dissolve those boundaries.
An organisation might believe it runs a local service while the application actually sits inside Microsoft Azure, authentication flows through Microsoft Entra ID, and reporting emerges through Power BI.
Each layer improves capability.
Each layer also deepens reliance on the vendor ecosystem.
Which reminds me slightly of Modern Times. Chaplin spends the film tightening bolts on a vast industrial machine he doesn’t understand. The system runs beautifully. Productivity rises. The factory becomes more efficient.
But slowly the worker realises something unsettling.
He isn’t controlling the machine.
The machine is organising him.
Modern digital platforms do something similar. They structure workflows, communication and decision-making so effectively that organisations begin adapting themselves to the architecture almost without noticing.
The paradox of good platforms
Here is the awkward truth.
The platforms creating the strongest dependencies are usually the best ones.
Microsoft’s ecosystem works because identity, collaboration, messaging, analytics and document management interlock so well. Once an organisation moves into that environment the productivity gains are real.
Leaving becomes correspondingly difficult.
France and Denmark have started asking strategic questions about long-term autonomy. The UK, by contrast, has largely embraced hyperscale platforms as the fastest route to modernising public services.
Both approaches are rational.
But they reveal two different governance instincts.
One asks how to reduce dependence.
The other assumes dependence can be managed.
Governance with a heartbeat
In the Governance with a Heartbeat series I argued that governance should not simply record decisions. It should help organisations see the structural patterns forming beneath those decisions.
Digital sovereignty is a perfect example.
No single project board will ever propose a motion titled “Let us quietly restructure the organisation around a single vendor ecosystem”.
Yet that is often the cumulative effect of perfectly reasonable choices.
Which raises a governance question worth asking more often.
What assumptions are shaping our decisions that we have never explicitly written down?
The assumption beneath the platform
Most organisations now operate under a quiet belief that the infrastructure shaping their decisions will always remain available, affordable and politically neutral.
Usually that assumption holds.
But good governance has never been about assuming the world will remain stable. It has been about making the assumptions visible before they become structural.
Because once an assumption becomes structural it begins to shape every future decision.
And by then the technology choice has quietly become something much larger.
Not an IT decision.
A governance constraint.
A final thought
When we talk about digital sovereignty we often imagine a battle between nations or platforms.
But the more interesting story may be happening inside organisations.
It’s the slow realisation that the most powerful forces shaping our decisions are often the ones nobody ever formally decided.
Which leaves an uncomfortable but useful question hanging in the air.
If our infrastructure is quietly shaping our choices…
how confident are we that we’re still the ones designing the system?
Comments
Post a Comment