Executive Summary

An opinion piece by Martin Andenmatten in Netzwoche criticizes the confused debate on digital sovereignty in the IT industry. Although politicians, providers, and enterprises use the term omnipresently, there is a lack of clear definition and orientation. The author argues that the central problem is not the technology itself, but the missing leadership decision: enterprises must consciously define which dependencies are acceptable, rather than pursuing mythical "sovereignty."

People

  • Martin Andenmatten (Author, Netzwoche Columnist)

Topics

  • Digital Sovereignty
  • IT Governance
  • Vendor Lock-in
  • CIO Responsibility
  • Data Control

Clarus Lead

The current debate reveals a paradoxical pattern: the more intensively digital sovereignty is discussed, the less concrete guidance emerges. The core problem lies not with cloud providers or regulatory requirements, but with missing internal governance. CIOs must understand themselves as architects of digital agency, not as technology operators – and thus take responsibility for strategic dependency management rather than waiting for perfect technical solutions.

Detailed Summary

The article identifies a central contradiction: while enterprises invest millions in cloud platforms, AI solutions, and digital ecosystems, they often fail to understand what new dependencies they are creating. The discourse fragments into disparate concepts – data sovereignty, cloud sovereignty, AI sovereignty, European and regulatory sovereignty – without core understanding.

An uncomfortable reality is overlooked: no sovereign technology exists. There are only sovereign decisions. Enterprises complain about vendor lock-in without ever defining which dependencies would be critical. They demand data control but can rarely articulate which data they actually own or what is business-critical. This treatment of digital sovereignty as a binary switch ignores operational reality.

The author makes clear: complete independence is illusory. The relevant question is not whether dependencies exist, but whether they are understood, evaluated, and consciously accepted. This is precisely where legitimate governance separates itself from wishful thinking. Digital sovereignty emerges through active management of dependencies, not through their elimination.

The solution does not lie in state regulation or perfect cloud products, but in CIO leadership. This requires: clear risk visibility, predetermined decisions, and established governance where today only uncertainty prevails. Whoever assumes responsibility, sets priorities, and decides consciously gains genuine digital agency – not technological independence.

Key Statements

  • The term "digital sovereignty" is fragmented and meaningless without clear internal definition of acceptable dependencies
  • Enterprises invest massively in technologies without understanding what new dependencies and risks they create
  • True sovereignty is not technological but a leadership task: conscious acceptance and active management of dependencies
  • CIOs must transform their role from technology operators to architects of digital agency
  • Whoever waits for perfect technical solutions will be overtaken by reality

Critical Questions

  1. Evidence Gap: The article criticizes lack of clarity on dependencies but provides no empirical data on the scope or costs of these governance deficits. How quantifiably measurable is the diagnosed problem?

  2. Conflicts of Interest: Andenmatten advocates CIO-led governance – a position that strengthens the role and budget of IT leadership. To what extent does this interest position shape the argumentative structure?

  3. Causality Trap: The text claims that missing decisions lead to inability to act. Alternative thesis: perhaps rational uncertainty exists because technology markets are too volatile for long-term commitments. Was this counter-hypothesis considered?

  4. Feasibility: The demand for CIO-led dependency management presupposes organizational rationality. How realistic is this in enterprises where business pressure and IT planning conflict?

  5. Regulatory Context: The article rejects state solutions. Yet EU mandates (e.g., data sovereignty, cloud regulation) force decisions that are not purely voluntary. To what extent does governance autonomy actually exist?

  6. Measurability of Sovereignty: The author argues against binary treatment. But how can "acceptable dependency" be concretely measured and communicated? Is an operational framework missing here?

Bibliography

Primary Source: Andenmatten, Martin (2026). "Digital Sovereignty Requires Leadership." Netzwoche, 10.06.2026. https://www.netzwoche.ch/news/2026-06-10/digitale-souveraenitaet-braucht-fuehrung

Verification Status: ✓ 10.06.2026

This text was created with the support of an AI model. Editorial Responsibility: clarus.news | Fact-Check: 10.06.2026