> 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/question-storming.md).

# Question Storming

Question storming is a creative technique used in product design to generate a wide range of questions related to a specific topic or problem. It is a brainstorming activity that encourages divergent thinking and helps to uncover new insights and perspectives.

1. **Choose a topic or problem:** Identify the area you want to explore through question storming.
2. **Set a timer:** Limit the brainstorming session to a specific amount of time to maintain focus and energy.
3. **Generate questions:** Encourage participants to ask as many questions as possible, without judgment or criticism. The goal is to generate a diverse range of questions that explore different angles and perspectives.
4. **Categorise questions:** After the brainstorming session, group the questions into related categories to identify common themes and areas of interest.

Question storming can be used at various stages of the design process, but it is particularly valuable during the discovery and ideation phases:

* **Discovery:** Question storming can help to uncover user needs, pain points, and opportunities for improvement. By asking a wide range of questions, designers can gain a deeper understanding of the problem they are trying to solve.
* **Ideation:** Question storming can stimulate creative thinking and generate new ideas for potential solutions. By asking questions that challenge assumptions and explore different possibilities, designers can develop innovative and effective product concepts.

While question storming is primarily used in the early stages of the design process, it can also be helpful during the testing phase to identify areas for improvement and gather feedback from users. By asking targeted questions, designers can gain insights into how users interact with their product and identify areas where the design may need to be refined.

#### Further Reading

{% embed url="<https://www.printmag.com/strategy-process/business-design-school-question-storming/>" %}

{% embed url="<https://medium.com/@jasmea/the-power-of-question-storming-7f2f19c4fceb>" %}

{% embed url="<https://samaquillano.kit.com/posts/business-design-school-006-question-storming>" %}

#### Further Viewing

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


---

# 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/question-storming.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.