| name | itk-service-blueprint |
| description | Outline and visualize a service to connect the user experience, or “frontstage,” to what happens behind-the-scenes, or “backstage.” |
| intent | Achieve a holistic, shared perspective of how the user experiences your service. Provide insights about critical moments and possible improvement throughout the service. Transform the service and create change. |
| type | component |
| phase | understand |
| outcome | understand |
| difficulty | advanced |
| group_size | 5+ people |
| time_required | 60+ minutes |
| best_for | ["Diagnosing root causes of a complex problem that spans multiple teams, systems, or touchpoints before committing roadmap resources","Aligning cross-functional stakeholders on how frontstage user experience maps to backstage operations and dependencies","Identifying handoff failures and orchestration gaps when a user journey crosses organizational or technical boundaries","Planning a service redesign where fixing the visible experience requires changing backend processes, policies, or systems","Surfacing systemic friction and ownership ambiguity that single-team retrospectives or journey maps cannot reveal"] |
| sources | ["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/service-blueprint/"] |
Service Blueprint
What Is It
Outline and visualize a service to connect the user experience, or “frontstage,” to what happens behind-the-scenes, or “backstage.”
Why Use It
Achieve a holistic, shared perspective of how the user experiences your service. Provide insights about critical moments and possible improvement throughout the service. Transform the service and create change.
When to Use It
When a problem spans multiple offerings, groups, or locations. When identifying the root cause of a complex problem. When streamlining a user experience to remove barriers or blockages.
How to Do It
- Identify the problem space that is key to the success of your service. The opportunity space should be easy to understand, a simple subject matter, and based on data.
- Pick the scenarios within your problem space that will have the most impact. Develop a scenario statement using the following format: “A user wants/tries to ___, and experiences ____, resulting in ____.” Then, break down your scenario into steps and touchpoints.
- Hold a blueprinting workshop with stakeholders and users to develop the end-to-end view of each scenario. Lay out the steps and touchpoints beforehand, and add detailed layers to capture the critical moments and ideas. Blueprint Layer Definition Step Definition What happens in the step Touchpoint What/where of the step’s interaction Actor Who supports that step System Technology, hardware, processes Observation Notes that add detail to the step Data Metrics to indicate importance Policy Rules that make it so Question Questions that need to be followed up Critical Moment Sources of pain that breakdown the experience Idea Opportunity to improve overall impact
- Separate the critical moments and ideas to identify insights and potential service improvements. Look to amend critical moments that could leave the user dissatisfied with the service.
- Out of the critical moments and ideas, themes will emerge for service improvements. Create categories and relationships between themes.
- Take action on the strategic fixes to drive service improvement!
Key Concepts
Frontstage vs. Backstage — Frontstage is everything the user directly experiences; backstage is the people, systems, and processes invisible to them. Mapping both reveals where backend constraints silently degrade the user experience.
Line of Visibility — The boundary separating what users see from what happens behind the scenes. Tracing how actions cross this line exposes where frontstage promises break against backstage reality.
Touchpoint — A specific point of interaction between the user and the service at each step. Cataloging touchpoints clarifies where to instrument metrics and where experience quality is won or lost.
