What it is
A diagram that maps the customer’s frontstage experience alongside the backstage actions, support processes, and systems required to deliver it, separated by lines of interaction, visibility, and internal support.
When to use it
During Synthesize and Ideate, for service design where operations and technology must align with the experience.
Why (value)
Connects the user experience to the organizational machinery behind it, exposing operational gaps, redundant work, and failure points invisible on a journey map alone.
How to run it
- Start from a customer journey (frontstage actions).
- Add the line of interaction and the frontstage touchpoints.
- Below the line of visibility, map backstage actions.
- Add support processes and systems below that.
- Mark failure points and improvement opportunities.
Inputs and outputs
- Inputs: A journey map, operational knowledge, cross-functional input.
- Outputs: A service blueprint linking frontstage experience to backstage delivery.
Time and effort
High. Requires cross-functional collaboration and detail.
Evidence and limitations
Frontstage accuracy depends on user research; backstage accuracy depends on operational input. Both can be evidence-based or assumed, label which. See Evidence and limitations.
Tips and pitfalls
- Involve operations and engineering, not just design.
- Use the standard lines (interaction, visibility, internal).
- Mark failure points explicitly, they are the payoff.
Variations
Current-state vs. future-state blueprints, simplified swimlane variants.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Experience orchestration extension (2026-11-07)
Connect each moment to visible touchpoints, backstage capabilities, accountable owners, and dependencies. Mark bridge/handoff and repair/recovery touchpoints, status changes, timing assumptions, and the user-visible consequence of failure. Keep current evidence separate from future intent. Backcast from the desired journey to capabilities and feasible increments; review the resulting sequence with operational and engineering partners.
Adapted from Risdon and Quattlebaum, Orchestrating Experiences (Rosenfeld Media, 2018), especially chapters 2–11.
Explore related methods
- Journey mapping — Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.
- Ecosystem mapping — Map the people, systems, channels, and relationships around a product to see the bigger system it lives in.
- Task flow diagramming — Diagram the single sequence of steps to complete one task, without user-specific branching.
