In terms of UX design, a scenario describes the context where the group of users represented by a Persona Document use the application in order to complete a task. It should be mainly focused on why the user opens the app and which kind of action the user develops. One Persona can use the application in different scenarios for different tasks.

It will be easy for the development team to understand why the users spend their time using the application. It is easier to visualize the frustrations and problems a user can find using an app when you know more about the reasons and circumstances surrounding the user. For example, one user can have a very different experience using a health app when booking an appointment for a routine checkup than when trying to find a doctor for a emergency assistance. In the second case, the user will be stressed and can run into problems with relatively easy tasks, which may not be an effort in a calm situation.

This kind of document allows us to illustrate the problem without jumping to the solution. The scenario will set a context for you to later explore possible solutions for it. Working with a higher-level perspective will give you a clearer view about the problem, and will let the team evaluate different possibilities to solve the user needs.

A scenario can represent a use case from a very superficial point of view, or it can analyze the user interaction in detail. When this scenario is very detailed, it can overlap information with the user journey. The main difference is the kind of information you try to transmit with each of them. The scenario document is more focused on the set of circumstances that lead the user to perform the actions, while the user journey focuses on the different steps and the feelings the user has on each interaction with the system.

Here are some possible scenarios:

• John is a 30-year-old guy who habitually buys on the internet, so he is familiar with pages such as Amazon or eBay. His motivation is to find a great product with a good price. The delivery time is not first in his preferences list, but the sooner the better. John always buys from his mobile, and before buying any product, he often finds reviews on YouTube.
• Margaret has never bought through the internet, but she knows that prices are better on some internet sites. She wants to find a good deal, but she only knows how to find things on the internet using Google. If she finds too many options, she will not be able to decide between all of them, so she prefers something easy and clear. She always uses a laptop to access the internet, and usually, she uses the internet at work while doing other things and without paying a lot of attention.

When you have a complete set of scenarios, the design team will be able to create a solution keeping in mind all that the different users need. One by one, all the specific needs can be checked in the system, and the team will be able to take confident decisions.

Usually, the scenarios are connected with Personas Documents, so it is easier to understand all the circumstances that are involved in the process. With the pair of Persona and Scenario, it is easier to imagine how that person will interact with the system, and the team will be able to find the limitations and difficulties that the user will encounter. Also, the team will be able to determinate the external elements that can impact the whole process and anticipate the possible solutions.