Public institutions often describe transformation as a technology program because technology is visible in the budget, the procurement, and the delivery plan. The public experiences something else: whether an application is understandable, whether a case moves, whether a benefit arrives, whether a record can be corrected, and whether a person can reach accountable help when the system is wrong.
That is a product experience. The product is not a website or a platform in isolation. It is the public service as a whole: policy translated into eligibility, eligibility translated into workflow, workflow carried by people, and technology providing the evidence and control that keep the promise credible.
The UN’s 2026 Sustainable Development Goals report makes the public-sector context unavoidable: progress is meaningful but uneven, the 2030 window is narrowing, and investment, international cooperation, technology, and data access must move faster. The implication for public services is practical: governments need impact measurement, skills, infrastructure, procurement, and partnerships—not just a successful pilot.
Product thinking is a mission discipline
Product management is sometimes dismissed as a private-sector metaphor. In public service, its most valuable discipline is not growth. It is sustained attention to the user, the promise, the evidence, and the next release.
A mission product should make four things explicit:
- Promise: what outcome should a resident, beneficiary, regulated party, or caseworker be able to rely on?
- Journey: what decisions, documents, systems, and human interactions produce that outcome?
- Evidence: how will the agency know the service is accessible, timely, accurate, and safe?
- Authority: who can change the service when policy, technology, or public need changes?
These questions expose why modernization cannot be managed as an inventory cleanup. The UK Service Standard makes the product discipline concrete: understand the wider user journey, test with real users, make the service simple, and define success with performance data. Disposition decisions are therefore product decisions: what should be retired, what should be redesigned, and what continuity must be protected while the service changes.
The service is the unit of accountability
An agency can have excellent data governance and still deliver a confusing service. It can have a modern cloud platform and still make a caseworker copy information between systems. It can deploy an AI assistant and still lack a clear way for the public to challenge an outcome.
The management move is to put the service at the center and align the functions around it. Policy owners define the intent. Program leaders define the promise. Technology leaders define the platform path. Security, privacy, legal, records, procurement, and workforce leaders define the conditions for trust. A product owner keeps the service coherent and accountable over time.
A practical diagnostic
Pick one public-facing service and follow a single case from the first question to the final outcome. Record where the person waits, repeats information, changes channels, or loses visibility. Then map the internal decision rights and evidence behind each step. The distance between public experience and internal accountability is the transformation backlog.
Use a small set of service measures: time to a clear answer, first-time-right completion, unresolved exception age, accessibility barriers, worker rework, and the percentage of policy or technology changes that can be traced to a service outcome. These measures turn transformation into management rather than a program that disappears after launch.
What would change our mind?
Not every public service needs a permanent product team or a release cadence that resembles a consumer application. The appropriate model depends on volatility, volume, risk, and the importance of continuity. The OECD evidence suggests that the real test is whether the service can move from use case to operated capability while preserving accountability. Product thinking is useful precisely because it helps leaders choose the lightest management system that can keep the promise visible and improve it responsibly.
Public trust is built at the point where the mission meets the experience. That is where government transformation should begin, and where it should remain accountable.