Complete firstClear scope
Agree the subject, boundary and decision before filling the model.
A broad or mixed scope produces a misleading model.
Method guideUX Design
Service Blueprinting
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityHigh
Time0.5-2 Tage
Participants6-12
FormatWorkshop
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant evidence
Bring source material and people who know the work; distinguish facts from assumptions.
Unverified interpretations become false certainty.
02
Preparation
What needs to be ready before start
Materials
Shared visual workspace, source evidence, and an agreed decision question.
People / roles
Facilitator, customer-facing staff, backstage operations, system owner.
Pre-read
Collect existing data, examples, constraints and relevant stakeholder perspectives.
Time needed
90–150 min for one bounded episode; validate operational details afterward.
Setup
Choose one service scenario, customer, start/end and business question. Combine customer actions with observed employee work, logs and system evidence. Align customer actions, visible interactions and backstage/support work by time. Mark line of interaction and visibility, handoffs, waits, failures and measures. Refine the as-is or to-be view; assign owners to a few evidenced service gaps.
03
Core question
The one question this method answers
Where do customer actions depend on backstage work, systems, or handoffs?
04
Flow
Phases with goal, actions, output and pitfall
Maps customer actions, visible service interactions and supporting operations to reveal service gaps and handoffs.
Service blueprint: one evidenced stage
Fictional worked example
Fictional, current parcel return: customer starts return in the portal → label is created → parcel is handed in. Frontstage: confirmation page and status email. Backstage: return inspection and refund. Support process: payment provider supplies status. Observed gap: status remains unchanged for two days after receipt; cause and duration come from internal logs, not assumption.
| Scenario | Customer action | Frontstage | Backstage | Support process |
|---|---|---|---|---|
| Stage 1Record an observation or example for this row. | Patient selects follow-up | Portal shows slots | Reception updates calendar | Practice system syncs slots |
1. Customer action
- Stage 1
- Patient selects follow-up
2. Frontstage
- Stage 1
- Portal shows slots
3. Backstage
- Stage 1
- Reception updates calendar
4. Support process
- Stage 1
- Practice system syncs slots
Fictional, current parcel return: customer starts return in the portal → label is created → parcel is handed in. Frontstage: confirmation page and status email. Backstage: return inspection and refund. Support process: payment provider supplies status. Observed gap: status remains unchanged for two days after receipt; cause and duration come from internal logs, not assumption.
- 1
Scope
Bound the service case
Goal
Blueprint scope
Inputs for this step
- Service goal, customer group and sponsor
Actions
- Choose one end-to-end case with start, end, target group and a specific quality question.
Output
Blueprint scope
Blueprint scope
Quality check
Is this one traceable case?
Pitfall
Too many variants share one timeline. Separate cases with different rules or flows.
Timing: Allow time according to scope and evidence; no universal duration.
- 2
Evidence
Gather evidence
Goal
Evidence-backed service material
Inputs for this step
- Journey, staff interviews, observation and logs
Actions
- Collect customer actions and internal work from direct sources. Label each step’s source and time period.
Output
Evidence-backed service material
Evidence-backed service material
Quality check
Are customer and employee perspectives represented?
Pitfall
Backstage steps are filled from assumption. Label the gap and observe or interview the responsible role.
Timing: Allow time according to scope and evidence; no universal duration.
- 3
Blueprint
Connect frontstage and backstage
Goal
As-is or to-be service blueprint
Inputs for this step
- Evidenced sequence, touchpoints, actors and systems
Actions
- Align customer action, visible interaction, invisible work and support processes on the same timeline.
Output
As-is or to-be service blueprint
As-is or to-be service blueprint
Quality check
Are visibility and interaction lines traceable?
Pitfall
Roles and systems sit side by side without handoffs. Connect only evidenced handoffs and name the handing-off role.
Timing: Allow time according to scope and evidence; no universal duration.
- 4
Actions
Prioritize service breakdowns
Goal
Prioritized service improvements
Inputs for this step
- Blueprint, wait times, quality and service data
Actions
- Mark waits, failures and ownership; select a few breakdowns and agree a measure or change.
Output
Prioritized service improvements
Prioritized service improvements
Quality check
Does each breakdown have evidence and an owner?
Pitfall
Solutions are chosen before the cause is known. State the observed breakdown first and investigate its cause.
Timing: Allow time according to scope and evidence; no universal duration.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Maps customer actions, visible service interactions and supporting operations to reveal service gaps and handoffs. Record scope, evidence, assumptions, owner and next review in the versioned artifact.
Versioning / ownership
Record scope, date, participants, source version and owner. Note changed assumptions and the reason for each revision.
Tool alternatives
- Shared whiteboard or paper template
- Source links, records or measurement data
service-blueprint-working-template.md
Prepare the decision, source evidence and next review.
Service Blueprinting: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Run the method Time: See catalog planning range; no universal duration.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared visual workspace, source evidence, and an agreed decision question.
- Roles: Facilitator, customer-facing staff, backstage operations, system owner.
- Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
- Overall time needed: 90–150 min for one bounded episode; validate operational details afterward.
- Setup: Choose one service scenario, customer, start/end and business question. Combine customer actions with observed employee work, logs and system evidence. Align customer actions, visible interactions and backstage/support work by time. Mark line of interaction and visibility, handoffs, waits, failures and measures. Refine the as-is or to-be view; assign owners to a few evidenced service gaps.
Prepare for the work steps
Scope: Bound the service case
- Service goal, customer group and sponsor
Evidence: Gather evidence
- Journey, staff interviews, observation and logs
Blueprint: Connect frontstage and backstage
- Evidenced sequence, touchpoints, actors and systems
Actions: Prioritize service breakdowns
- Blueprint, wait times, quality and service data
Service blueprint: one evidenced stage
| Scenario | Customer action | Frontstage | Backstage | Support process |
|---|---|---|---|---|
| Stage 1 |
- Stage 1: Record an observation or example for this row.
Use evidence and aligned stages; separate observed service from proposed future state.
The 5 Steps to Service Blueprinting · Nielsen Norman Group
Scope: Bound the service case
Expected artifact: Blueprint scope
Blueprint scope
Entry:
...
- Is this one traceable case?
Evidence: Gather evidence
Expected artifact: Evidence-backed service material
Evidence-backed service material
Entry:
...
- Are customer and employee perspectives represented?
Blueprint: Connect frontstage and backstage
Expected artifact: As-is or to-be service blueprint
As-is or to-be service blueprint
Entry:
...
- Are visibility and interaction lines traceable?
Actions: Prioritize service breakdowns
Expected artifact: Prioritized service improvements
Prioritized service improvements
Entry:
...
- Does each breakdown have evidence and an owner?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/service-blueprint/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
service-blueprint-beispiel.md
Concrete filled scenario, fictional example
Fictional, current parcel return: customer starts return in the portal → label is created → parcel is handed in. Frontstage: confirmation page and status email. Backstage: return inspection and refund. Support process: payment provider supplies status. Observed gap: status remains unchanged for two days after receipt; cause and duration come from internal logs, not assumption.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Bound the service caseToo many variants share one timeline.View in phase
- Gather evidenceBackstage steps are filled from assumption.View in phase
- Connect frontstage and backstageRoles and systems sit side by side without handoffs.View in phase
- Prioritize service breakdownsSolutions are chosen before the cause is known.View in phase
Trap
Bound the service case
Symptom
Too many variants share one timeline.
What to do
Separate cases with different rules or flows.
Trap
Gather evidence
Symptom
Backstage steps are filled from assumption.
What to do
Label the gap and observe or interview the responsible role.
Trap
Connect frontstage and backstage
Symptom
Roles and systems sit side by side without handoffs.
What to do
Connect only evidenced handoffs and name the handing-off role.
Trap
Prioritize service breakdowns
Symptom
Solutions are chosen before the cause is known.
What to do
State the observed breakdown first and investigate its cause.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Stop if the decision question or scope is disputed; align it first.
Stop if key inputs are unavailable; list what evidence is needed.
Stop if the group treats assumptions as observed facts.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.