> 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.md).

# Ideation

<figure><img src="/files/D3zUIqAeckb3VPrmPXpK" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Use the 'Ideation' menu to browse methods for the ideation phase
{% endhint %}

### Ideate

The 'Ideate' phase encourages creativity and brainstorming. Generate a wide range of ideas for solving the problems identified in the previous phases. Use techniques like mind mapping, storyboarding, or brainstorming sessions to stimulate innovation. This phase is all about exploring possibilities without constraints.

1. Brainstorm solutions: Generate a broad set of potential solutions, encouraging creative thinking.
2. Explore design concepts: Begin creating low-fidelity sketches or wireframes for visual direction.
3. Collaborate cross-functionally: Engage with product, engineering, and other stakeholders to refine ideas.
4. Evaluate feasibility: Ensure ideas are technically and financially viable.
5. Narrow down concepts: Select the most promising ideas that align with user needs and project goals.

{% embed url="<https://medium.com/design-bootcamp/44-workshop-activities-to-ideate-with-your-product-team-7e03f68ceef0>" %}

{% embed url="<https://www.youtube.com/watch?v=eqGTGFSDnRQ>" %}

{% embed url="<https://www.youtube.com/watch?v=k3q0Zry7H2o>" %}

### Prototype

Once you have a set of promising ideas, it's time to create prototypes. Prototypes are preliminary versions of your design that allow you to test and validate concepts. These can range from low-fidelity sketches to high-fidelity interactive mock-ups. Prototyping helps you visualise your ideas and gather feedback before committing to a final design.

1. Build interactive prototypes: Create clickable prototypes to simulate user interaction and flow.
2. Ensure UX consistency: Align design elements to brand guidelines and established UI patterns.
3. Incorporate feedback: Quickly iterate based on input from team members and stakeholders.
4. Prepare test scenarios: Define specific user tasks and flows to evaluate in user testing.
5. Identify technical dependencies: Outline requirements or adjustments needed for the engineering team.


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.