TRENDING
Gain access to an ecosystem of thousands of product experts, colleagues and peers from around the world.
Complete the Pragmatic Data Maturity Assessment to see if you’re making the most of your company’s data. 
Determine your company’s strategy and be intentional in your design activities choices and recommendations. First, what are use scenarios?
Use scenarios are stories that walk through the typical situations where the user encounters the problem. Use scenarios—in conjunction with personas—provide powerful context, because they articulate the what, who, why and when.
What use scenarios don’t do is provide the “how.” It’s not the job of product management to define how to solve a problem. Instead, the goal is to provide critical context that will set the stage for a collaborative exploration of the how.
This context is critical because it drives innovation. With user scenarios, your team—designers, developers, analysts, product owners and testers—better understands who your users are, what problems they are trying to solve and help you to envision how you can help them.
What use scenarios don’t do is provide the “how.” It’s not the job of product management to define how to solve a problem.
Product managers take the lead when it comes to developing use scenarios. But they can involve stakeholders from many aspects of the business—designers and developers, data analysts, the executive team, sales and more.
Your external-facing internal stakeholders may have context you don’t, and it can be beneficial to capture that information.
You should remember that this work is never “finished.” It’s an ongoing task that needs to account for the evolution of both personas and problems. Product managers and other team members should examine personas, problem statements, use scenarios and problem frequency regularly to keep them relevant.
Building user personas is a prerequisite for writing use scenarios. User personas are a research-based archetype of potential users designed to help teams evaluate multiple solutions as well as create connection and empathy with users. Here’s where you can learn more about this part of the framework.
The use scenario takes one of your persona’s requirements and expands it into a real-life story by focusing on the environment where your persona uses your product or service and the frequency with which the scenario occurs.
A good use scenario is written so all of your stakeholders—even non-technical people—can understand it.
A use scenario doesn’t get deep into design or details. And it doesn’t mandate solutions. It outlines what your persona needs or wants in a relatable story. From there, your designers and developers can talk about the persona and the use scenario and brainstorm solutions.
User personas are a research-based archetype of potential users designed to help teams evaluate multiple solutions as well as create connection and empathy with users.
For example, if you are trying to understand the problems faced by full-time residential college students (let’s collectively call them Jessica) during the class registration process. You might reach out to partner universities and ask to observe students in the registration process. The students might be selected to participate in an interview where they verbalize their thinking through the process. Then a follow-up survey (quantitative research) released to hundreds of students might be built based on the observation of several students (qualitative research).
Together those two activities might reveal that students (Jessica) have too many irrelevant options and difficulty making sure courses align with their graduation requirements. Here we have two use scenarios a product manager could craft based on one user persona (Jessica).
You might have multiple use scenarios for the same product or service. For example, an online grocer may have use scenarios centered around three different personas:
These personas are all using the same product—online grocery delivery—but their descriptions, motivations, goals, etc., are all different.
Here’s an example of a use scenario for busy families.
Marital/family status: Married, two children
“I want to make smart food choices that my family will love. I also wish I had time to shop and plan meals.”
Friday is fridge cleaning day and once again, Sam notices that there are many ingredients and leftovers and that have spoiled from the week. She hates when food goes to waste because she knows that means they are not maximizing their food budget.
Sam looks at the calendar for the upcoming week and needs to decide what meals she’s going to make for her family. They all have their favorites, but she wants to introduce new, healthier options her family will enjoy. Meal planning sites are overwhelming, and it’s impossible to know what recipes are going to be winners, what will fail the taste test, and how she’s going to be able to buy all the ingredients she needs to make so many meals for the week.
Most importantly, none of the use scenarios outlined above mention the “how.” The solution-building should be done in collaboration with the development teams and engineers. So, product managers must resist the urge to be prescriptive and instead be descriptive. And, use scenarios are the tool that helps provide the much-needed context to other teams because the primary job of a product manager is to understand the market problems.
When you understand use scenarios, you understand your users. And you and your team can use that information to brainstorm ideas and develop new or improved products and services that delight your user. Learn more about crafting use scenarios that lead to better products and services and more satisfied customers in Pragmatic Institute’s Build and Design courses.
Fill out the form today and our sales team will help you schedule your private Pragmatic training today.
