So here we are at part two of creating a user journey map. Now we've got a goal, and we've got a framing. So I updated the goal. It says, What is it like for our user to maintain our product, or add on to it with the things that we offer? And this is the situation where maybe we we have support calls or questions or some interactions on social networks where we've we've got some feedback that this is something we need to investigate. So how do we investigate it where we put ourselves into the experience of our users?

That's what step two is about is let's understand the user. So who is the person in this situation? Here we have customizing Karla so this is a person with some behaviors. It is a placeholder persona. Ideally, we've based this off of prior research, we understand that this kind of person exists, or it's a placeholder that we're going to use this as an assumption to move forward and design something that we can then test the idea. So we have a complete enough idea to see how does this meet our audience.

But either way, here's this this, this person that's going to be going on the journey is customizing. customizing, Carla. So Karla is interested in digging deeper into this app wants to customize it and find ways to solve new problems or be more expressive and is ready to dig in. starts out before there was a time when she wasn't aware that it was possible that this SAP had extensions. But then one day a dialog pops up and says, basically, it's a little mini ad that says, hey, there's add ons available. That leaves Carla looking for where to get those add ons because maybe this didn't have a built in way to do that.

To jump right in. And with some effort, let's let's say Carla does find those add ons and sees like there's a there's an app extensions menu item. But then in the middle, is also discovering that the ones that she was hoping would be there in this app in this extensions marketplace. They aren't available. So thankfully, there was one on sale and she ends up picking that as a compromise. And then let's say there's nothing really there built in.

She would perhaps just eventually move on. So eventually she moves on to another app that supports the things she's interested in creating. This is the basic journey. This is one basic journey. So there could be more users. And that's going to be that's this will depend on the kind of the kind of experience you're analyzing, is it?

If it's the you're hosting the board gaming party, then are you are you inviting people have different ages and different backgrounds and interests? So how do you want to how do you want to deal with that with your party? Will that be about theming it and having some, some requirements ahead of time? Do you have a dress code? What have you I don't know. It's your party.

You know, so why do something that's like before they start How could you be before they started and chicken and egg and That? Well, there's a context that someone's always in before they know you before they've met your product or before they've seen your portfolio. And there's something in the before time, that brings them into the connection time. So then, however, you want to label that these labels and stages are all up to you as well. Fairly reusable ones that we have here before then start middle, complete and after. But really whatever makes sense for you as far as though that that progression of stages, but it's really a time series.

And so here we have a time series of steps for Karla, but then we could add more. And instead of adding another user, we're going to move on to the next step which is adding a wider perspective to the journey.