> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/user-scenarios.md).

# User Scenarios

It is easy to confuse **User Stories** with **User Scenarios** or **Use Cases** but the three are different.&#x20;

User Scenarios are narratives or stories that describe specific situations or contexts in which users interact with a product or service.&#x20;

These scenarios depict the user's goals, motivations, and actions within a given context, highlighting the steps they take to accomplish a task or solve a problem. User scenarios provide a realistic and contextualised view of how users may engage with a system, considering factors such as their environment, needs, and constraints.&#x20;

They help designers and stakeholders understand user behaviours, pain points, and opportunities for improvement. User scenarios aid in the design process by guiding decision-making, shaping user experiences, and ensuring that the product or service meets user needs effectively.&#x20;

By envisioning and designing for user scenarios, organisations can create more relevant and impactful solutions that align with users' real-world situations and expectations.

#### Further Reading

{% embed url="<https://medium.com/@smartgamma/user-scenarios-user-stories-use-cases-what-s-the-difference-75bf75d4bb60>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/ux-methods/discovery/user-scenarios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
