> 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 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/ideation/design-excursions.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.
