> 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/ideation/use-cases.md). # Use Cases It is easy to confuse user stories with user scenarios or use cases but the three are different. See the article from Smart Gamma below to find out more about their differences. Use cases are descriptions that illustrate how a system, product, or service can be utilised to achieve specific goals or fulfil certain requirements. They outline the interactions between actors (users or systems) and the system itself, showcasing the intended functionality or behaviour. Use cases typically consist of a series of steps or actions, highlighting the sequence of events and the expected outcomes. They serve as a means to understand and communicate the intended usage of the system from the user's perspective. Use cases help identify system requirements, validate design decisions, and ensure that the system meets the needs and expectations of its users. They provide a clear and structured way to capture and document user interactions, guiding the development process and facilitating effective communication among stakeholders, designers, and developers. #### 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/ideation/use-cases.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.