 This is a question from Marie and she said, what is the difference between a service blueprint and a customer journey map? And before we answer this one, people who wanna know more about this question, we answered this in our free customer journey mapping, essentials, masterclass, one hour long masterclass. I'll put the link for it in the notes of this video, but let's answer it right now, Daniel. You have a really clear explanation. Yeah, the customer journey map is a part of the service blueprint. So a service blueprint, the classical service blueprint is where you have the customer journey on the top. You have the customer perspective on the top and based on the starting point there is the customer's situations or activities going through an offer or a service or experience. Under that, you have the touch points. What is visible from our organization? What are the meeting points between our organization and the customer? So that's under it. And then if you go down even one more step, then you have what are we doing internally? What are employees doing? What kind of processes do we have? What kind of support systems do we have? That's the lowest part in the service blueprint. So the top, the customer situation is actually the customer journey map. And people used to put touch points in the customer journey map as well. So I would say that's kind of the customer journey map. Then when you add, what are we doing internally? What are behind the line of visibility? Then we start to talk about how do we, what are we doing as an organization to make all the things that the customer can see? Then it's the service blueprint. So the way I like to see it is, what are we doing to actually deliver the service? Yes. And anything that has to do with how you answer that question that is part of a service blueprint, right? Yes. I think that it sometimes the service blueprint or usually I would say, I mean, that's where you really create value because why is it, why should we know what the customer are doing? If we don't have any means to make anything about it? And I think that many organizations started to make customer journey maps. The first mistake they do is that they just list a lot of touch points and that's super stupid. But even if they work from the customer's perspective and they have the touch point and they see problems, if they don't work with what happens behind it, what do we do about it? Why are they doing customer journey maps in the first place at all? I mean, why even bother about it? Why bother to understand the customer's perspective if you don't understand the customer's perspective if you don't do anything about it? And that's one of my tricks is to talk to a customer who wants to do a journey map is to ask them how much budget do you have to actually implement the ideas that come out of it? How much time on budget? Because you don't want to create a customer journey map. You want to improve a process. You want to create a new service. That's the conversation you should be having but maybe we're sort of drifting off but if somebody asks you for a journey map, say that's great, but you're going to do something with the map. Yeah, I think that's very important. And I think it's good for the whole customer journey map in community to be sure that the customer journey maps that we are doing in this overall global movement that you really create value of it. Otherwise people will stop doing customer journey maps in a few years, I think. That was a good, it was a fun thing but this year we do some different kickoff. We have a new campus. Yeah. Yes. That's pretty clear on the difference between a service blueprint and a customer journey map.