> 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/worst-possible-idea.md).

# Worst Possible Idea

The "Worst Possible Idea" is a creative brainstorming technique used to break through mental blocks by intentionally searching for the most ridiculous, ineffective, or even disastrous solutions to a problem. Instead of the usual pressure to be brilliant or innovative, team members are encouraged to suggest ideas that are clearly wrong or impossible. This playful approach lowers the stakes and creates a relaxed environment where people feel comfortable sharing thoughts without the fear of being judged, which often leads to more honest and energetic collaboration.

By focusing on bad ideas, the team can more easily identify the exact opposite traits that would make a solution successful. For example, if the goal is to make a website more accessible, a "worst idea" might be to hide the navigation menu entirely or use invisible text. By examining why these ideas are terrible, the team can pinpoint the critical requirements for a good user experience, such as clear visibility and intuitive pathways. It is a way of defining what success looks like by first exploring the boundaries of failure.

This method is particularly effective for teams that are stuck in a rut or struggling with "blank page syndrome." It shifts the perspective from a search for perfection to a process of elimination and reversal. Once a list of terrible ideas is generated, the group can then work together to "flip" those bad traits into functional, creative solutions. This often uncovers unconventional and highly effective approaches that would have remained hidden during a more traditional, serious brainstorming session.

#### Further Reading

{% embed url="<https://www.interaction-design.org/literature/topics/worst-possible-idea>" %}


---

# 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/worst-possible-idea.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.
