Beneath the surface: Six structural fault lines holding back government digital transformation

May 1, 2026
Woman with long hair using a laptop at a conference table.

To achieve effective service delivery, governments must focus on 'transformation' as much as on ‘digital’.

Photo: UNDP/Sumaya Agha

The incoherence between digital potential and actual results is striking. Governments worldwide spend over US$800 billion on technology. Software anticipates what we need, learns from how we behave, improves itself almost continuously and builds new software—perpetuating itself. Yet, some 70 percent of digital transformation projects in the public sector don’t reach their goals. Why?

In pursuit of public sector digital transformation, it seems that focus tends to be more on ‘digital’ than transformation. While there is no single recipe, many governments find it difficult to resist the alure of quick fixes, better technology and AI magic at the expense of rethinking policy and service delivery and results people care for. As Tiago C. Peixoto cautions “many digital reforms haven’t stumbled because of poor technology, but because they’ve had to operate within outdated institutional models.”

Our work points to a similar conclusion. Across dozens of engagements with partner governments, we see digital transformation efforts running into similar underlying obstacles. The problem is rarely the technology itself but structural conditions in which digital transformation exists—how public sector governs technology quietly undermines well intentioned efforts.

In this piece, we identify six of the most consequential of these inherent structures. We think of them as fault lines, borrowing from geology, where invisible fractures beneath the surface generate earthquakes. In our context, these are structural, institutional and cultural dynamics that slow down or impede the transformation that digital is meant to enable.

Man in a blue jacket on a grassy hill, holding a phone, overlooking a cluster of colorful houses.

Partnering with governments, UNDP works to identify and address structural fractures that hinder 'transformation’ in digital.

Photo: UNDP Denmark/Zoe Cox

Six fault lines

Across UNDP’s engagement with partner governments, six structural fractures that hinder ‘transformation’ in digital and that emerge with striking consistency—cutting across different political systems, income levels and geographies. Some are not specific to “digital,” others clearly stem from lack of understanding how digital ways of working are structurally different from analogue. These fault lines hinder ‘transformation’ in digital and lead to the ‘pacing problem’—a widening gap between the rapid evolution of technology & governments’ ability to understand, adopt, regulate and ultimately translate it into public good and results citizens care for. 

Fault line 1: The (lack of) policy intent 

The digital transformation projects in the public sector are often divorced from the overarching reform intent of the government and are not seen as a critical “differentiator” to allow government to achieve its strategic objectives on people-centred service delivery, financial inclusion or economic competitiveness. And so the logic of these initiatives becomes inverted and self-serving: at best they achieve some efficiency gains for the civil servants, at worst they keep on adding digital and AI layers on the existing stacks or requirements.

This is surprising, given that many truly transformative digital initiatives, from GDS in UK to India Stack, served a clear public purpose from revolutionizing service delivery for the people to driving financial inclusion and reduction of public funds leakages. In those transformative journeys digitizing or setting data exchanges have never been goals on their own, and yet, too frequently existing digital projects focus on optimizing their digital aspects without asking fundamental questions “why?” and “for whom”? Strategically it is a missed opportunity of leveraging digital to deliver impact, tactically it's a failure to build reform coalitions across the government and authentically engage key constituencies those projects should serve. This fundamental fault line sets many digital projects for isolation and redundancy, if not harm altogether.
 

Fault line 2: The funding architecture

In many government contexts, digital is budgeted the way you would budget a bridge. A large capital allocation funds "construction." When the system is delivered, remaining resources shift to a much smaller operations and maintenance line—and attention moves elsewhere. The trouble is that software is not a bridge. A bridge, once built, does not need to be adapted every time the river changes course. Software on the hand exists in a changing environment of user needs, security threats, policy shifts and evolving integrations. It is never really "delivered" in the way a physical asset is. Rather, it is made operational and from that point forward it requires some attention by a team to remain functional, let alone to improve. As Jennifer Pahlka has documented extensively in Recoding America, this structural mismatch between how governments budget and how software behaves is one of the most consequential and least discussed problems in government technology.

The cost of this cycle, measured in both public expenditure and in the quality of services that citizens ultimately receive, is significant. In many of the contexts UNDP works in, this pattern recurs across ministries and across administrations, with each cycle consuming resources that could have sustained a functioning product. The underlying challenge is not primarily technical; it sits in public financial management frameworks, as well as the tendency to “buy more and build more”, that predate modern software practice. What is needed is a shift toward ongoing, product-style funding streams for digital services, treating them not as construction projects with an end date, but as public institutions that require continuous investment and care to remain effective.

Smiling man peeks from a rustic log cabin under construction.

UNDP aims to close the gap between the rapid evolution of technology and governments’ ability to translate it into results for their citizens.

Photo: UNDP Haiti/Pierre Michel Jean

Fault line 3: Overlapping mandates

A citizen seeking a social benefit does not experience government as a set of different ministries, departments and agencies. They experience a journey of applying, verifying, waiting, appealing, receiving that cuts across multiple institutional boundaries. But accountability structures in government are typically organized around ministerial mandates rather than user needs or journeys. A municipal case worker may determine a person’s eligibility for social services as directed by rules from the Social Protection Agency. The identity verification of the person sits with a National Identification Authority under the Ministry of Home Affairs. The process of payment is authorized and completed somewhere else entirely. Where no single actor owns the end-to-end experience, it becomes difficult for any single actor to identify and address the points where that experience breaks down, and thus to design good digital services. 

Where mandates overlap, coordination tends to be effortful rather than automatic. Each ministry operates within its own planning cycle, its own political context and its own set of institutional priorities. These structures were not designed to be obstructive, they reflect a long-established logic of accountability by function. But they create real challenges for the delivery of services that cross those functions. The response is rarely a reorganization of government, which is seldom politically or financially viable, but the creation of cross-cutting mechanisms: shared outcome metrics, joint budget lines for cross-ministry services, Policy and Service Labs, mission-driven institutions, and service owners whose remit genuinely spans institutional boundaries. This is less a technical challenge than a governance design challenge, and it rarely resolves without deliberate convening across lines that do not naturally connect. 

Fault line 4: Data as territory 

Ask a citizen to apply for a social benefit in most countries and they will likely be asked to prove their identity, their address, their income and their family situation, information the government may already hold, scattered across ministries operating under different mandates. Each ministry collects data for its own purposes, stores it in its own systems, and manages it under its own rules. There are genuine boundaries for what can be shared with whom, and access to data raise real questions of accountability and privacy. But there is also a subtler dynamic at play as data confers relevance within the state, and the institutional incentive to protect it may sometimes outweigh the incentive to share it. Why bother with the work and risk to share data in your systems to another part of government if no one can force you to it? The result is that integrated services often fail at the most fundamental point: the exchange of information between institutions. 

The interoperability tools exist. What is often missing is the governance settlement underneath: an agreement, backed by law and supported by institutional design, about what data can shared, to whom and under what conditions, and a shared understanding that data held by the state is ultimately held in trust for citizens, not as the property of the agency that collected it. Countries that have made meaningful progress here, Estonia with X-Road, Singapore with its data empowerment frameworks, did so not primarily through technical innovation but through a deliberate political decision to treat data as shared public infrastructure. Without that settlement, interoperability remains aspirational, and the gap is most visible to citizens who find themselves re-submitting the same information to different parts of the same government. 

Governments do not lack digital ambition—they lack the institutional conditions for that ambition to take root.

Fault line 5: The talent pipeline 

Governments consistently struggle to attract and retain the people needed to build and run good digital services. Software engineers, product managers, service designers, ethnographers, UX researchers, data scientists, the skills at the heart of modern digital delivery are in high demand in the private sector and command salaries, career trajectories and working cultures that most civil services cannot match. This means roles remain vacant for extended periods and bringing in external consultants who leave with the institutional memory and know-how accumulated in government digital programmes. When a digital agency is established but subjected to the same pay bands, hiring rules, and procurement constraints the structural mismatch simply moves address.

This fault line persistent because of deep institutional instincts in government: The drive toward uniform frameworks, consistent rules, and equal treatment across agencies and departments. This instinct ensures accountability, fairness, the appropriate use of public resources. But when applied to digital transformation it produces a category error. In response, a growing number of countries are reforming the civil service and establishing new public utility type institutions giving more flexibility for those entities to define career pathways, pay scales, working arrangements and internal structures to attract talent and organize for using digital to solve public problems. Semi-public government agencies tasked with digital transformation (e.g. Singapore’s Open Government Products, Rwanda’s Irembo, Cambodia’s Techo Startup Centre, and emerging equivalents in Ethiopia and Sri Lanka) are all an acknowledgement of this fault line.  

Fault line 6: ICT procurement and specifying to “reduce risk” 

Broadly speaking, government procurement of digital lends a lot of influence from how services and infrastructure is bought: Define what is wanted, identifying a supplier, and manage risk through the specification, monitoring and testing. That instinct is understandable, but software does not behave like other services and infrastructure government may buy, whether it be food delivery for the elderly or building a road. While detailed specifications in theory sounds good in effect it locks everyone into a design that may already be wrong by the time it is built. Requirements written eighteen months before launch cannot anticipate what will be learned in the first weeks or months of speaking to users and building. Vendors are then contractually obligated to deliver what was asked rather than what is actually needed, and variation becomes expensive, contested and slow.

Woman with ponytail checking a QR code with her phone, at an outdoor market near crates of apples.

To advance people-centred service delivery, digital transformation projects in the public sector must be designed and implemented with the overarching reform intent in mind.

Photo: UNDP Cambodia/Zoe Cox

What keeps this fault line in place is a deeper disconnect: a procurement official and a business analyst or software engineer looking at the same tender process are looking at fundamentally different things. One sees a contractual instrument to manage risk while the other sees a constraint that will shape everything that follows. There is growing awareness of this as agile methods have entered the vocabulary of government technology, and a number of procurement frameworks have begun to create more room for iterative delivery. Yet there is more to be done, and the track record of large government IT programmes suggests the structural adjustment is still incomplete. Closing that gap through rule changes, more cultural awareness, and the kind of cross-functional engagement that lets both perspectives reshape how digital is procured is where reform need to start. 

Why do fault lines matter?

These challenges share characteristics that distinguish them from ordinary governance problems and that explain why they persist despite being widely recognized. 

  • They have an 80/20 quality meaning addressing any one of them unblocks progress on many other things simultaneously. Fixing the funding architecture enables capable teams can stay together; address the data governance challenge and integrated services become achievable; reform procurement and more capable suppliers can contribute. These are leverage points in a system, not isolated deficiencies. 
  • They are, in the language of complexity, wicked problems, not in the sense that they are malicious, but in the sense that they have no single right answer, that attempted solutions change the nature of the problem, and that they require the involvement of multiple actors who see the problem differently.  
  • They are easy to defer. None of them will necessarily break any individual project. But each puts an invisible tax on every project in the portfolio. Partner governments can build functional digital services despite a broken funding model, despite siloed data, despite fragmented mandates but not efficiently, sustainably, or at scale.  
  • They are not primarily technology problems. Digital transformation that focuses on technology while leaving these structures intact will reliably produce more of the same.

Governments do not lack digital ambition—they lack the institutional conditions for that ambition to take root. For us engaging seriously with fault lines means complementing downstream delivery support, which remains essential given the acute capacity needs many governments face, with more upstream, systems-oriented engagement. Working alongside governments on the funding models, governance arrangements, talent pipelines, and procurement rules that will help to determine all digital investments are sustained and make a positive impact.  

For us at UNDP’s Digital, AI and Innovation Hub, fault lines increasingly frame how we engage with governments and cities around the world. In our next article, we will share some of those stories.