A service blueprint is a diagram that maps a service delivery process from two sides at once: what the customer experiences, and everything happening behind the scenes that makes that experience possible.
Developed by G. Lynn Shostack in a 1984 Harvard Business Review article, it organizes a service into five components, customer actions, frontstage (onstage) employee actions, backstage employee actions, support processes, and physical evidence, separated by specific lines showing what the customer can see and where work crosses internal team boundaries.
It matters for Six Sigma work because most current-state tools (like process maps or value stream maps) were built for manufacturing flow, not customer-facing services; a service blueprint fills that specific gap by capturing both the customer’s visible experience and the invisible operational work behind it in a single view.
Quick Reference Table
| Component | What It Captures | Example |
| Customer Actions | Steps the customer takes throughout the service | Booking an appointment, checking in, receiving service |
| Frontstage (Onstage) Actions | What employees or systems do that the customer can see | A receptionist greeting a patient, a chatbot answering a question |
| Backstage Actions | Employee work the customer cannot see | A nurse preparing a chart before the patient is called in |
| Support Processes | Internal systems and departments enabling the service | IT systems, inventory management, billing |
| Physical Evidence | Tangible or digital items the customer interacts with | A receipt, a confirmation email, a waiting room |
Table of contents
- Quick Reference Table
- Key Takeaways
- What Is a Service Blueprint?
- The Lines That Organize a Service Blueprint
- Service Blueprint vs. Customer Journey Map: What’s the Difference?
- How Do You Create a Service Blueprint?
- How Does a Service Blueprint Fit Into a Six Sigma Project?
- Frequently Asked Questions on Service Blueprint
Key Takeaways
- A service blueprint shows two sides of a service at once. It maps what the customer experiences and what the organization does behind the scenes to deliver it, in a single, unified diagram.
- It was introduced in 1984 by G. Lynn Shostack, a banker frustrated that services lacked the same structural design rigor routinely applied to physical products.
- The blueprint has five standard components: customer actions, frontstage actions, backstage actions, support processes, and physical evidence.
- Specific lines organize the diagram and carry real meaning. The line of interaction separates the customer from employees; the line of visibility separates what the customer can and can’t see; the line of internal interaction separates frontline staff from internal support functions.
- A service blueprint is not the same as a customer journey map. A journey map shows only the customer’s experience; a blueprint shows that plus everything happening behind it that makes the experience possible.
- For Six Sigma practitioners, a service blueprint fills a real gap. Most current-state tools (process maps, value stream maps) were built around manufacturing flow; a service blueprint is purpose-built for customer-facing service delivery, where visibility to the customer is itself a critical variable.
- Building a blueprint should be a cross-functional, collaborative exercise, not a document one person produces alone, since its main value comes from surfacing gaps between departments that don’t normally see each other’s work.
What Is a Service Blueprint?
A service blueprint is a visual map of how a service is actually delivered, showing what the customer does, what frontline employees do, what happens backstage, and which internal systems or support teams make the whole experience possible.
The technique was introduced by G. Lynn Shostack in a 1984 Harvard Business Review article. Shostack was a banker, not a designer, and she was frustrated that services were being managed without any of the structural rigor routinely applied to designing a physical product. Her answer: treat a service as a system, map that system visually, and use the resulting map to design, diagnose, and improve it, the same discipline product design already had, applied to something far less tangible.
Public, Onsite, Virtual, and Online Six Sigma Certification Training!
- We are accredited by the IASSC.
- Live Public Training at 52 Sites.
- Live Virtual Training.
- Onsite Training (at your organization).
- Interactive Online (self-paced) training,
The Five Components of a Service Blueprint
A conventional service blueprint is built from five distinct components, typically arranged as rows in a matrix, with time or process steps running left to right across the top.

- Customer Actions — the steps, choices, and interactions the customer performs while evaluating, purchasing, or using the service. These are placed at the top of the blueprint, since they’re the reason the rest of the diagram exists.
- Frontstage (Onstage) Employee Actions — what employees do when they interact directly, face-to-face, with the customer. In technology-delivered services with no employee physically present, this becomes “onstage technology,” a website, a self-check-in kiosk, or a chatbot the customer interacts with directly.
- Backstage Employee Actions — work performed by employees that supports the frontstage interaction but that the customer never sees directly.
- Support Processes — the internal systems, departments, and processes (IT, inventory, billing) that enable both frontstage and backstage work to actually happen.
- Physical Evidence — tangible or digital items the customer encounters throughout the service, a receipt, a confirmation email, the physical space itself, that shape their perception of quality.
Also Read: Custom Manufacturing Services: How to Deliver Quality at Every Batch Size
The Lines That Organize a Service Blueprint
This is the structural detail that gives a service blueprint its real analytical power, and it’s worth understanding precisely rather than treating the lines as arbitrary dividers.
| Line | What It Separates | Why It Matters |
| Line of Interaction | Customer actions from employee/system actions | Marks every point where the customer and the organization actually meet |
| Line of Visibility | What the customer can see from what happens behind the scenes | The single most important line in the diagram, separating frontstage from backstage |
| Line of Internal Interaction | Frontline employee actions from internal support processes | Shows where frontline work depends on a different team or system entirely |
Why does the line of visibility matter so much specifically?
It’s the line that reveals where an organization’s internal complexity is genuinely invisible to the customer, and where it might be leaking through in ways that actually hurt the experience (a long, unexplained wait while backstage work happens, for example). Improvement opportunities cluster disproportionately around this line, since it’s where operational reality and customer perception most often diverge.
Service Blueprint vs. Customer Journey Map: What’s the Difference?
This comparison shows up in nearly every source on this topic, and it’s worth stating precisely rather than vaguely.
| Factor | Customer Journey Map | Service Blueprint |
| Perspective | The customer’s experience only | The customer’s experience plus everything behind it |
| Shows backstage work? | No | Yes, explicitly, as its own dedicated layer |
| Best for | Understanding customer emotions and pain points | Diagnosing and redesigning the operational delivery of a service |
How do the two relate?
A service blueprint can be thought of as a journey map’s second half: it takes the same customer actions a journey map already captures and adds the operational reality behind them, frontstage actions, backstage actions, support processes, and physical evidence, that a journey map alone never shows. Many teams build a journey map first, then extend it into a full blueprint once they need to understand and fix the operational side of a customer’s experience, not just describe it.
Also Read: Six Sigma in Telecommunication and ISPs: A Guide to Perfect Service
How Do You Create a Service Blueprint?
1. Identify the Specific Service Process to Blueprint
Choose a defined service journey with clear start and end points, not an entire, sprawling customer relationship. A blueprint works best scoped to something specific enough to map in real detail.
2. Map Customer Actions First
List the actual steps the customer takes, in order, across the top of the blueprint. This becomes the backbone the rest of the diagram is built against.
3. Add Frontstage and Backstage Employee Actions
For each customer action, identify what employees (or systems) are doing visibly, and what’s happening behind the scenes to support it, placing these below the line of interaction and line of visibility respectively.
4. Add Support Processes and Physical Evidence
Map the internal systems and departments enabling the backstage work, and note the physical or digital evidence the customer encounters at each step.
5. Involve Representatives From Every Function Shown in the Blueprint
Building a blueprint is a genuinely collaborative, cross-functional exercise, not a document one person produces alone. Involving people from each department shown in the diagram, and incorporating real Voice of the Customer input rather than internal assumptions, is what surfaces the hidden gaps between departments that don’t normally see each other’s side of the process.
How Does a Service Blueprint Fit Into a Six Sigma Project?
A service blueprint is the specific tool best suited to customer-facing service processes, where a standard process map or value stream map’s manufacturing-flow orientation doesn’t naturally capture what matters most: the line between what the customer sees and what they don’t.
In a Measure-phase current state analysis for a service-industry DMAIC project (healthcare, financial services, hospitality, customer support), a service blueprint accomplishes what a generic process map alone can’t: it makes the customer’s actual visibility into the process an explicit, mapped variable, not an afterthought.
This matters directly for the Analyze phase that follows, since a significant share of service-quality root causes trace back to invisible backstage delays or handoffs the customer experiences only as unexplained waiting, exactly what the line of visibility is specifically designed to expose.
Real-World Example: Healthcare Intake Blueprint

Customer actions: a patient arrives, checks in at the front desk, waits, is called back, meets with a nurse, then a physician.
Frontstage actions: the receptionist greets the patient and processes check-in; the nurse calls the patient back and takes vitals.
Backstage actions: administrative staff verify insurance eligibility before the patient is called back; a medical assistant prepares the exam room and pulls the patient’s chart.
Support processes: the practice management system that stores patient records and schedules; the insurance verification system.
Physical evidence: the check-in kiosk or clipboard, the waiting room itself, an after-visit summary handed to the patient at the end.
The insight the blueprint surfaces: mapping this process reveals that the patient’s perceived wait time is driven largely by backstage insurance verification, a step entirely invisible to the patient, who simply experiences it as “waiting,” with no indication of why. This is exactly the kind of gap a service blueprint is specifically built to expose, one a simple process map, without the line of visibility, would likely miss entirely.
Common Mistakes When Building a Service Blueprint
- Building it without cross-functional participation. A blueprint built by only one department typically misses the backstage reality of other teams whose work the customer never sees.
- Skipping the line of visibility distinction entirely. Without explicitly separating frontstage from backstage, the blueprint loses the specific analytical power that makes it different from a basic process map.
- Scoping it too broadly. Attempting to blueprint an entire, sprawling customer relationship at once, rather than one clearly defined service journey, produces a diagram too large to act on.
- Treating the blueprint as a one-time document. A blueprint reflects a snapshot of the process at a point in time; like any current-state tool, it should be revisited as the process changes.
- Confusing a service blueprint with a customer journey map. Using the terms interchangeably risks stopping at customer perception without ever mapping the operational reality that a blueprint’s real value depends on.
Frequently Asked Questions on Service Blueprint
Q: What is a service blueprint?
A: A service blueprint is a diagram mapping a service delivery process from both the customer’s and the organization’s perspective at once, showing customer actions, frontstage and backstage employee actions, support processes, and physical evidence.
Q: What are the components of a service blueprint?
A: The five standard components are customer actions, frontstage (onstage) employee actions, backstage employee actions, support processes, and physical evidence.
Q: What is the line of visibility?
A: The line of visibility separates what the customer can see (frontstage actions) from what happens behind the scenes (backstage actions). It’s the most analytically important line in a service blueprint, since gaps between operational reality and customer perception cluster around it.
Q: What is the difference between a service blueprint and a customer journey map?
A: A customer journey map shows only the customer’s experience. A service blueprint shows that same experience plus the frontstage actions, backstage actions, support processes, and physical evidence that make it possible, essentially extending a journey map to include the operational side.
Q: How do you create a service blueprint?
A: Identify a specific, well-scoped service process, map customer actions first, add frontstage and backstage employee actions below the appropriate lines, add support processes and physical evidence, and build the whole diagram collaboratively with representatives from every function shown.
Q: How does a service blueprint apply to Six Sigma?
A: It functions as a Measure-phase current-state tool specifically suited to service-industry processes, filling a gap that manufacturing-oriented tools like process maps and value stream maps don’t naturally address: making the customer’s visibility into the process an explicit, mapped variable.
Final Words
A service blueprint earns its place in a service improvement toolkit by doing something a standard process map doesn’t: making explicit what the customer can and can’t see. That line of visibility is where a disproportionate share of service-quality problems actually hide, invisible backstage delays experienced by the customer only as unexplained waiting.
Built collaboratively, with real participation from every function it touches, a service blueprint turns that invisible operational reality into something a Six Sigma team can actually diagnose and improve.
Mapping a service process well enough to see where invisible backstage work is actually hurting the customer experience is a genuine Measure-phase skill for service-industry improvement projects.
Six Sigma Development Solutions, Inc. (SSDSI) is IASSC-accredited and 5-star rated on Google Reviews, having certified 5,322+ professionals across 600+ organizations in 52 cities. Our onsite, live virtual, public, and online Green Belt and Black Belt training covers current-state analysis tools, including service-specific mapping techniques, in the depth needed to diagnose real service-quality gaps. Explore SSDSI’s Green Belt certification to build that foundation.
About Six Sigma Development Solutions, Inc.
Six Sigma Development Solutions, Inc. offers onsite, public, and virtual Lean Six Sigma certification training. We are an Accredited Training Organization by the IASSC (International Association of Six Sigma Certification). We offer Lean Six Sigma Green Belt, Black Belt, and Yellow Belt, as well as LEAN certifications.
Book a Call and Let us know how we can help meet your training needs.


