Scenario Mapping Template
Create a guide to what personas are doing, thinking, and feeling in different situations.
Trusted by 65M+ users and leading companies
About the Scenario Mapping Template
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 — as well as suggestions that come up as you go through this exercise.
Miro's scenario mapping template is divided into four quadrants to guide you through the exercise:
Steps (the structured framework of what is being done)
Doing (the practical application of the task)
Thinking (cognitive processes behind the task)
Feeling (emotional and subjective aspects)
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 scenario mapping when conducting user interviews or observation.
How do you use the scenario mapping template?
Scenario mapping is made simple with Miro's template. Follow these steps to use it effectively:
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.
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?
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.
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?
Map out your steps. Most people prefer to map each step from left to right and add comments, ideas, and suggestions below each step.
Repeat until the user has completed their task.
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?
Get started with this template right now.
T-Chart Template
Works best for:
Ideation, Operations, Strategic Planning
T-Charts can help you compare and contrast two different ideas, group information into different categories, and prove a change through “before” and “after” analysis. T-Charts are visual organizational tools that enable you to compare ideas, so you can evaluate pros and cons, facts and opinions, strengths and weaknesses, or big-picture views versus specific details. Designers and content creators can use T-Charts to turn possibilities into actionable ideas. T-Charts are useful for discussing differences and similarities with your team or clients and can help you to reach a decision together.
Lean Inception Workshop
Works best for:
Agile, Lean Methodology
The Lean Inception Workshop streamlines project kickoff by aligning teams on goals, scope, and priorities. It leverages Lean principles to eliminate waste and maximize value, guiding exercises to define user personas, map user journeys, and prioritize features. By fostering cross-functional collaboration and customer-centric thinking, this template accelerates project initiation and ensures alignment between stakeholders, empowering teams to deliver customer value faster.
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.
Lean Coffee Template
Works best for:
Agile Methodology, Product Management, Meetings
What makes a great meeting (other than donuts)? It’s appreciating everyone’s skills, resources, and time by making the very best use of them. That’s what the Lean Coffee approach is designed to do. Great for team brainstorms and retrospectives, Lean Coffee breaks the meeting into three basic stages: what to discuss, what’s being discussed, and what’s been discussed. This template makes it easy for you to collect sticky notes and to update the columns as you go from topic to topic.
Ansoff Matrix Template
Works best for:
Leadership, Operations, Strategic Planning
Keep growing. Keep scaling. Keep finding those new opportunities in new markets—and creative new ways to reach customers there. Sound like your approach? Then this template might be a great fit. An Ansoff Matrix (aka, a product or market expansion grid) is broken into four potential growth strategies: Market Penetration, Market Development, Product Development, and Diversification. When you go through each section with your team, you’ll get a clear view of your options going forward and the potential risks and rewards of each.
MoSCoW Matrix Template
Works best for:
Ideation, Operations, Prioritization
Keeping track of your priorities is a big challenge on big projects, especially when there are lots of deliverables. The MoSCoW method is designed to help you do it. This powerful technique is built on a matrix model divided into four segments: Must Have, Should Have, Could Have, and Won’t Have (which together give MoSCoW its name). Beyond helping you assess and track your priorities, this approach is also helpful for presenting business needs to an audience and collaborating on deliverables with a group of stakeholders.