Scenario Map

5 min readSep 21, 2022

Understand the breadth of the product by documenting all the possible use cases that a user might encounter while using it.

The scenario map is a comprehensive collection of use cases that a user might encounter while using a product. A scenario is a way, feature, or touchpoint that helps in accomplishing a goal of a major task in the journey. In the scenario map, you should focus on users and their tasks rather than on the product’s structure. As a result, you will know what is the breadth of the product you should focus on to serve the needs of the user.

Creating a scenario map for a product/application is a collaborative session between designers, SME’s, Project managers, etc. Where all of them will be discussing what are different types of scenarios, users will go through the product.

Free & Discounted Udemy Courses — Explore Now

There are five steps to be followed to create a scenario map.

Step 1: Identify all the users

Identify all the users who are involved in the product. By the time you start the scenario map, you should have a clear understanding of all the users involved along with their key tasks.

For example, the users considered in Restaurant Management Application are Manager, Chef, Receptionist, Customer, Waiter, Accountant, etc.

Step 2: Identify major tasks/concepts in the journey

Once you understand the user’s role, now identify what are the key tasks/concepts in their journey.

For example, in Restaurant Management, for customers, the major tasks/concepts can be Inquiring about a restaurant, Booking a table, Getting into a restaurant, Ordering food, Paying the bill.

Document the major tasks in columns like a journey by following in a similar way to the above image

Step 3: Define scenarios for each major task/concept

A scenario is a way that a user can accomplish a specific need. Various digital features or offline touchpoints might be involved in accomplishing this need. For each major task/concept above, define scenarios that users will be going through or the ones which help in completing the task/concept.

For example: In a major task like booking a table, there will be scenarios that are part of it like

“User wants to book a table for a specific time today through the app”
“User wants to book multiple tables for his birthday party which is after 10 days”
“User wants to book a table which has more privacy, from the app itself”.

The scenarios should be identified by thinking around different situations users might go through and different needs that users might have to accomplish the major task.

And a scenario can be achieved in multiple ways, so try to frame alternate scenarios too…. So that you could explore all the ways and understand which of them should be part of your product.

For example: “User wants to book a table for a specific time today through the app” can be achieved in different ways…. “User wants to book a table for a specific time by calling the restaurant manager” “User wants to book a table in this restaurant from other dine-out applications”.

List down the scenarios in the column for each major task

Step 4: Prioritize the scenarios

After identifying all possible major tasks/concepts and their scenarios in the scenario mapping session, prioritize them by discussing them with stakeholders/participants based on the goal of the project or by doing the voting. It helps in deciding which should be part of the product immediately and which can be backlogged for the future.

Step 5: Create consolidated scenarios

After writing all possible scenarios for all the major tasks/concepts, you can also create a consolidated scenario which is a meaningful combination of scenarios from tasks/concepts. Every scenario should be

Realistic
Relevant
Concise
Meaningful
Anchor to the needs/goals

For example: “Alex is giving a birthday party to his friends today, so he wants to reserve multiple tables in the Novotel restaurant and also specify the buffet menu that should be provided”.

In the above scenario, Alex is the user, birthday party to her friends is the context and reserve a table and specifying menu are the actions which come into the category of different major tasks/concepts like booking a table and ordering food. You can use these scenarios to make workflows.

Example

Below is a feature level scenario map done by project managers to understand which user story can be done in which release

Tips / Best Practices

Explain what are considered major tasks and scenarios to the involved participants with appropriate examples.
Ensure that every scenario includes user, context, and action
Arrange the major tasks/concepts as a user journey in the product from start to the end.
Identify MVP scenarios by voting and by considering the need, effort, and impact.
Use the consolidated scenarios as workflows scenarios.

Checklist

Identify all the users involved in the product.
Identify the major tasks for each user based on the user’s journey from start to end in the product.
Write down all possible scenarios under each experience.
Highlight the scenarios which are included in the scope.
Check for consolidated scenarios.
Ensure user, context and action are mentioned in every scenario.

Quick Question

From the below list which needs to be thought through while creating a Scenario map
a. Users
b. Scenarios
c. UI components
d. High level tasks/concepts
e. Workflows

Leave your answer in the comments section below!