Civic tech and deliberation tools: choose a conversation, map or participation process

Start with the process, not the software

A two-person debate, a written argument map and a citywide consultation collect different kinds of input. Before choosing software, state who can participate, who makes the decision and what happens to contributions.

This is a category guide based on official public descriptions, not a procurement assessment or independent security audit. A product’s ability to collect views does not establish that a process is representative, accessible or legally authoritative.

Five categories worth separating

Sources: Computational Democracy: Polis · Decidim: participatory democracy software · CONSUL DEMOCRACY: participation platform · Kialo: structured written discussions · Debagle: one-device in-person sessions

Polis: understand patterns across statements

The Computational Democracy Project describes Polis as a system where people submit short statements and respond with agree, disagree or pass. Analysis of those responses can help people inspect patterns of opinion. It is a different activity from taking turns defending a motion.

For a real project, ask how participants were recruited, how statements were moderated and how conclusions will be used. A set of responses should not quietly become a claim that all residents agreed.

Sources: Computational Democracy: Polis

Decidim and CONSUL: configure a participation process

Decidim and CONSUL DEMOCRACY present infrastructure for citizen participation. Evaluate the specific configuration, operating organization and process rules rather than assuming every installation offers the same workflow.

A meaningful process makes clear whether a contribution is advice, a proposal, a discussion input or part of a formally authorized decision. Check language access, assistance for people without suitable devices, retention, moderation and the route for challenging an error.

Sources: Decidim: participatory democracy software · CONSUL DEMOCRACY: participation platform

Kialo and Debagle: reasons and human exchange

Kialo organizes written reasons into pro/con discussions. Debagle’s described flows focus on people exchanging spoken arguments, with AI review; its in-person mode also supports open questions and reflection. These can be useful practice activities before a larger process.

Do not treat a short debate’s winner as a public mandate. Two people’s common ground is their overlap, not a representative survey. If using a consumer conversation tool in an organization, check its actual privacy, access and governance requirements first.

Sources: Kialo: structured written discussions · Debagle: one-device in-person sessions · Debagle: privacy and media handling

A process-design checklist

• Purpose: What can this participation change?
• Authority: Who decides, and how will they respond?
• Access: Who might be excluded by language, time, disability or device requirements?
• Evidence: Can people inspect the information behind the question?
• Moderation: What rules apply and what appeal route exists?
• Data: What is collected, shared and retained?
• Reporting: How will disagreement and participation gaps remain visible?

A hypothetical sequence for a neighborhood issue

For a library-hours proposal, begin with listening sessions about unmet needs. Map the arguments and identify missing cost data. If an authorized consultation follows, publish its scope and recruitment approach. Report the evidence and differences before the decision.

A paired practice debate can prepare speakers to explain competing options. It should sit inside a larger, accountable process when the outcome affects people beyond the participants.