What the Government Digital Service Got Right (And What Most Organisations Still Miss)

When GDS launched GOV.UK in 2012, it did something that felt almost radical for a government body: it put users first and made that commitment visible, measurable, and non-negotiable. The Service Standard, the Design Principles, the open blog posts detailing what worked and what did not: these were not just process documents. They were a cultural statement about how public services should be designed, and they had a genuine influence on how service design is practised across both public and private sectors. More than a decade later, it is worth being honest about what GDS actually got right, and equally honest about what most organisations are still getting wrong despite having access to all of that published thinking.

The Service Standard and Why It Matters

The UK Government Service Standard is a set of criteria that digital services in central government must meet to receive funding and go live. It covers everything from understanding user needs and iterating based on evidence to operating a reliable, secure service and making it accessible. What makes it powerful is not the individual criteria but the system it creates: a mandatory assessment process at each phase of delivery, conducted by independent assessors, that teams cannot bypass by promising to do the work later.

This is structurally different from most organisations' approach to quality, where standards are aspirational rather than gatekeeping. In most corporate environments, a team can ship a product that has not been tested with real users, is not accessible, and has no clear success metrics, without any formal consequence. The Service Standard, at its best, makes that impossible. The assessment model forces teams to be honest about what they know and what they do not know before they move to the next phase.

From Project Thinking to Service Thinking

Services are not projects. They do not end at launch. GDS understood this before almost anyone else in the public sector.

One of GDS's most enduring contributions is the shift it drove from project-based thinking to service-based thinking. Government had traditionally commissioned digital work as a series of discrete projects: build this system, deliver that form, launch this website. Each project had a start date, an end date, and a handover to an operational team. The idea that a service is a continuous thing that needs to be iterated, measured, and improved after launch was genuinely novel in that context.

GDS baked this into its operating model. Teams were expected to show evidence of ongoing iteration, user feedback loops, and operational monitoring as part of their assessment against the Service Standard. This forced organisations to think about sustainable team structures and funding models rather than treating digital as a one-time capital investment. Many organisations, public and private, still have not made this shift. They launch and move on, leaving services to degrade over time without dedicated resource to maintain and improve them.

The Bold Move of Publishing Everything in the Open

GDS published its work openly and extensively, from weeknotes written by delivery teams to detailed retrospectives on projects that did not go well. This was unusual for a government body, and it created something valuable: a shared body of knowledge about how to design and deliver digital public services that any practitioner in any organisation could access and learn from. The GOV.UK Design System, published as an open standard, is now used by local authorities, NHS trusts, arms-length bodies, and even private sector organisations building services that need to feel familiar to users.

The lesson here for private sector organisations is not to copy GOV.UK's visual design but to adopt its habit of working in the open. Teams that document their thinking, share their research findings, and publish their design rationale build shared understanding faster, onboard new team members more effectively, and create an institutional memory that survives staff turnover.

What the Private Sector Can Borrow

• Define a service standard of your own, with explicit criteria and a genuine assessment mechanism, not a checklist teams fill in at the end of a project.
• Treat services as products with ongoing teams, not projects with handover dates.
• Invest in a design system that creates consistency across services and reduces duplicated effort.
• Publish your thinking internally with the same rigour that GDS publishes externally.
• Make user research a mandatory gate, not an optional input.

Where Even GDS Has Room to Grow

An honest assessment has to acknowledge that GDS has not been without limitations. Its influence has been strongest in central government and has had uneven reach into local government, where the most complex and resource-intensive services often live. The Service Standard, while valuable, has sometimes been applied in a formulaic way that prioritises compliance over genuine improvement. And the emphasis on digital channels, while right for many services, has at times obscured the needs of users who cannot or prefer not to engage digitally.

These are not reasons to dismiss what GDS built. They are reasons to apply its lessons with nuance. The principles are sound. The implementation is, like all service design, a continuous process of learning and adjustment. For any organisation serious about designing services that genuinely work for the people who use them, GDS's body of work remains one of the most valuable reference points available. The mistake is treating it as a finished answer rather than a starting point.