← Services
Service 02 · Design

Services designed around real users and sound architecture

Discovery, research and user-centred design that turns customer needs into services people actually use. Design here means the whole service, not the screens: the process, the policy, the data model and the handoffs behind them.

Methodology

Research, prototype, test, decide. Then draw it properly.

01

Mixed-method research

Interviews, observation and diary studies alongside behavioural data. Qualitative tells you why, analytics tells you how often.

02

Service blueprinting

Front stage, back stage and the systems underneath on one page, so the design problem stops being mistaken for a UI problem.

03

Prototype at the right fidelity

Paper to working code, chosen by the question being answered. Prototypes exist to be wrong cheaply.

04

Test with real users

Moderated usability and accessibility testing, including assistive technology, with recruitment that reflects the actual audience.

05

Architect the solution

Domain and data model, integration boundaries and non-functional requirements agreed before build, not discovered during it.

06

Hand over a system

A design system with components, tokens and content rules, so the next team does not restart the argument.

What you get

Evidence, artefacts and a buildable design

  • Research findings with recordings and a traceable evidence base
  • Personas, journeys and a service blueprint
  • Clickable prototype, tested and iterated
  • Accessibility audit against WCAG 2.2 AA with fixes prioritised
  • Solution architecture, data model and integration contracts
  • Design system and content guidelines
Tools we use
FigmaFigJamDovetailMazeaxe DevToolsStorybookdesign tokensGOV.UK service manual
Where this sits in delivery

Design owns steps one and two of the framework and stays involved through alpha and beta. It never hands a static specification over a wall.

The delivery framework →

Show us the service people keep abandoning.