Digitise a Citizen or Customer Service
Digital Transformation · 4–8 weeks · Advanced
The job
Move a paper-based or in-person service to digital, keeping the human experience front and centre.
What the sponsor gets
Each canvas and map from this playbook — Persona Canvas, Service Blueprint, Pre-Mortem Canvas, Experiment Canvas, Journey map — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Understand the current service
Shadow the existing service for a full cycle. Observe staff and customers/citizens interacting with it. Collect volume data, error rates, processing times, and complaint logs.
Tip: The highest-volume transactions often aren't the most painful — interview users to find out which interactions they dread most.
Build citizen/customer personas
Create Persona canvases for 2–3 key user segments, including at least one digitally excluded group. Design for the least digitally confident user — if it works for them, it works for everyone.
Tip: Include staff personas too — they're users of the digital service as well, and their experience determines whether the service actually works.
Blueprint the current service end-to-end
Create a Service Blueprint of the as-is service, capturing front-stage interactions, back-stage processes, and support systems. Highlight manual steps, handoffs, and failure points.
Tip: The paper forms people fill in are often the best documentation of what the service actually needs — the official spec is usually out of date.
Map the future digital journey
Create a journey map for the digitised service. Design the path of least resistance for common transactions, with clear off-ramps to human support for complex cases.
Tip: The biggest mistake in service digitisation is forcing 100% digital — always design the "I need to talk to someone" escape hatch.
Pre-mortem the digital transition
Run a pre-mortem with staff, policy, and technology stakeholders. Focus on: what fails for digitally excluded users, what happens when the system is down, and how errors get corrected.
Tip: Ask frontline staff — they'll predict the failure modes that architects miss.
Prototype and test
Build a minimal prototype of the highest-volume transaction. Test it with 10–15 real users, including at least 3 from your digitally excluded persona.
Tip: If users can't complete the task without help in testing, they won't complete it without help in production — iterate before launch.
Plan phased rollout with parallel running
Launch the digital service alongside the existing service. Monitor adoption rates, error rates, and user satisfaction. Only retire the old service when digital adoption exceeds 80% and error rates are stable.
Tip: Set up a feedback loop from day one — the first two weeks of live operation will reveal problems no amount of testing catches.
The canvases and maps
- Persona Canvas
- Goals, frustrations, behaviours, motivations and needs side by side, so the person you are designing for is specific enough to disagree about.
- Service Blueprint
- Five lanes stacked from what the customer sees and does down to the backstage processes and support systems behind it, so the handoffs nobody sees become the thing everyone can point at.
- Pre-Mortem Canvas
- It starts from failure — the project, how it failed, root causes, mitigations and early warnings — so people can voice doubts as foresight rather than dissent.
- Experiment Canvas
- Hypothesis, design, metrics and success criteria come before results and the decision, so the goalposts are written down before anyone sees the data.
- Journey map
- Stages run across and lanes run beneath them, so the experience reads in the order people live it and each low point lines up with what causes it.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.