Scenario Mapping Template
Create a guide to what personas are doing, thinking, and feeling in different situations.
About the scenario mapping template
What is scenario mapping?
Scenario mapping is the process of outlining all the steps a user will take to complete a task. It generally includes notes about what users are thinking and feeling at each step. It can also include comments or information you feel is important for each step, questions or assumptions you have, and good ideas or suggestions that come up as you go through this exercise.
When should you do scenario mapping?
Scenario mapping can be used both to outline the intended or ideal scenario (what should happen) as well as what currently happens. If you’re trying to outline the ideal scenario, user mapping should take place very early on in a project and can help inform user stories and the product backlog. If you’re just trying to get a better sense of what currently happens, you can do user mapping when conducting user interviews or observation.
How do you use the scenario mapping template?
Scenario mapping can be simple when you have a user scenario template and easy-to-follow steps. We have a pre-made template that you can use on Miro’s virtual collaboration platform to do this.
1. Start by explaining the purpose of the scenario mapping session. The goal of scenario mapping is to identify what your users will do, not how they will do it. You can sketch out the details later. Set these expectations up front.
2. Identify one of your primary user personas and a key task that they will accomplish. What do you want your user to do? What is their goal?
3. Contextualize the scenario. Make a note of who the persona is, what they’re doing, why they’re doing it, and how often. Remember, don’t get too bogged down in the details. But it’s a good idea to keep these elements in mind as you move forward.
4. Walk through each step your user might take. As a group, visualize the user’s pathway on your site. At each step, you’ll want to capture the following information: What does the user do? Are there any assumptions or question you need to resolve at this step? How can you make this step more user-friendly?
5. Map out your steps. Most people prefer to map each step from left to right and add comments, ideas, and suggestions below each step.
6. Repeat until the user has completed their task.
7. Gather feedback from stakeholders and potential users. Ask them to walk through each step and see if they make sense. Is something missing? Do they have any additional thoughts or suggestions?