The four-output deliberation kit
A deliberation build ships as a kit: the app, a timeboxed facilitation agenda, an outreach plan, and a printable flyer with a QR code. Programs without software are valid deliberation builds too.
What a deliberation build produces, so the software never arrives alone:
- The app: the tool that serves the stage(s) named, with ground rules on the page, plain language, a named host, and Export results.
- program/agenda.md: a timeboxed facilitation agenda with the tension and the starting prompts written in; small-group formats over open microphones.
- program/outreach.md: who invites whom, where flyers go, which doors get knocked, which languages, and the weekly rhythm for whoever keeps organizing between sessions.
- materials/flyer.html: a standalone printable flyer with inline styles and room for a QR code to the tool.
Bridge on-land and online in both directions: the flyer carries the block in; a printable summary carries the conversation back to the bulletin board. Say who was heard and who was not wherever results appear, and treat early rounds as growing the corpus, not settling the question.
-
Build prompt
A "what we heard" report page
Build prompt: after the listening, a report page in the Talk to the City pattern: themes with real quotes, minority views kept visible, a…
-
Build prompt
A listening wall for one neighborhood question
Build prompt: a Pol.is-style listening wall for one question, two weeks open, QR flyer on every corner, with a printable consensus summary…
-
Methodology
A Relational Tech Practice
-
Tool
CivicOS (BLOOM Project)
Infrastructure for public problem-solving: an Open Poll maps the opinion landscape, small-group community conversations work through…
-
Tool
Decidim
The free participation platform cities and cooperatives run themselves: proposals, assemblies, participatory budgeting, consultations.…
Contributed by Relational Tech Project, Deliberation Studio · relationaltechproject.org
See something to fix or add? Suggest an edit on GitHub — the commons lives in git too, and its history is the changelog.
deliberationkitfacilitationoutreachflyermethodology