> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/dialogue/how-can-we-bring-diverse-stakeholders-together-in-dialogue-and-deliberation/how-to-host-a-community-conversation.md).

# How to Host a Community Conversation

The [Interactivity Foundation](https://www.interactivityfoundation.org/) is a US-based non-profit organisation dedicated to fostering open, exploratory dialogue on shared public concerns. Their *How to Host a Community Conversation* resource provides a concise, practical set of three interlocking guides — covering organisation, facilitation, and participation — designed for anyone wanting to bring a diverse group of people together for a structured yet open-ended conversation.

The guides are grounded in the principle that community conversations should be genuinely exploratory rather than focused on reaching a predetermined conclusion. They aim to expand the range of perspectives under consideration, encourage collaborative problem-solving, and ensure that diverse voices are heard. The facilitation guide in particular offers useful practical advice: aiming for 6–10 participants per facilitator, establishing clear participation guidelines, crafting a discussion outline with introduction, content development, and conclusion phases, and maintaining an exploratory rather than directive tone throughout. Together the three guides cover what each role — organiser, facilitator, and participant — brings to a successful community conversation, making them a useful starting point for citizen observatory teams planning their first community dialogue event.

SOURCE: Interactivity Foundation (2024). *How to Host a Community Conversation*. <https://www.interactivityfoundation.org/how-to/how-to-host-a-community-conversation/>

**How to Host a Community Conversation — Access the Guides**

* [How to Organize an Exploratory Discussion (PDF)](https://cdn.interactivityfoundation.org/wp-content/uploads/2024/06/HOW-TO-Organize-an-Exploratory-Discussion_Public-Guide-Google-Docs.pdf)
* [How to Facilitate an Exploratory Discussion (PDF)](https://cdn.interactivityfoundation.org/wp-content/uploads/2024/06/HOW-TO-Facilitate-an-Exploratory-Discussion_Public-Guide-Google-Docs.pdf)
* [How to Participate in an Exploratory Discussion (PDF)](https://cdn.interactivityfoundation.org/wp-content/uploads/2024/06/HOW-TO-Participate-in-Exploratory-Discussion_Public-Guide-Google-Docs.pdf)
* [Overview page](https://www.interactivityfoundation.org/how-to/how-to-host-a-community-conversation/)


---

# 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://inclusivity.toolkit.citiobs.eu/dialogue/how-can-we-bring-diverse-stakeholders-together-in-dialogue-and-deliberation/how-to-host-a-community-conversation.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.
