In January 2025, the UK government published two documents that, taken together, constitute the most candid official account of the state of public digital services in more than a decade. The State of Digital Government Review and the accompanying Blueprint for Modern Digital Government were unsparing in their diagnosis. Public satisfaction with digital public services had fallen from 79 per cent to 68 per cent over the preceding decade. Satisfaction with 70 per cent of the government’s top 75 services sat below private sector benchmarks. Nearly half of central government services and 45 per cent of NHS services still lacked a digital pathway. The average UK adult was spending a week and a half each year dealing with government bureaucracy. Someone managing a long-term health condition or disability was required to interact with more than 40 services across nine different organisations.
The diagnosis is a familiar one to those who have delivered digital programmes across regulated industries and the public sector. The problem is not, in the main, a shortage of digital investment. The UK government spends over £26 billion annually on technology. The problem is structural: investment has accumulated in disconnected initiatives, delivering improvements in isolated services without materially changing the experience of the citizen trying to navigate an entire system. Satisfaction has fallen not because services have gotten worse in isolation, but because expectations have risen faster than joined-up delivery has improved.
This is the context in which “citizen-centric” has moved from a design aspiration to a measurable delivery requirement, and in which the absence of meaningful outcome measurement has become the most consistent predictor of programmes that disappoint.
What Citizen-Centric Actually Means in Practice
The term has been in circulation long enough to become hazardous. Used loosely, it means little more than “we consulted some users before we built it.” Used precisely, it describes a fundamentally different approach to how services are designed, measured, and iterated, one that defines success in terms of citizen outcomes rather than system outputs.
The distinction matters because the two are easily confused. A service can process 10,000 transactions a month with high uptime and low cost per transaction while still failing the citizens who use it: because the transaction required three prior interactions to reach, because the information provided was inaccessible, because the outcome, the benefit, the permit, the appointment, did not arrive in a way that was actually usable. Output measurement captures the first kind of performance. Outcome measurement captures the second.
KPMG’s Citizen Experience Excellence research for 2025–26 identifies the core issue with precision: citizen experience has barely moved despite years of digital investment, not because progress has not been made, but because transformation has been fragmented. When data, workflows, technology, and people are connected end-to-end, when the citizen, rather than the departmental boundary, becomes the organising principle, public services can move from incremental change to integrated, proactive experiences that reflect real citizen journeys. That shift is not a product decision. It is an architecture, data, and governance decision, made, or not made, long before a service is built.
For healthtech organisations, regulated service providers, and public sector delivery teams, the practical question is how to operationalise this at the programme level. Not at the level of an individual product or service, but across the full scope of what a citizen encounters when they need something from an organisation.
The Outcome Measurement Problem
Most digital programmes define metrics at the point of inception and measure what is convenient rather than what is meaningful. Conversion rates, task completion rates, and page load times are all legitimate indicators of service performance, but none of them captures whether the person using the service actually got what they needed, in a way that improved their situation.
The Blueprint’s six-point plan for digital reform commits the UK government to publishing and acting on performance data, and to working “in the open” so that people can help shape changes that affect them. The fifth priority, fund for outcomes, procure for growth and innovation, makes explicit what has long been implicit: that the funding and procurement structures governing most digital programmes have been calibrated to measure activity, not impact. This is the structural origin of the outcome gap.
Correcting it requires three things that are harder than they appear.
Defining outcomes at the system level, not the service level. A citizen applying for a disability benefit is not trying to complete a form. They are trying to secure financial support that enables them to live. The outcome is not a submitted application; it is a supported life. Defining it correctly changes everything downstream: what the service needs to do, how it connects to adjacent services, what data it needs to share, and how its success will be measured. Programmes that define outcomes at the service level optimise the wrong thing and discover this only when satisfaction data fails to improve.
Connecting measurement to the citizen’s journey across organisational boundaries. The State of Digital Government Review notes that someone moving home must contact ten separate organisations. None of those ten organisations, measured individually, may be performing badly. The experience is poor in aggregate. Meaningful outcome measurement requires a longitudinal view of the citizen’s interaction with a system of services, not a cross-sectional snapshot of individual transactions. This is a data infrastructure question as much as a service design question, which is why the Blueprint’s roadmap, published in January 2026, places data infrastructure, GOV.UK One Login, and joined-up platforms at the foundation of the government’s reform agenda rather than as downstream considerations.
Embedding measurement as a discipline, not an audit. In too many programmes, performance data is collected for reporting purposes and reviewed retrospectively. By the time a pattern of underperformance is visible in the data, the design decisions that produced it are often already embedded in production systems that are expensive to change. Outcome measurement that influences delivery requires short feedback loops, product-led governance, and a team structure in which the people measuring are the same people with the authority to act on what they find.
The Role of Data and Architecture
Citizen-centric service design without the underlying data infrastructure to support it is an aspiration, not a programme. The single most common reason that digital services fail to deliver measurable citizen outcomes is not poor user research or inadequate product management. It is fragmented data: services that cannot share information with each other, identity systems that require citizens to prove themselves repeatedly to different parts of the same organisation, and measurement frameworks that cannot aggregate across touchpoints because the data that would enable aggregation is held in incompatible systems.
The Blueprint’s commitment to a “once only” principle, that information provided to one government service should be reusable by others, with appropriate safeguards, is a data governance commitment as much as a service design one. It requires a shared understanding of data assets, a reliable identity layer, interoperable APIs, and the governance structures to manage consent and permissioning at scale. None of this is achievable without senior technical leadership that understands both the architecture and the policy context in which it must operate.
For organisations outside central government, funded healthtech startups, NHS trusts, energy companies, financial services firms, the structural challenge is the same, even if the regulatory environment and the scale differ. Citizen-centric service design requires a data foundation that enables a coherent view of the person, not the transaction. Building that foundation, and building it in a way that is compliant, secure, and capable of evolving as service requirements change, is the hardest part of the work. It is also the part most likely to be deferred in favour of visible product features, and the part whose absence most reliably undermines the measurable impact of everything built on top of it.
Designing for Measurement from the Outset
The practical implication of all the above is that outcome measurement cannot be retrofitted onto a programme that was not designed to produce measurable outcomes. It must be built in from the point at which the programme is defined, which means it must be part of the discovery and architecture phase, not the post-launch evaluation phase.
In practice, this means establishing the following before significant build work begins: a clear definition of the citizen outcomes the programme is intended to produce, expressed in terms that are both meaningful to citizens and measurable within realistic data constraints; an instrumentation strategy that captures the data needed to assess those outcomes throughout the citizen journey, across organisational and system boundaries where relevant; a governance model that connects performance data to the people and processes empowered to act on it; and a review cadence that is short enough to inform delivery decisions rather than merely document them.
This is the kind of work that does not show up in a product roadmap or a sprint backlog. It is the pre-work that determines whether the product roadmap and the sprint backlog are pointed in the right direction. In funded scaleups and mid-market organisations with constrained in-house capability, it is frequently the work that gets skipped, not because its value is not understood, but because there is no one in the room with the authority and the technical credibility to make the case for investing in it before delivery begins.
The Commercial and Reputational Dimension
For organisations in regulated industries and healthtech, the stakes of getting citizen-centric delivery wrong extend beyond satisfaction data. The State of Digital Government Review identified 22 per cent of government systems as “red-rated,” with 123 critical outages in NHS England alone during 2024, incidents that had real consequences for patients. The relationship between service design, data architecture, and citizen outcomes is not abstract in healthcare and regulated services. It is clinical, legal, and reputational.
Organisations that build citizen-centric services with measurable outcomes are not simply delivering better user experiences. They are building the evidence base that justifies continued investment, demonstrates compliance with outcome-based regulatory frameworks, and differentiates their offering in markets where commissioners and buyers are increasingly sophisticated about the difference between activity and impact. That evidence base is built on data infrastructure, measurement discipline, and the kind of senior technical leadership that can hold both the architectural and the strategic dimensions of a programme simultaneously.
At Flipware Technologies, we work with regulated-sector organisations, public sector bodies, and funded healthtech platforms to design and deliver digital programmes that produce outcomes citizens can feel, and that organisations can measure. If you are building or redesigning a citizen-facing service and want senior-level input at the discovery and architecture stage, we would welcome the conversation.
References
- GOV.UK / DSIT, A Blueprint for Modern Digital Government (January 2025): https://www.gov.uk/government/publications/a-blueprint-for-modern-digital-government/a-blueprint-for-modern-digital-government-html
- Government Transformation Magazine, Government’s digital deficit revealed (January 2025): https://www.government-transformation.com/transformation/governments-digital-deficit-revealed-new-report-calls-for-urgent-transformation
- KPMG UK, The shift: from digital delivery to system alignment, Citizen Experience Excellence 2025–26: https://kpmg.com/uk/en/insights/government-public-services/the-shift-from-digital-delivery-to-system-alignment.html
- Government Digital Service Blog, Our roadmap for modern digital government (January 2026): https://gds.blog.gov.uk/2026/01/20/our-roadmap-for-modern-digital-government/
- Global Government Forum, New UK digital services plan aims to ‘transform the relationship between citizen and state’ (January 2025): https://www.globalgovernmentforum.com/new-uk-digital-services-plan-aims-to-transform-the-relationship-between-citizen-and-state/
Flipware Technologies is a UK-based digital transformation and data consultancy with offices in Glasgow and London. From FTSE 100 data programmes to funded startup platforms, we bring senior-level technology and data leadership to organisations that need outcomes, not just delivery.
