> 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/design-excursions.md). # Design Excursions Design excursions are a creative UX method used to break through mental blocks by looking for inspiration outside of your specific industry or problem space. During an excursion, a design team identifies the core essence of their challenge and then investigates how completely different fields handle that same concept. For instance, if you are designing a complex check-in process for a mobile app, you might study how a busy hospital triage unit or a high-end hotel concierge manages arrivals. By stepping away from the screen and observing these unrelated environments, you can uncover fresh metaphors and novel interaction patterns that you would never have found by looking at your competitors. This approach encourages lateral thinking and helps teams move past obvious solutions to find truly innovative ways to improve the user experience. --- # 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/design-excursions.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.