> 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/what-if-scenarios.md). # What-If Scenarios "What-if scenarios" are hypothetical situations or scenarios that designers, researchers, or product teams use to explore potential outcomes and user interactions within a user experience (UX) context. These scenarios are often constructed to evaluate how users might interact with a product or service under various conditions or circumstances. For example, in the design of a mobile banking app, a what-if scenario might involve imagining how users would react if they were unable to access their account due to a system outage while traveling abroad. By considering such scenarios, designers can identify potential pain points, usability issues, or areas for improvement in the user experience and then address them proactively. This approach helps to create more robust and user-friendly designs that better meet the needs and expectations of users. What-if scenarios typically belong to the ideation phase of product design. During the ideation phase, designers generate and explore a wide range of ideas and concepts to address user needs and solve identified problems. What-if scenarios are used to brainstorm potential situations or challenges that users might encounter while interacting with the product or service being designed. These scenarios help designers to think creatively about different user contexts and to generate innovative solutions that can enhance the user experience. Once the ideation phase is complete, the generated ideas and concepts are usually refined and tested in the subsequent phases, such as prototyping and testing, to validate their effectiveness. #### 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/what-if-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.