Session Brief: Service Blueprinting

Goal

Artifact: Service Blueprint

Working Question

At which invisible backstage steps do fail points emerge that the customer experiences as friction at the frontstage?

Context

Customer journey; list of all touchpoints (digital, phone, physical); system landscape with ownership; known incidents or complaints from the last 90 days; SLAs of external providers.

Setup

• Format: Method session
• Duration: 4-6 h for one service slice, then 1 h maintenance per quarter
• Mode: Workshop
• Participants: One facilitator with service-design experience; one representative per frontstage role (sales, service, support); one owner per backstage system; one notetaker; one UX lead for the visibility line.
• Owner: One facilitator with service-design experience
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Service Blueprint. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Large whiteboard or Miro board with five lanes (Customer Actions, Frontstage, Backstage, Support Processes, Physical Evidence); stickies in five colors; ruler cards for lines (Interaction, Visibility, Internal Interaction); access to process diagrams and system documentation.

Preparation

Horizontal lanes: Physical Evidence at the top, then Customer Actions, Line of Interaction, Frontstage, Line of Visibility, Backstage, Line of Internal Interaction, Support Processes. Vertically split into journey phases.

Agenda

1. Phase 1: Customer Actions (45 min) Owner: Facilitator Action: Enter concrete customer actions per journey phase, verb-oriented and with touchpoint ("opens app", "calls hotline"). Take them from the journey, do not reinvent them. Hint: If this lane is created from scratch instead of coming from an existing journey, a precondition is missing. Pause and clarify the journey, otherwise the blueprint becomes speculation. Output: Service Blueprint

2. Phase 2: Frontstage (45 min) Owner: Facilitator Action: Add the visible employee or system actions below each Customer Action. Include role and tool. Put Physical Evidence (emails, receipts, app screen) above the actions. Hint: Frontstage is only what the customer directly experiences. Internal validations already belong behind the visibility line. Output: Fail Points

3. Phase 3: Backstage and support (60 min) Owner: Facilitator Action: Add backstage actions and support processes per frontstage step. Name owner and system. Connect with arrows, mark asynchronous handoffs. Hint: A backstage lane without owner is a blind spot. Better to write "unknown, clarify by ..." explicitly than assume an owner. Output: Ownership Map

4. Phase 4: Fail points and wait times (45 min) Owner: Facilitator Action: Mark fail points with red stickies (handoffs, external calls, manual steps). Quantify wait times and SLA breaches where possible. Hint: Black-box fail points without frequency or impact are subjective. Require at least one observation or metric per fail point. Output: Service Blueprint

5. Phase 5: Action slice (30-45 min) Owner: Owner Action: Prioritize three to five fail points by frequency x pain. Define one concrete improvement per point with owner and success metric. Hint: If the improvement is "more people", it is not one. Look for structural levers: automation, remove handoff, renegotiate SLA. Output: Fail Points

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Service Blueprint

Closeout

• Update result artifact: Service Blueprint
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Service Blueprint: Service Blueprinting

Working Question

At which invisible backstage steps do fail points emerge that the customer experiences as friction at the frontstage?

Context

Customer journey; list of all touchpoints (digital, phone, physical); system landscape with ownership; known incidents or complaints from the last 90 days; SLAs of external providers.

Participants

• Owner: One facilitator with service-design experience
• Participants: One facilitator with service-design experience; one representative per frontstage role (sales, service, support); one owner per backstage system; one notetaker; one UX lead for the visibility line.

Input

Large whiteboard or Miro board with five lanes (Customer Actions, Frontstage, Backstage, Support Processes, Physical Evidence); stickies in five colors; ruler cards for lines (Interaction, Visibility, Internal Interaction); access to process diagrams and system documentation.

Template

Service Blueprinting Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

• Area 1:
• Area 2:
• Area 3:
• Relationships / patterns:

Output artifacts

• Service Blueprint:
• Fail points:
• Ownership map:

Open questions

• ...

Next step

Owner, date, success signal.

Completion Check

• Service Blueprint is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision