 How do I draw a third customer journey map to bridge the as is and the to be map so Maybe I can give a little bit of context in this situation because I this is a question I got from Daniela through the through the mail recently and basically the situation is They're creating a customer journey Map of the current situation of the service. They're building mapping There are the the stages and they know that they will be expanding the journey in the future This is not the end journey. This is like minimal viable product or service journey And they also want to map them to be Journey like how would look or should it look in three to five years? And now the question comes if you have those two maps today and five years How do we bridge that gap? How do we create the? How do we make this reality? Should we create another map or what is the approach here? Yes, I have done it in several projects where We created an as is map and a to be map and then created evolution of steps in between so With several maps with one the minimal viable product very close to the as is and then Maybe in a more desired With a bit more resources in the future I I think that's a way to do it if you just look at it from a service designers perspective Creating a lot of maps when you look at it from a an operational from a business perspective It's super stupid in the first place to create as is and to be maps because then we have to keep looking at several maps We have to keep updating several maps. How do we relate to the as is when? Two months when we have been been going two months. The as is is not an as is like any more So This was one of the challenges when we started to create at castelans Five years ago to make it possible to create the same Everything in the same map. So we just have to update and relate to one map And this is what we see people are doing today that they create several lanes For if it's an as is so if it's to be if it's a minimal viable product if it's a desired situation Or if it's the the the ultimate solution You will never reach that I think If the question is should we do a third map between as is and to be the answer is yes But a better answer to this is stop doing as is and to be maps Make it all in the same map make it an operational map Yes, because what I we've done this we have done this and I saw it so clearly that when we put everything in the same map Okay, it would be a bigger map. It would be more complex But you would draw everybody's attention to one map and You could keep updating them that map I've seen that of course there are problems with that as well because it would be big But the problems are so much smaller than the problems with as he sent to be maps and bridge maps. So Put them in the same app Okay, now I can imagine that there is a desire for some people who want to show a situation like Like three years out is really It's really far out. Yeah, and adding that to to a Operational map a day-to-day map One it might I can imagine that if you want to Have conversations with the CEO or other stakeholders, you don't maybe don't want to show them the You're working the map you're working on you just want to show them the future vision or use that to guide development Okay showing showing managers a desired future to be situation. That's dangerous because managers See level people use it usually think that what's been said and thought is already done So it's It's the best thing is to show. Where are we today? Where do we want to be in the future and how are we going between a and b? Yeah, and that's the question here. I guess right. That's that's the bridge Yeah, we're talking about so how do you show? How do you show death? Yeah, and I think that the best thing is to keep it in In the same map and if you are not confident with putting up everything up front Just put it in in sub lanes in castelans and have the sub lanes for how do we solve this today? how will we solve it in the future and What are the middle steps? What is? possible to make What could we possibly do today? I See this is as the really the best practice on doing this because The minimal viable product is what could we what can we do with it? We have today in the future. We will have a different IT solution than we could do this But what can we do today? So having like three? Three parts at five years. What could we do now? How are we doing it today in sub lanes and just close them and don't you don't need to show that to the C-level people if they're not interested in details So basically adding some kind of road map milestones in The journey in the map. Yes. Yes. I think that's a That's a general Really good thing to do to looking at the journey map as a change plan and not I say as a As an image, right, right, right. Yeah, that's a like like a Shot of the Snapshot of the situation, right? Yeah