In summary

 How do you sell service design? The strategy logic part when clients, customers don't realize it needs to happen before the implementation part of services. And here I would say Don't try to sell service design, you know, why should people know that you're doing service design? Often people don't care about your process.

So why mention a name that will make people ask a lot of questions? Instead, use the names that they already know. If they speak about Agile and service design is quite Agile, speak in that way. Oh, I'm doing something which is in a similar way to Agile. And then speak more about their end results, because that's what people really care about.

The way you're doing it, if they ask questions about it, you can obviously speak about them. We don't need to always say we are doing service design. And, you know, most people I work with on a daily basis don't know that I'm a big nerd in service design, because I don't speak about that with them, because it has no value for them.

But, uh, and that's, I think it's a big reminder, we don't need to share this kind of information if it's not needed. So don't try to sell it. Another tip is maybe give a trium horse. Uh, so just a little hint. There is a great book by Dan Hill that you can read about that, uh, and a lot of stuff. It's, it's one of the smartest books I have ever read, so go read that one.

But one of the ideas is the trium horse and the, you might know this, I, this idea from the train horse, uh, basically. There is, uh, in a very old war, there was, um, one part of the battle who shared a horse with, um, a big city and they said, Oh, cool. We won. They gave us a horse, uh, to show that they lost. Okay.

We're going to take it inside our city, but inside the horse were soldiers and then they could come out in the middle of the city and then get one. So here, the idea is find out what's one thing. The clients you're working for, the people you're working with, really would love to get. And pop inside that one thing, the strategic thing you really care about.

And people will say, we want the horse, and you will say, no worries. I'm going to give you the horse, but beside the horse, there is another part which is important also to you, uh, for strategic purposes.

And as I said, you can learn to sell services and there is a lot of resources, uh, on that topic out there. And, uh, there is one question that I all have already shared notes about, uh, that you can find on that link, uh, where, uh, I share courses. Uh, tips from other people on how to share, uh, to explain service design, to pitch it and to sell it.

Uh, so go check that out. There is a lot of stuff that already exists if you really want to, uh, sell service design. Now we're back to another topic, which is the service design projects. So, let's jump into that part. Question from Amin. How should I start? What's the first step to begin with, uh, when a service design project is waiting to be done?

Again, a wonderful question. Thanks, Amin, uh, for sharing it. I would say, first thing, ask questions. That's a, that's a, um, an answer I give a lot, but, uh, ask questions to understand the context, ask people why they are interested in doing this project, ask people, um, what their, what are their needs, ask employees and ask end users what they would like to have.

And also, Another question which is very important is try to find out who really has the power in the organization to make the change happen. Because if you're doing a little project and you never have access to the people who make the final decision, it's not gonna work that well. So that's a big one.

Uh, ask questions, try to understand the context. Once you do that, You'll know what you have to do and with who you have to work. And now we're back with another little break about a service design principle. And this is one that is a draft because it's part of the third book in the series. And it's one that has been co created with someone from the community called Daniel Turit.

And it's a tip that goes extremely well with this question, which is he recommends Help first those who you can impact the most. So, when you start a project, obviously, there is a lot of things you could do, and a lot of people you could help in your organization. And, here, I think that's a very smart thing, is reduce the scope by thinking Who are the people who can benefit the most of the little time we have?

And if we work with these people, they get excited, then we can show to the rest of the team, Hey, it worked. Uh, we invested with just these people and it worked. And then you can do another project, uh, and then grow, uh, your, um, initiatives to, uh, impact even more people. But, you know, be focused, start small, start with the people you can impact.

The most.