An iteration of the service blueprint
The service blueprint is a service design model. It helps to consider the different steps people go through when they use a service. This blueprint shows what happens before and after the service.
Such a canvas is something that every strategist adapts to its needs. Sometimes, strategist even creates a specific type of blueprint for specific projects.
People leave and come back
The first element that like to add in the blueprint is the « Re-join » phase. Usually, the blueprint goes from the « join » phase until the « leave » phase. But I think that we should ease the join phase for the previous user of the service. That’s why, in the iteration of the canvas I use, I always add a « re-join » phase at the end.
There you can imagine how you bring people back to your service. And you can see how to make it easier for these people.
People should easily leave your service, but even more easily come back.
Details for better management
As most of you know, a typical we divide the service blueprint into two sections: front stage and backstage. This way of dividing the canvas helps to differentiate the needs. We see what people will experiment. And on the other side we see what stakeholders have to do to make it happen. To enable the service blueprint to be more than an idea generation tool, we should have more details in the backstage part. By having more granularity, project managers can also use the tool. That’s why in certain projects, I add two sub-sections in the backstage. I display the backstage elements that we build only once. And then I display a second sub-section with recurring tasks or elements.
Use the template
Use with Paper by fiftythree
I release here this iteration of the service blueprint. Use it and adapt it to your needs
You might use the complete service blueprint with the « re-join » phase and the detailed backstage with the Paper iPad app. This thinker tool is well adapted to create visual canvases that are easily shareable. Furthermore, you can change the elements created within the app can with ease. That makes it possible to prototype several different service blueprints.