What are the best, or what are the deliverables of service design for a client? And here I will frustrate you. Because my answer is like the Swiss answer, which is it depends. The real answer is whatever this person needs to solve his problem. So the deliverable depends from each project and from the goal and the project proof.

So it's hard to say. If every time you do a project, you end up with a service blueprint that you give to people, you might have to ask yourself, why am I doing this? Does it really serve each client that I do that? There is often stuff that we do in the backstage that is important to us to understand that project, but that is maybe not an end deliverable.

So you might have the same tools that you use for you in the backstage to understand things, but that you might not give to to the client in the end, because maybe you think, oh giving the service blueprint in the end might overwhelm the baker that I'm working with, but it was important for me to understand the complexity of his service.

Good. And then another client might want the Service Blueprint as a deliverable. So deliverable really depends on the project that you are doing.

What's the deliverable of a Service Design project?

Is it the Service Blueprint? Is it the customer journey? Is it an empathy map?

Obviously I'm biased because I love to build things. For example, a Service Blueprint isn't so much a deliverable, but rather a step that brings you to a deliverable. But then you might ask Daniele what's a deliverable?

The deliverables are all the tiny changes that you make in a service. The tiny prototypes that you created and tested. The tiny things that you implemented in real life. Those are the deliverables.

And to get there, sometimes you need a Service Blueprint or another method.