Thanks for the amazing courses you are sharing, very inspiring and helpful. Will you please let me know what application you are using on this tutorial making the structure. Thanks.
Hi Jenny thank you for the great question! In the context of Design Sprints, we typically aim for the process of alignment (between team members) to start early… Before Day 1 even starts. Hence, there’s Preflight. During Preflight we encourage team members to “prime” their thinking by answering a few simple questions. One of these questions, is about the current state of their user’s experience. What actions does the user persona do during their stages of interaction with the product/service? They can simply write down points or cards under each stage of the experience. There’s no need to think of a flow to specific goals. Simply a list of actions, under each stages, in no strict particular order either. On Day 1 of the Design Sprint, we then run an activity called User Journey Map. This map typically looks into the future state, rather than current state. It’s the vision of what we want to achieve in the Sprint. The map is more structured and looks more like a diagram of a user flow rather than just a simple list of actions. This map also aims to get to the “User Goals” a bit more intentionally. And during this User Journey Map session, team members are also encouraged to narrow down and pick a focus within the overall experience, so their prototype and user interviews can be a lot more specific and objective (relative to the Sprint Goal). So, Experience Map during Preflight is high level, current state, broad and less structured. Whereas the User Journey Map during Day 1 is specific, future state, focused and goal-oriented. Hope that helps Jenny 🙏
@@relabstudios Thank you so much for taking time and answering my question! In 2 weeks I’m going to run my first design sprint. I have been binge watched your tutorial videos and it helps me a lot. I sent several your videos to our design manager and got good feedback from them: they are inspired by the way how you do it. Herzlichen Dank!🙏🏼🙏🏼
@@relabstudios I''m wondering how to approach this exercise where the current-state of the experience doesn't exist yet (i.e. we're working on something new)? Should we start with some user insights and then proceed to future-state user journey mapping?
Thank you very much for this video. So easy to understand 👌
We’re glad it helps Ene!
Love the explanation.. so simple.
Thank you for this tutorial!
Thank you for watching ✨🙏
Well explained, thank you.
Which tool you are using?
Thanks Jitendra. This one was done in MURAL
Thank you!
Thanks for watching Reihan!
please website/software did you use for your journey maps
Hi there, the online whiteboard used in this video is Mural www.mural.co
Another similar one worth trying is Miro miro.com
Hope this helps
Thanks for the amazing courses you are sharing, very inspiring and helpful. Will you please let me know what application you are using on this tutorial making the structure. Thanks.
Hi Daniel, thank you for watching! In this example, we used MURAL www.mural.co
It’s great for remote workshops and collaboration 👍
Sorry, have a stupid question: what is the difference between this map and the user experience map in your preflight artifact?
Hi Jenny thank you for the great question!
In the context of Design Sprints, we typically aim for the process of alignment (between team members) to start early… Before Day 1 even starts. Hence, there’s Preflight. During Preflight we encourage team members to “prime” their thinking by answering a few simple questions. One of these questions, is about the current state of their user’s experience. What actions does the user persona do during their stages of interaction with the product/service? They can simply write down points or cards under each stage of the experience. There’s no need to think of a flow to specific goals. Simply a list of actions, under each stages, in no strict particular order either.
On Day 1 of the Design Sprint, we then run an activity called User Journey Map. This map typically looks into the future state, rather than current state. It’s the vision of what we want to achieve in the Sprint. The map is more structured and looks more like a diagram of a user flow rather than just a simple list of actions. This map also aims to get to the “User Goals” a bit more intentionally. And during this User Journey Map session, team members are also encouraged to narrow down and pick a focus within the overall experience, so their prototype and user interviews can be a lot more specific and objective (relative to the Sprint Goal).
So, Experience Map during Preflight is high level, current state, broad and less structured. Whereas the User Journey Map during Day 1 is specific, future state, focused and goal-oriented.
Hope that helps Jenny 🙏
@@relabstudios Thank you so much for taking time and answering my question! In 2 weeks I’m going to run my first design sprint. I have been binge watched your tutorial videos and it helps me a lot. I sent several your videos to our design manager and got good feedback from them: they are inspired by the way how you do it. Herzlichen Dank!🙏🏼🙏🏼
That means the world to us Jenny! Thanks for sharing your story 😊
@@relabstudios I''m wondering how to approach this exercise where the current-state of the experience doesn't exist yet (i.e. we're working on something new)? Should we start with some user insights and then proceed to future-state user journey mapping?
what program are you using?
Hi Chris, we use MURAL (www.mural.co) in the example in this video.
Really appreciate your effort 👌
Glad you enjoyed this 🙏
Well explained user journey map
Thank you brother 🙏
Would you please this template with me?
This is not how to create user journey maps
Thank you for the video. I just feel you should know that you are cute too