A sample from Digital Sovereignty: The Power to Decide

The viral outbreak hit the capital on Tuesday. By Friday, three hospitals had activated surge protocols. Weeks ago, the Health Ministry's Chief Data Officer (CDO) had been flagging anomalies in the northern provinces to system leaders. The response: "Noted, with thanks. We'll review it at the next quarterly meeting." That meeting is still held in attendees’ diaries, in two weeks time. Too late.

The data to track an outbreak was out there. But it sat in separate systems that no one had built to communicate: health records in one, pharmacy logs in another, hospital admissions in a third. Some years earlier, ministers had approved a cross-ministry protocol to connect these systems. Money was tight, so implementation got deferred to a ‘Phase Two’. Then ‘Phase Two’ became 'when resources allow.' Resources never arrived.

The CDO had supported that delay. At the time, it seemed reasonable. It didn’t seem like the ‘answer’ to the data sharing problem had really arrived. Fifteen years of underfunding had made delays the default response in any case. But each deferral narrowed the ministry's ability to respond when it counted.

There was no crisis at the small education non-profit. That was the problem. Too few girls were completing primary school, and four years of paper attendance records and community health workers walking between villages in the dry season had taught the organisation what was going wrong without revealing why. The pattern was there, buried in analogue records.

Then a global technology company arrived with a gift. A free mobile platform for tracking attendance, engaging parents, and targeting outreach. Implementation in weeks, not years. For an organisation that had been solving problems on foot, it felt like a lifeline.

The executive director read the terms more carefully than the board had. The platform granted the vendor rights to aggregate data across its entire portfolio of non-profit partners. Then came a bombshell that changed the conversation entirely: the same tech company was suddenly on the front pages, facing scrutiny for how its tools had been used to spread misinformation in three neighbouring countries.

The gift was real, but so were the strings attached. The executive director faces a choice that they can’t afford to get wrong: take the tools and accept dependency, or walk away from the only offer on the table that might address the problem.

The airline's Chief Technology Officer had 90 days to make a decision that would shape every booking, ticket, and crew schedule for the next five years. On the desk: 756 pages of revised terms from a vendor that had controlled these systems for twenty-two years.

Each of those twenty-two annual contract renewals was justifiable at the time. Yet each was also a decision not to build internal capability. The engineers who understood the legacy architecture left the company long ago. The current team knows how to configure the vendor's systems, but not replace them.

The vendor has pressed for new terms. "Enhanced data collaboration" would grant them rights to aggregate passenger behaviour across fourteen client airlines, including three direct competitors. Booking patterns, pricing sensitivity, route preferences, all flowing to the competition.

The board wants competitive advantage. The IT contract offers the opposite. But switching is not simple. The last airline that tried to extricate itself from the supplier spent four years and hundreds of millions before a system failure stranded 140,000 passengers across three continents.

The CTO knows the board will not accept "we had no choice." They were hired to create choices. But ninety days is half the time it takes to mobilise a new team, and twenty-two years of inertia have left no easy options.

Three sectors. Three different pressures. The same problem holding each one in place. Inertia, heightened by fear.

The kind of fear that shows up as prudence: renewing contracts because switching seems risky, maintaining systems because rebuilding is costly, putting off decisions about tomorrow because today's problems feel urgent enough. Inertia often feels sensible; the safe option. But it’s also the risk nobody wanted to calculate.

The government CDO relied on a governance system never tested under pressure. The NGO director operated for years without the data to see the problem clearly. The airline CTO inherited two decades of customisation in a system the airline didn't own.

Inertia is ultimately sustained by people, mistaking what is familiar for what is sensible, or seeing the next month so clearly that the next decade disappears from view. Not because they lack the intelligence to act differently, but because no one has given them the tools or incentives to see what ‘different’ could look like.

Widespread AI adoption is compounding this dynamic. The rush to adopt new tools without understanding existing dependencies accelerates the consequences of every deferred decision. The pace no longer forgives one more quarter of waiting.

We have all been in the meeting where everyone agrees something must change, and nothing does. This is how institutions lose their sovereignty and their future: gradually and without resistance.

The way back starts with knowing exactly what you're trying to restore. Digital sovereignty is the agency and capacity of any organisation to make deliberate, informed choices that build its digital future by design.

Digital sovereignty is earned through a series of intentional calculations: seeing your position before you commit, designing new options where few appear to exist, and building in ways that leave leaders with more room to move, not less.