Public Sector · December 2025 · 9 min read
What a digital public infrastructure programme owes its citizens
The technical architecture of digital public infrastructure — identity, payments, consented data exchange — is now well-rehearsed. The harder questions, and the ones that determine whether a programme earns public trust, are not technical at all.
The argument
A DPI programme owes its citizens four things the architecture diagrams rarely cover: the right to know what was looked up about them and by whom, a path to correction that does not require a lawyer, a continuity commitment if the operator changes, and a credible explanation of why a private actor was allowed inside the rails. Programmes that answer these well outlast the political cycle that built them.
What we see in the field
In the programmes we have supported, the moment of trust has consistently been earned not at launch but at the first public failure — the missing payment, the disputed identity record, the data request from an agency the citizen did not know existed. The programmes that handled those moments transparently kept their mandate. The ones that didn't, didn't.
What it changes
For ministries, the implication is that the accountability layer of DPI is the product, not a wrapper around the product. For multilaterals, it is that funding the rails without funding the redress is the most reliable way to produce a politically fragile programme.
Where to start
For any DPI programme currently in design or roll-out, write down the public answer to the four questions above before the next funding tranche is approved. If any answer is missing, the programme is not yet ready to scale.
