We have a lovely question from Sandra. Who asks, how do I manage the amount of detail on a blueprint? There are a few answers to that. The first one is, what do you want to achieve? And be clear on that. Is it to create a blueprint which will give an overview? Is it a service works, or is it a blueprint that will be needed to, for the implementation work?

And so it's very different, and I think the level of detail when you go into like deep implementation stuff, then you might have a lot of details, but when you just want to summarize your understanding of a service, you don't need that much details. Another answer to your question is basically to work with Progressive Summaries.

So what I usually do is I have on the top of the blueprint like an executive summary line where for each phase of the blueprint I will have a little bit of a summary line so that If a decision maker wants to read that blueprint, it just has to read like the five or six sentences which are on the top.

Then, I will do the same for the front stage and the back stage. Also have a little kind of executive summary for each moment of the front stage, have a little summary and exactly the same. for the backstage. And this allows you to have kind of this middle ground where you can give a lot of information, but at the same time, if people don't need that information, they know where they can just read a nice short summary.

So that's the answer of how do I manage the amount of detail in a Blueprint. And maybe, just to come as a like, last answer for that, and inspired by what we shared in another video, it's to decide how long should it take for people to understand your Blueprint. Define that at the start, is it 5 minutes, is it 30 seconds, is it 20 minutes?

And then, once you have defined that, give your blueprint to someone, and give them, and tell them, hey, now you have 5 minutes, please go through it and let me know what you understand, and if you were able to go through everything. And this is a good test to know that the amount of detail is workable in the amount of time that you want people to spend on your blueprint.

So in summary very simple use executive summaries, summarize. the front stage and the backstage at every moment and define how long it should take for people to understand your blueprint, test it out, and this will help you to have a level of detail that is more manageable for people.

 Hi there, in this little video I want to share with you a little idea about something for a problem. Someone asked me how can you share a service blueprint without overwhelming people? And there is an idea that I use, which is the idea of toggles, where you can show and hide a piece of a blueprint.

And so I'm showing here a little demo of how I would do something like that for a service blueprint inside of Notion. You have your service blueprints with the front stage, the backstage, and usually it would look like something like that. It's wow we have the story, we have the different stages, we have all the elements from the front stage and the backstage.

And when people come into something like that and they see that, they are like, oh, fuck, I'm so overwhelmed. So that's why in Notion, you have this little toggle system, which is quite nice. Because you can basically present by showing just, okay, guys, I'm going to share with you the executive summary and you can share, okay, this is what happens.

All good for you. Cool. Now let's focus on the front stage and then you can go in the front stage. Same for the backstage. So this is just a little demo of how you could still have a quite complex Service Blueprint, but then share it in a kind of very summarized way with these little toggles. Obviously here it's done in Notion, but you could do that in other various programs.

If you do it in an Excel sheet or something like that, you could use that. I make it like if you have a PDF, then maybe you just create various PDFs where you just show one part. But basically, I think making it in something like Notion is quite powerful because you just have a link, you share it with people, and then they can see what is important for them.

Another tip, obviously, is to break down maybe the front stage in various parts. For example, you could say I want just the touchpoints. And then you have one toggle to show all the touchpoints, and one toggle to show all the pain points. So it's quite flexible as a system, but the idea was in this video just to share with you that you can build a service blueprint in a way that makes it also easy to share it and to not be overwhelmed by it.

I hope that helps and thank you again for the people who reminded me this little trick so that I could share it with you. Bye!