Here we are in the midst of the project, creating a user journey map, and part for adding a wider context by delving into asking questions and observations from at least three different points of view. We have your users, how might things be going well, or could be better. You have your business. What could be going well, or going better from from that perspective, and also, engineering or makers, artists, right, that that that perspective, too. So those three perspectives in that Venn diagram we explored earlier, business design and engineering, essentially. So from a business school perspective, maybe having a dialog pop up for this, for this user isn't the best way to go about it.

What if there were a message somewhere else in this whole system, how else could that happen? And so the business might say, we want to communicate better. We want to come up with New new methods of communicating. And now design representing representing that user audience can help with? Well, in what ways are what ways are harmonious or meet our user where they're at? And do they do they opt into a?

Is it notifications? Is it badging? Like when you add that little icon to the corner of an app that has a number that may go up or down? Maybe it's neither. But the designers can come up with a way that helps accomplish that goal and doesn't hurt the audience. So these may be more questions than answers.

You may not know exactly what to do, but you may know where to start exploring to investigate where to go next. from an engineering perspective, there may be costs associated from different types of messaging. And there may be the development of a new feature preferred, it might be low, but it's something. So that's something that the engineering perspective can can take note of. Sometimes ideas will come up. And then engineering can present that as a potential risk, where maybe badges or notifications or some other mechanism that's being talked about in the project isn't available in the current tools that were used to build this thing.

And that applies for physical products, digital products, and what have you, then engineering is, is here and involve to bring that context to light and say, Hey, oh, there's a risk here. What do we do about that? mapping is a collaborative tool. It's about trying to find a successful way forward. From the perspective of engineering can we build it is it supportable, and then finance and business have Is there a a healthy model in this that works for what we're trying to accomplish for our organization and then in design is, does this represent who we're trying to serve in our end audience? And are we meeting them where they are at?

And are we doing this in the ways that are healthy for them? So again, in this part four, we're adding that wider perspective, business design and engineering. And we're doing that as observations on each step along the way. It's not mandatory, maybe some observations fit in different places or not. It's about creating the space to bring these different perspectives together. And so this is what you would do to continue on making additional observations from each perspective.

You can be asking the same questions, what's going well, what could be better? Where do we want to go next and why? So, here we have a few more observations and questions based on the different parts of the journey for Carla, what she experienced, and then the perspective of business design and engineering. So we started out with maybe figuring out new ways to communicate and message and connect with the Karla early on. But then maybe there's other issues as well, like so as far as finding an extension, how do we make that more possible? How is it?

How can we make it easier to find? But then from a design perspective, are we using naming that connects Well, with the with the user, our labels for things? If they fit the vocabulary and expectations of Carla, that will work better than if they don't? Because it'll it's essentially like hiding something if it's not named in a way that that Carla would expect. So, from an engineering perspective, maybe is is there a speed problem with search, maybe there's a it's hard to find things because it's just really slow to do searching. Or there could be other technical issues as far as words not matching or whatnot.

That's a, you know, lots of potential ways to dig into that from an engineering perspective, from a, a later on in the journey or so the business could pose the idea of like, are we publishing enough expansions? How do we publish more? Let's fill up this marketplace, let's do something that makes sure that there's something there for everybody. So when you know, there wouldn't be a situation where Carla couldn't find what you wanted. And then from a design standpoint, we could be asking, Are we publishing the right extensions? Because maybe it's not about the quantity, maybe it's about the specificity and quality and meeting expectations differently.

So what we did with step four is with this goal in mind with this user in mind with this journey in mind, we take the three different perspectives of business design and engineering potentially more based on based on your needs. Are you representing in your map include them. Maybe there's way more users than just Carla. That makes sense. Because even for the example of hosting a board gaming gathering, you may have parents with kids, you may have people who've never played a board game and people who are bringing a stack of board games so high that they're making multiple trips to their vehicle. So all sorts of possibilities, even in the goal that sounds so simple on the surface, but then when we dig into it, there's a lot of possibility there and a lot of potential journeys to explore.

Coming up next is part five, learning and deciding based on what you've learned from the journey map.