← Back to Design craft
What it is: a view of how the internal company teams and processes act together to create the experience customers, clients, and others have.
When to use it:
Service blueprints help highlight how teams two or more degrees removed from the user action still influence the outcome
Seeing the relationship between the workstreams can help uncover dependencies and details of a requirement that are key to success
How to use it:
Start broad, gather all the pieces you know
Document gaps in knowledge so we don’t forget we don’t know
As the project progresses, or in dedicated workshops, add details and questions
As project decisions are made, use this as a tool to identify knock on effects
This works great with
Cross-project views - service blueprints gives you a cross-section snapshot of your flow and who is involved in making it happen. Cross-project views give you a way to catch which of those back-end processes you need to pay attention to
← Back to Design craft
