What on earth is a service blueprint?
Making customer journeys, team interactions and hidden operational friction visible.
Written by Danny Tomalin · Originally published by Razor
Condensed adaptation of Danny’s article for this site.See the service behind the screen
A requested software change can be a symptom of a problem elsewhere in the business. A service blueprint makes the customer journey visible alongside the people, backstage activities and supporting processes that deliver it.
Build it with the people who do the work
The map starts with the user’s goals. Conversations across teams reveal handovers, duplicated effort and workarounds. Observation and contextual research matter too: being in a meeting does not tell you everything about someone’s working day.
Choose a useful change
A blueprint helps a team identify where effort is being lost and agree what to improve. Automation can help, but the right answer can also involve a manual step. Proposed changes need to be tested with the people affected.
Deliver in manageable steps
An understood service creates a better foundation for an MVP and later improvements. Each step can deliver value while moving towards the wider goal. The original article was written for Razor; this is a shorter adaptation.