USER-CENTRED DESIGN · UK GOVERNMENT PRACTICE
Two frameworks. One way of working.
UCD Services explains how user-centred design practice and the UK Government Digital Service delivery approach fit together — the Design Council's Double Diamond alongside the Service Standard and the Discovery, Alpha, Beta, and Live phases. Free, independent, and written in plain English.
FRAMEWORKS
The two frameworks
DOUBLE DIAMOND
Design Council
Divergent and convergent thinking across two diamonds — Discover, Define, Develop, and Deliver. A model for how to think before you build.
SERVICE STANDARD
GDS approach
Fourteen principles for building good public services, plus the Discovery → Alpha → Beta → Live delivery rhythm with assessment at key points.
VISUAL OVERVIEW
Thinking and delivery
PHASE INDEX
Delivery phases
Discovery
Understand the problem, users, and constraints before committing to a solution.
Outputs: User needs, problem definition, evidence, and a recommendation on whether to proceed.
Alpha
Test the riskiest assumptions with cheap prototypes before building the real service.
Outputs: A tested direction, validated assumptions, and a clear view of what to build or drop.
Beta
Build the real service and put it in front of real users, then iterate on live usage.
Outputs: A working service, performance data, support processes, and readiness for full launch.
Live
Run, support, and continuously improve the service in production.
Outputs: Ongoing measurement, iteration, incident response, and eventual retirement planning.
WHY BOTH MATTER
Frameworks that reinforce each other
The Double Diamond gives you the thinking. It describes when to expand exploration and when to narrow choices — first in the problem space, then in the solution space. Teams that skip the first diamond often build the wrong thing efficiently.
The phases give you the delivery rhythm. Discovery, Alpha, Beta, and Live provide a shared language for what the team is trying to achieve at each stage, what evidence is needed, and when independent assessment happens.
Together they reduce two common failures: jumping to solutions before understanding the problem, and shipping work that has not been tested against user need or the Service Standard. Neither framework replaces the other — they answer different questions.
METHODS
UCD methods
User interviews
Structured conversations with people who use or might use a service. Interviews surface needs, frustrations, and context that surveys alone rarely capture.
Ask UCD Chat about interviewingContextual research
Observing people in the settings where they actually encounter a problem. Context reveals workarounds, environmental constraints, and behaviours people struggle to articulate.
Usability testing
Watching representative users attempt realistic tasks with a prototype or live service. Testing exposes where the design confuses, blocks, or slows people down.
UX Principles on cognitive loadAccessibility testing
Checking that people with disabilities can perceive, operate, and understand the service. Combine automated checks with testing by people who use assistive technologies.
Journey mapping
A visual timeline of what someone does, feels, and needs across every step of a service. Journey maps make gaps, pain points, and hand-offs between teams visible.
Service blueprinting
A diagram linking front-stage user actions to back-stage processes, systems, and policies. Blueprints show where the experience depends on things users never see.
Problem framing
Restating a challenge as a user need rather than a predetermined solution. Good framing opens up more options and stops teams from defending the wrong problem.
Assumption mapping
Listing what you believe to be true about users, technology, and policy, then ranking assumptions by risk. High-risk assumptions become the focus of early research and prototyping.
PRODUCTS
UCDOps product family
UCDOps Agent
An AI agent that runs the full UCD pipeline — from research to prototype — with evidence and human approval at each step.
UCD Chat
Free AI chat for questions about user-centred design, UX, service design, and research methods.
UCD Coach
A free daily design digest covering trends, tools, AI workflows, and UCD methods.
UX Principles
Thirty evidence-based UX laws with illustrations and further reading for each principle.
FAQ
Common questions
Is Alpha the same as Develop in the Double Diamond?
Not exactly. Develop in the Double Diamond is a thinking mode — exploring possible solutions. Alpha is a delivery phase where you prototype and test the riskiest assumptions. Alpha work often involves Develop-style exploration, but the phase also includes converging on a direction to take into Beta.
Do I need a service assessment?
If you are building or changing a transactional government service in the UK, you will typically need assessment against the Service Standard at key points — usually at the end of Discovery, Alpha, and before going Live. The exact requirements depend on your department and the type of service. Check with your digital lead or the GOV.UK guidance on assessments.
Does the Double Diamond replace agile?
No — they complement each other. The Double Diamond describes how to think (diverge and converge twice). Agile describes how to deliver in iterations. Teams often run sprints inside each delivery phase, using diamond thinking within each sprint cycle.
Can I use these frameworks outside government?
Yes. The Double Diamond is widely used across sectors. The Service Standard and delivery phases originated in UK government, but the underlying ideas — understand users, prototype early, iterate on evidence — apply wherever you are building services for real people.
How long does each phase take?
There is no fixed timetable. Discovery often runs four to eight weeks; Alpha and Beta vary widely depending on complexity, team size, and risk. Duration should be driven by what you need to learn or prove, not by a calendar template.
Where does the Service Standard fit in day-to-day work?
The Service Standard is a set of principles teams use to shape decisions throughout delivery — who you involve, how you measure success, what you publish. Assessment is a checkpoint; the standard itself is the ongoing reference for how to build good services.
See how the frameworks map
Our interpretive guide to where Discover, Define, Develop, and Deliver sit against Discovery, Alpha, Beta, and Live.