Summary of the video

• If you don't see the value in a Service Blueprint, don't build one just for the sake of it.

• Only build a Service Blueprint if you have a specific reason for doing so, such as showing how different departments can work together to provide a good customer experience.

• The Service Blueprint is useful for bringing people together and smoothing transitions between departments.

Video transcript

This transcript was generated using Descript. So it might contain some creative mistakes.

 So we have a question from Jochem, who says, what am I, what I am missing out if I don't have a Service Blueprint? And the very straightforward answer to this is, if you have to ask this question, maybe nothing I would suggest never build a Service Blueprint just for building one. You always have to have a kind of a, an idea why you're doing it.

So just, if you don't see the value, just don't do it. Don't build a Service Blueprint. Please, because there is nothing worse than just building a service blueprint, a customer journey or anything else just for the sake of doing it. But there is one moment where I think it's very interesting to have a service blueprint is when you are in a situation where you feel, I need to show to the different departments that we should work together.

And that's where the Service Blueprint is really great because it shows how the backstage, how the different departments can work together in order to serve a nice customer experience. I think this is one of the key moments, but if you don't want to bring people together and smoothen the transitions between the departments, you don't need to build a Service Blueprint.

✨ Made with assistance of AI.

The transcript of the video was made using Descript, and the summary was made by using Notion.ai and the automated transcript with the prompt: "Make a summary with bullet points"