GoITSystems by Dr. M. Gottlieb

Why Digital Transformation in Public Administration So Often Fails in Germany—and What's Really Behind It

Paradoxon Digitalization

The Paradox of German Digitalization

Germany is the world's fourth-largest economy, has invested billions in digitalization programs, and enacted the Online Access Act (Onlinezugangsgesetz, OZG) — a clear statutory mandate with a binding deadline of end-2022. Yet the Bitkom DESI Index 2025 ranks Germany only 21st out of 27 EU member states in the digitalization of public administration — behind both France and Italy (). The INSM Government Digitalization Meter 2026, produced by the Institute of the German Economy (IW), puts concrete numbers to the failure: of 7,509 legally mandated individual services, only 823 were available nationwide as of early 2026 — barely eleven percent (). Three years after the OZG deadline, not a single German state can point to an implementation rate above 50 percent.

This failure is not accidental. It has structural causes — and they can be named.

Theoretical Framework: Socio-Technical System Failure

The findings below can be read through a common analytical lens: public sector digitalization in Germany fails due to a socio-technical mismatch — a systematic decoupling of technology deployment, process maturity, governance structure, and organizational change (). This mismatch manifests in six causal clusters that are not merely additive but causally interdependent: inadequate process foundations, federal fragmentation, systemic media discontinuities, governance gaps, procurement law constraints, and insufficient change management.

Cause 1: Technology Focus Without Process Foundation

The first instinct in any digitalization initiative is almost always the same: "Which software should we buy?" The question of process — what is actually being digitalized — comes too late, or not at all. Fraunhofer FOKUS, in its 2025 EfA evaluation study, identifies inadequate coordination and transfer mechanisms as the core structural barrier: processes were not defined clearly enough to be digitalized across administrative levels ().

Bogumil and Gräfe (2024) demonstrate, using the OZG as a case study, that most digitalization projects remained limited to "translating existing analog workflows into an internet-compatible process" — rather than fundamentally redesigning them (). The result: a poorly defined, inefficient process gets digitalized. What you end up with is a digitally rendered but still inefficient system — one that costs more to maintain than the paper original.

Cause 2: Federal Fragmentation Without Coordination

Germany has approximately 11,000 municipalities, 16 federal states, and numerous districts and special-purpose agencies. Each level maintains its own IT infrastructure, procurement procedures, and specialized administrative systems. The EfA principle (Einer für Alle — "One for All") was designed to address this through a division of labor: one state digitalizes a service; all others adopt it ().

In practice, reuse has fallen far short of that promise. Bogumil and Gräfe find that no mandatory reuse obligation exists — with the result that OZG developments compete with municipal standalone solutions, and states cling to their own portals out of institutional self-interest (). The Fraunhofer FOKUS study adds a procurement dimension: municipalities face substantial hurdles in adopting EfA services — ranging from financial uncertainty and interface incompatibilities to complex procurement law requirements (). As early as 2023, the Federal Court of Audit criticized redundant parallel developments, noting that the Federal Ministry of the Interior had been unable to provide central IT solutions on time ().

Cause 3: The Media Discontinuity Problem

Many so-called "digital" public services are digital only at the point of entry. A citizen submits an online form — which then gets printed out and processed by hand, or sent as a PDF email that someone manually rekeys. Bogumil and Gräfe document this mechanism: many OZG services lack electronic interfaces to specialist back-end systems and e-file platforms. "The result is media discontinuity — for instance, when application data submitted as a PDF must be retyped manually" ().

The Federal Court of Audit frames this structurally: many OZG projects do not constitute a finished product from the implementing agency's perspective, because the OZG neglects internal administrative digitalization (). States typically funded the introduction of e-file systems or digital application forms — but not the integration of specialist back-end systems via interfaces.

Cause 4: Missing Process Owners and Governance Gaps

Digitalization projects in public administration are typically treated as IT projects: the IT department is responsible, executes, and signs off. The substantive owners of the processes — the specialist departments — are rarely integrated in any structural way. Bogumil and Gräfe describe how OZG projects are conducted in digitalization labs that are interdisciplinary by design, yet in reusing municipalities run up against specialist offices that hold the operational expertise but have no structural role in the project design ().

The National Regulatory Control Council (NKR) identifies a further root cause in the absence of strategic clarity: "Federal, state, and municipal governments are getting tangled in a thicket of technical silos and jurisdictional disputes" (). The Federal Court of Audit adds, in its review of the federal government's central IT: silo thinking and the unanimity principle within the IT Planning Council have blocked timely and well-grounded decision-making ().

Cause 5: Procurement Law and Innovation Hostility

German public procurement law was not written for agile digitalization projects. It optimizes for cost transparency and equal treatment of bidders — not for outcome quality or adaptability. Tenders are based on requirements documents that are already outdated by the time contracts are awarded; vendors optimize for the tender specification, not for the actual result.

The innovation partnership procedure under Section 119 of the Act against Restraints of Competition (GWB) allows development and procurement to be conducted within a single process — without separate award procedures (). Yet uptake remains marginal: across the EU, only 218 innovation partnerships were awarded between 2016 and 2024; in 2024 alone, that number dropped to 12 — the lowest since the instrument was introduced (). The KOINNO Guide to Innovation Partnerships 2025 explicitly recommends the instrument for public IT projects requiring high innovation capacity and flexibility, but flags complex requirements as a barrier to adoption ().

Cause 6: Inadequate Change Management

Digitalization is not an IT project. It is a change project. Civil servants who have carried out a process the same way for years will not change their behavior simply because new software has been deployed. Bogumil and Gräfe document that change management is systematically neglected in OZG projects: "Actively shaping the organizational change that digitalization brings is therefore essential in order to build acceptance and trust among managers, staff, and the public" ().

In small and medium-sized municipalities in particular, the human and financial resources — as well as the expertise — needed to manage digitalization properly are frequently absent. Instead, digitalization is often handled "on the side" by front-line staff and managers alongside their regular duties. Specialist offices describe feeling like they are at "the end of the food chain" when they are notified late — or not at all — about changes to the systems they depend on ().

What Actually Works: Three Interventions With Demonstrated Impact

1. Process first — with FIM as the standard:
Before any IT project begins, the target process must be modeled in BPMN (Business Process Model and Notation) and validated jointly by the specialist department and IT. Since 2017, the Federal Information Management framework (Föderales Informationsmanagement, FIM), operated by the IT Planning Council, has provided three standardized building blocks for exactly this purpose: service descriptions, data schemas, and reference processes (). FIM is legally mandated under Section 3(2a) of the E-Government Act (EGovG) and offers quality-assured reference models that spare states and municipalities the effort of building from scratch ().

2. Mandatory reuse instead of voluntary EfA:
As early as 2024, the NKR called for a coherent platform strategy and a capable digitalization agency to succeed FITKO — replacing voluntary reuse with structural obligation (). A working counterexample already exists: in tax administration, the KONSENS program makes reuse of jointly developed solutions mandatory — with demonstrably positive results ().

3. Pilots instead of master plans:
Small, self-contained digitalization pilots with measurable results within six months consistently outperform long-running megaprojects. They fail cheaper, generate insights faster, and build organizational capability. In this spirit, the Fraunhofer FOKUS study recommends prioritizing the optimization of existing functionality over feature expansion, and systematically capturing both success factors and obstacles along the way ().

Conclusion: Failure Is Not Inevitable

The causes of failure are well established, documented consistently across multiple independent sources — the Federal Court of Audit, the National Regulatory Control Council, Fraunhofer FOKUS, and academic research. The solutions exist: process standards (FIM), procurement innovation (innovation partnerships), mandatory governance (the KONSENS model), and rigorous change management. What is missing is not insight but execution — and the willingness to start not with the technology, but with the process.

Related Articles

References

Publications

Social Networks

Newsletter - Anmeldung