Swim Lane Maps

Swim Lane Maps

Overview

Swim lane maps (service blueprints) are specialized flowcharts for designing service processes. They visually distinguish between customer-visible activities and back-office operations through the “line of visibility,” clarifying responsibilities and identifying potential failure points.

ELI5

A Swim Lane Map is like a football play diagram showing which player does what:

Football example:

• QB lane: Throw the ball
• WR lane: Catch and run
• OL lane: Block defenders

Each player has their “lane” — you can see who does what!

Restaurant example:

Customer  → Enters → Orders → Eats → Pays
Host      → Greets → Seats            → Thanks
Server    →        → Takes order → Serves → Brings check
Kitchen   →                    → Cooks

Line of Visibility = What the customer SEES vs. what they DON’T see:

• Above line (visible): Host, Server, you eating
• Below line (invisible): Kitchen cooks, dishwasher, cashier

Memory: “Swim lanes = Who does What!”

Core Concept

A service blueprint is a specialized flowchart for designing service processes that makes visible the distinction between high customer contact aspects and those activities the customer does not see. The blueprint is organized into horizontal “lanes” where each lane represents the activities controlled by a specific entity.

Key elements:

1. Levels/Lanes: Each lane shows activities controlled by a specific entity
2. Line of Visibility: Boundary separating what customer sees (front stage) from back-office (hidden)
3. Customer Actions: Top level shows activities under customer control
4. Front Stage: Service provider activities visible to customers
5. Back Stage: Internal support activities hidden from customers

The line of visibility is the defining feature that distinguishes service blueprints from ordinary flowcharts.

Components / Framework

Component	Description	Source
Service Blueprint	Specialized flowchart for service process design	MGH_book.pdf p.211-212
Swim Lanes	Horizontal bands showing entity controlling activities	MGH_book.pdf p.211-212
Line of Visibility	Boundary separating high-contact from back-office	MGH_book.pdf p.211-212
Front Stage	Customer-visible service activities	IPPTChap009.pptx Slide 22
Back Stage	Internal support activities (hidden)	IPPTChap009.pptx Slide 24
Customer Actions	Activities under customer control (top lane)	MGH_book.pdf p.211-212

Typical Lane Structure (top to bottom):

Lane Level	Entity	Example Activities
Top level	Customer	Enters, orders, eats, pays
Second level	Service manager	Greets, seats, thanks
Third level	Service provider	Takes order, serves, brings check
Lowest level	Internal support	Accounting, kitchen, IT

Example

From Slides - Service Blueprinting: The standard tool for service process design is the flowchart, called a service blueprint. Its unique feature is the distinction between high customer contact aspects and those activities the customer does not see, made by a “line of visibility.”

Restaurant Service Blueprint:

Lane 1: Customer → Enters → Orders → Eats → Pays → Leaves
Lane 2: Host → Greets → Seats →               → Thanks
Lane 3: Server →         → Takes order → Serves → Brings check
Lane 4: Kitchen →                    → Cooks
Lane 5: Cashier →                                  → Processes

Line of visibility: Between Server/Kitchen (customer sees server, not kitchen)

Hospital Emergency Department:

Lane 1: Patient → Arrives → Describes symptoms → Waits → Treatment → Leaves
Lane 2: Triage Nurse → Assesses → Prioritizes
Lane 3: Registration →                    → Records info
Lane 4: Doctor →                          → Examines → Orders tests → Discharges
Lane 5: Lab →                                          → Processes → Reports

Line of visibility: Patient sees Triage, Registration, Doctor — not Lab processing

Implications

Why it matters to organizations:

1. Clarifies Responsibilities: Each lane shows exactly who does what, reducing confusion and accountability gaps.

2. Identifies Handoff Risks: Where work passes between lanes (handoffs) are potential failure points. Blueprints make these visible.

3. Designs Customer Experience: Organizations can intentionally design what customers see (front stage) to create desired impressions.

4. Coordinates Front/Back Stage: Ensures back-office support processes align with front-stage customer interactions.

5. Finds Bottlenecks: Visual mapping reveals where work piles up and processes slow down.

6. Standardizes Service Delivery: Blueprints enable consistent service design across locations and staff.

Related Concepts

• Flowcharting: General process mapping technique that service blueprints extend
• Customer Journey Mapping: Focuses on customer experience rather than internal processes
• Service Encounter: Direct customer-provider interaction points (front stage)
• Time-perishable Capacity: Capacity management affects how lanes are staffed
• Customer as Input: Customer actions lane shows input requirements

Quick Summary

Exam Recall Bullets:

• Service blueprint = specialized flowchart for designing service processes
• Levels/Lanes show entity controlling activities (customer, manager, provider, internal)
• Line of Visibility separates high-contact (visible) from back-office (hidden)
• Top level: activities under customer control
• Second level: service manager/front stage activities
• Third level: service provider/repair activities
• Lowest level: internal support (accounting, IT)
• Handoffs between lanes are potential failure points

Exam Tips:

• MCQ: Everything ABOVE line of visibility = customer sees it; BELOW = hidden
• MCQ: Front stage = customer interaction; Back stage = support
• Essay: Always identify line of visibility when creating service blueprint
• Remember: Line of visibility is THE unique feature distinguishing service blueprints

Sources

MGH_book.pdf [p.211-212], IPPTChap009.pptx [Slide 22, 24]