 How can you be sure that all stakeholders are involved slash covered in a map? What if I'm missing something and there's a question by Jean? Right. Yeah, and of course you will be missing stakeholders. There's no alternatives to that. I mean, in all projects I've been doing, we have missed stakeholders. The important thing is here to share what you are doing early. I mean, first you get a good overview of what you are doing, you get a good structure, but then start sharing. Yeah, sharing what are we going to share? Sharing the maps. I mean, for instance, in Castelans it's free to share what you are doing in Castelans. And we see that people that share very early in the project to just share viewing, that people could go into Castelans and view the maps that are starting to develop there. And then when you do that, you could ask people around you, what stakeholders have I missed? Are all the stakeholders here, can they find themselves in this map that we are developing? So, it's not a solo work, it's really a team effort working with customer journeys and customer experience. So, share it early, ask people, send out questions, what stakeholders have I missed? Do you feel that I've missed you? I'm really sorry, how could we solve it? Let people tell you instead of putting on yourself that you have to know, because you don't know. And the thing is, when you don't know, you will miss out people that won't tell you, they would just be very angry, and they will make it hard for you in the future. So, by inviting people early on, letting them have a look on what you are doing, sharing the map with them, to just log in, take a look, what do you think of this, have you missed out on the stakeholders? That's the way to go forward. Not guessing, and making it a shared responsibility, and involving people, that's basically the answer, right? Yeah, someone that was invited can't be angry on they were not invited. And sometimes you just also have to push them a little bit to participate. And it's easier to do in the early stages, when it's still more or less a blank or an open map, rather than showing them something that's completely done, where they feel that they have no more influence, or that they are too late. Don't give people the feeling that they are too late, right? That's a really good reason as well to just start sharing. I mean, I've been in so many situations where people, they like what's been done, but they work against it, and they don't want it to be implemented just because they weren't invited. It's not about the stuff, it's just about the process. They were not in the room. And that's again, I think we talk a lot about in the course, that journey mapping is not just about following the right steps to create a map, it's not just about the structure of the map, it's not just about the detail level, that those are things that are super important, but it's much more about the environment and context you create for doing journey mapping. And this is part of it, like how do you deal with stakeholders? That's what makes a successful journey mapping project. I was originally trained as an industrial designer, so I was trained to fill the world with more toasters. And industrial designers, it's just like architecture, it's not about good form or good design. That's not the toasters that you see in the store, it's the people that were really good at handling people internally. Handling engineers, leaders, handling politics, it's their toasters that you see. It's their cars that you see on the street. It's not the best designers cars you see. It's people who are able to make it a reality. Yeah, able to gather people around them, around this new design or new solution, and handling people, politics.