How to start a collective intelligence circle

Choose a question small enough to change

A collective intelligence circle is our name for a small, time-bounded group that combines different perspectives, investigates a question, and tests a useful response. It is a proposed practice, not an accredited method or a promise of transformation.

Start with a question that affects people you can actually involve. “How should humanity coordinate?” is too large for a first experiment. “How can our shared workspace become easier for newcomers to use?” is a question a small group can investigate. Choose something reversible, with a clear owner who can authorize the pilot.

Invite people with different relevant experience, including those who use the service and those who maintain it. Make the time commitment, access needs, and purpose clear before they agree to participate.

Week one: build a shared picture

Ask each person to describe what they have observed before the group proposes solutions. Separate observations from interpretations. “Three newcomers asked where supplies were kept” is different from “newcomers do not pay attention.” Keep both uncertainty and disagreement visible.

Create a one-page brief with the question, known facts, missing information, constraints, and who is affected. Decide what must remain private. Assign a facilitator to keep the conversation useful and a note-taker to preserve the reasoning. Rotate those roles where practical.

End the first meeting by choosing what to investigate, not by forcing agreement on a solution.

Week two: compare explanations and options

Bring back the evidence. Perhaps the supplies are hard to locate because the labels are unclear. Perhaps the instructions assume prior knowledge. Perhaps people cannot access the room at the right time. Different explanations imply different changes.

Ask everyone to propose an option independently, then discuss the reasoning. Include the option of leaving things as they are, so the group has a real baseline. Identify what each option could improve, what it could make worse, and what would disprove its main assumption.

Select a pilot through the decision rule agreed at the start. Record objections and explain why the chosen option is worth testing despite them.

Week three: run one bounded experiment

For the workspace example, the pilot might be a clearly labeled supply area and a short welcome guide. Name who will create it, who checks its accuracy, and when it will be tried. Set a limit on time and cost. Tell participants how to report an issue.

Choose a simple measure before launch: can a first-time visitor find the supplies without help? Add a qualitative question: what still feels confusing or unwelcoming? A count and a conversation reveal different things.

Avoid turning the pilot into a performance of success. If the change does not help, that is useful information. Document it without blaming the people who surfaced the problem.

Week four: learn in public, within agreed boundaries

Compare what happened with what you expected. Ask who benefited, who was missed, and what new work the pilot created. Decide whether to keep, change, or end it. Assign ongoing responsibility if it continues.

Publish a short account containing the question, evidence, decision, result, and next step. Remove personal information that should not be public. Make the account useful to another group trying a similar experiment.

The circle succeeds when it produces clearer understanding and a responsible next action. It does not need to become a permanent organization. Ending a completed experiment well is part of good coordination.

A brief you can reuse

Bring the brief into a shared document or print it for your first meeting. Keep the process lighter than the problem it is meant to solve. You are practicing a basic capacity of a better future: people learning how to think and act together.