Service Design
Connect the experience people see with the teams, processes and systems that make it happen.
Support Capabilities
Service Design research that informs clearer decisions.
A service experience depends on more than an individual screen or conversation. We help your team use research to understand how customer-facing steps and behind-the-scenes work fit together, then develop and test practical improvements to the service.
What we look at
Front-stage interactions and scripts- Back-stage systems and handoffs
- Support artefacts and evidence of service
- Failure and recovery paths
How we study it
- Service blueprinting
- Co-design with staff and customers
- Prototype service scenarios
- Service requirements and implementation considerations
When to research
When service design helps
Use this work when people repeat information, receive inconsistent guidance, encounter unclear handovers or struggle to get an issue resolved. It can also support a new service concept, a redesigned journey or a change that spans digital tools and staff interactions.
A small organization may focus on one service flow. A larger organization may need to coordinate several teams, channels or locations. We agree boundaries around the user goal, decisions and delivery capacity.
What we investigate
Understand both sides of the service
We explore what users need to do, the interactions they experience and the work required to support those steps. This may include staff responsibilities, information flows, systems, policies and third-party dependencies within the agreed scope.
Examples include booking and appointment services, onboarding, customer support, delivery and returns, employee services and partner workflows. We consider relevant exceptions and recovery paths, not only the ideal journey.
Our approach
Research grounded in evidence
We choose methods according to the decision your team needs to make, the people involved and the context of use.
Findings are linked to observations and participant accounts, with coverage and limits kept visible.
From context to opportunity
Our research process
Gather evidence. Review existing findings and investigate relevant gaps in user and staff experience
Map the current state. Connect visible interactions with supporting work, dependencies and failure points
Develop options. Explore improvements with your teams, considering user needs and feasibility
Test priority ideas. Evaluate selected prototypes or scenarios and refine proposals using the findings
Prepare the handover. Document the proposed service, open questions, responsibilities and validation needs
The output
What your team receives
Depending on scope, deliverables can include a current-state blueprint, opportunity assessment, proposed future-state flow, prototype findings and service requirements. Requirements can describe relevant interactions, information needs, roles and exception paths.
We also identify assumptions, dependencies and decisions needing approval. A findings and planning workshop helps your team agree next steps. Deliverables are adapted to the people who will use them rather than assume a diagram alone is enough.
Research focus
What a service blueprint shows
A service blueprint maps user actions alongside visible service interactions and the supporting work behind them. It helps teams see where information, decisions or responsibilities move from one group to another.
We distinguish a researched current-state blueprint from a proposed future-state blueprint. Evidence, assumptions and gaps are labelled. A workshop map based only on internal knowledge is not presented as a validated account of users' experience.
Our research process
How research informs the design
We review relevant research and existing service information, then identify unanswered questions. Interviews, observation and task testing can explore user experiences. Staff discussions and workflow analysis help understand operational constraints and dependencies.
Co-design sessions bring relevant people together to develop options. Participation in a workshop does not prove a proposed service will work. Prototypes and controlled scenarios can test selected interactions before an operational pilot is considered.
Research focus
Plan improvements with delivery teams
We involve appropriate service, product, operations and technology stakeholders to understand constraints and discuss options. Priority decisions consider user impact, evidence strength, effort and dependencies, with uncertain estimates made visible.
Service Design is a support capability within our research-led UX work. It does not automatically include process implementation, software development, staff training or ongoing service operation. Budgets, delivery commitments and operational approval remain with the responsible teams unless separately contracted.
Global research
Consider variation across users and markets
Different users may need different channels or support routes. We agree which roles, access needs and contexts to include, and document study coverage. A proposed improvement should not simply move difficulty from users to staff or another part of the journey.
For multi-market work, language, service availability and local operating arrangements may affect the design. Local research and specialist reviews are scoped as needed. We do not assume one blueprint represents every market.
Clear boundaries
Test within appropriate boundaries
We agree participation, consent, recording and data access before research. Controlled scenarios can explore proposed interactions without requiring consequential transactions. Live pilots require separate arrangements, permissions and operational safeguards.
Prototype findings do not establish that the full service can operate at scale. Security, safety, legal and other specialist assessments are not replaced by service research. Proposed changes affecting those areas require review by the responsible specialists.
Measurement
Measure whether changes help
Relevant measures may include successful completion of a service task, repeated contacts, handover delays and reported effort. We can help define a baseline and follow-up questions where measurement is included.
Qualitative findings do not establish population prevalence, and a prototype cannot prove a commercial return. Research supports better-informed service decisions; it does not guarantee satisfaction, lower costs or revenue gains.
Before we begin
Frequently asked questions
Journey research studies the experience from the user's perspective. Service design uses that evidence alongside delivery context to develop and test how the service could work.
Yes. We review its coverage and evidence, then investigate gaps or changes rather than replace useful work without a reason.
No. We can focus on one important handover, support flow or recurring problem, making the boundaries and dependencies clear.
Share the service, intended users, known difficulties and teams involved. Include existing research or process maps if available. We will discuss scope, access, deliverables, timing and budget.
Experience Strategy
Translate research findings into priorities and an evidence-led direction.
Explore
UI Design & Prototyping
Explore and test proposed interfaces before implementation.
Explore
Design Systems
Components, tokens, and the rules that keep them consistent as products and teams grow.
Explore
Development Support
Help teams carry agreed experience decisions into implementation.
Explore
Let us help shape the next step
Your service has a UX problem.
Let’s find and fix it.
Next research service UI Design & Prototyping Your service has a UX problem. Let’s find and fix it. Contact Us Tell us which service needs to work better.