# Service Blueprint

A service blueprint connects a customer journey to frontstage interactions, backstage work, support processes, evidence, and operational ownership.

- Type: artifact
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/service-blueprint/>)

## What it means

A service blueprint is a research-based diagram of how an organization delivers a service. It aligns the user’s actions with visible employee or system interactions, behind-the-scenes activity, supporting processes, and physical or digital evidence. Unlike a journey map, it deliberately exposes the operational machinery beneath the experience.

## Why it matters

Many service failures are caused outside the interface: a policy creates a delay, a handoff loses context, or a support team lacks authority. Blueprinting gives product, operations, design, engineering, and frontline staff one view of those dependencies so they can improve the experience without merely repainting the surface.

## When to use it

Use it when a journey crosses teams or channels, when recurring failures have unclear causes, before redesigning an operationally complex service, or when translating customer research into process change. Start with one bounded scenario rather than an entire company.

## How it works

1. Choose one actor, scenario, start point, end point, and improvement goal; decide whether the map describes the current or desired service.
2. Ground the customer-action lane in journey research, then gather evidence from frontline staff, system owners, policies, logs, and observation.
3. Map visible frontstage interactions, backstage actions, support processes, evidence, handoffs, wait states, and lines of visibility in aligned columns.
4. Mark breakdowns, risks, accessibility barriers, duplicated effort, ownership gaps, timing, and measures that matter to both users and operators.
5. Validate the blueprint with people who use and deliver the service, assign owners to opportunities, and keep the map updated as work changes.

## A practical example

A telehealth team blueprints appointment booking through follow-up. It discovers that patients repeatedly enter medication details because the booking vendor cannot pass structured data to the clinical system. Rather than add another reminder screen, the team fixes the integration, clarifies consent, and gives support staff a safe escalation path.

## Where it breaks

A blueprint simplifies reality and can make uncertain assumptions look authoritative. Workshops dominated by managers may hide frontline work, informal workarounds, or harm experienced by marginalized users. The artifact does not improve a service by itself; evidence, ownership, budget, and operational follow-through do.

## Common mistakes

- Mapping an entire organization instead of one meaningful scenario.
- Inventing backstage activity without observing or interviewing the people who perform it.
- Treating the finished diagram as the deliverable rather than turning findings into owned changes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/service-blueprint/#visualization-service-blueprint>)

## Sources

1. [The 5 Steps to Service Blueprinting](<https://www.nngroup.com/articles/5-steps-service-blueprinting/>) — Nielsen Norman Group · Professional guidance
2. [Mapping Journeys](<https://www.thisisservicedesigndoing.com/methods/mapping-journeys>) — This is Service Design Doing · Method guide

## Related topics

- [Customer Journey Map](<https://wiki.soroush.uk/topic/customer-journey-map/>)
- [Ecosystem Map](<https://wiki.soroush.uk/topic/ecosystem-map/>)
- [Stakeholder Map](<https://wiki.soroush.uk/topic/stakeholder-map/>)
