> 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. User Scenarios are narratives or stories that describe specific situations or contexts in which users interact with a product or service. 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. 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. 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="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.designreference.xyz/ux-methods/discovery/user-scenarios.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.