Why is this book interesting to you?

What I liked about this book is how it provides an easy way to explain those concepts to others in the organization, not necessarily with all the swears, sorry, Daniele 😁, but if you are trying to coach your team on adopting service design principles you can easily use some of the examples in the book to make your point and I bet they will land.

The book is written in plain, easy to read, and engaging language, making it easier to grasp what Daniele is trying to convey without all the jargon.

For who isn't this book for or what parts sucked?

The book is all in all great and an easy-read, but if you are trying to learn Service Design to be a service designer, this isn't really for you. So, in a nutshell, implementing these tips and tricks won't substitute for the knowledge and hands-on experience with real projects, but will help you probably ideate better, feel free to borrow/steal from other industries and make your customers feel better about your service.

I also found that some of the principles are very straight out practical and can be implemented tomorrow if you wished, and some were more of prompts that push you to dig deeper and have conversations about your own context and how you can change things accordingly. If you are looking for quick fixes, the latter principles won't be for you.

What other books would you recommend as companion to this one?

If you want to dig deeper on the same concepts or love practical principles that you can think about and implement more quickly, your next read should be Good Services; Designing Services that work.

Get in touch with Sarah