> 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/co-creation-workshops.md).

# Co-Creation Workshops

{% hint style="info" %}
AKA Collaborative Design Workshops
{% endhint %}

Co-creation workshops are collaborative sessions where designers, stakeholders, and actual users come together to solve problems as a team.&#x20;

Instead of designers working in isolation and then asking for feedback later, this method invites everyone into the creative process from the very start. During these workshops, participants use hands-on activities like sketching or mapping to explore ideas and build solutions together.&#x20;

This approach ensures that the final product truly reflects the needs and behaviours of the people using it because they helped build it. By breaking down the barriers between the creators and the audience, you foster a sense of shared ownership and uncover unique insights that a single person might miss. It is a practical way to ensure your design decisions are grounded in real world experience while making sure everyone involved is on the same page.

#### Further Reading

{% embed url="<https://uxdesign.cc/when-to-workshop-c91de323c0e4>" %}

{% embed url="<https://medium.com/design-globant/co-creation-how-tos-e25696f56d6f>" %}

{% embed url="<https://www.designkit.org/methods/co-creation-session.html>" %}

{% embed url="<https://www.ux-republic.com/en/how-to-prepare-and-lead-your-co-creation-workshop/>" %}

{% embed url="<https://www.interaction-design.org/literature/topics/co-creation?srsltid=AfmBOooOxTxfjdyy8dKKDuCxxKCQi4AhNGst4xpmhssYGZKpQTzLcRXv>" %}

{% embed url="<https://innerview.co/glossaries/user-research/co-creation-workshop>" %}

#### Further Viewing

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


---

# 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/co-creation-workshops.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.
