The deliberation loop

Say “deliberation” and most people picture a citizen assembly: a hundred strangers in a civic center working through a policy question over a weekend. That is where the word gets used most, and it has quietly narrowed the idea. Every strategy offsite is a deliberation. So is every Cynefin workshop, every Wardley mapping session, every honest retro. Each one is a group trying to think together well enough to decide something. They just don’t call it that, and because they don’t, the tools built to support them inherited an assumption nobody stopped to examine.

Here is the assumption. Watch what happens when a facilitator runs one of these methods across more people than fit in a room — thirty stakeholders, a dozen async threads, three time zones. Everyone contributes. A day later there is an artifact: a summary, a clustered board, a map with the components placed. It is competent. And when you put it in front of the group, the energy drains out of the room, because the picture was assembled for them rather than by them. A Wardley map that only the facilitator believes is a drawing. A Cynefin sort the group never got to contest is one person’s opinion with better formatting.

What is missing is not more input, and not a cleaner summary. It is a step in the middle that every good facilitator does by hand and almost no tool does at scale: show the group the picture that is forming, and let it push back before you call it settled. “That’s not what I meant.” “You’ve put that component in the wrong place.” “We spent an hour on the thing you dropped.” That pushback is not noise to be smoothed away. It is the deliberation. A conclusion nobody got to argue with is just a transcript that has been tidied.

So the shape worth building is a loop, not a pipeline. Five moves: express, map, reflect, validate, conclude. People say what they think. The system finds the themes, the tensions, and the places agreement is forming, continuously, across every parallel thread, instead of waiting for the end. Then come the two moves the pipeline drops — reflect that picture back, and let the group validate it or break it open. Only after that does a conclusion carry weight. The method the facilitator brought, whether it is Cynefin or Wardley or a stakeholder interview series, is the front end: the vocabulary the group thinks in. We have called Harmonica a runtime for facilitation — a system that takes a method and runs it for a group the way a computer runs software. The loop is what that runtime runs, and it stays the same no matter which method sits on top.

The map, and the five things you do to it

Everything in the loop happens to one shared object. Call it the map: the running picture of what the group thinks, where it is converging, and where it splits. Each of the five moves is a different operation on that map, and each one is a concrete piece of the product — some of it working today, some of it what we are building next.

Express is feeding the map. Today this is a one-to-one conversation with an AI facilitator that adapts to each person, follows up on what they actually said, and works in their own language — richer than a survey box because it can ask the second question. What we are adding is range: participants who bring their own questions into the flow, paste a link or a document mid-conversation, or meet a facilitator that adjusts to how much time and energy they showed up with. The better the expression, the more there is for the map to hold.

Map is building it and watching it move. As people talk, the facilitator keeps a live picture — the recurring themes, the tensions, the places agreement is forming — drawn from every parallel conversation at once, not stitched together at the end. That part runs today. The hard part we are building on top of it is knowing when the picture has stopped moving. “The conversation went quiet” is a trap: threads go quiet when people are bored, busy, or crowded out by two loud voices. What you actually want is saturation — the point where new participants stop adding new ground. When the thirtieth person only restates what the first ten already said, the map has settled, and that is a signal you can act on. It is not the same as silence, and confusing the two closes conversations that were only catching their breath.

Reflect is showing the map back and inviting a reaction. This is the move almost every tool skips, and the one we care most about getting right. When the map settles, the instinct is to generate the final deliverable; the better instinct is to hand it back with a single question — here is where you landed, what is missing, what did we get wrong? On a public topic this already happens: an opinion landscape shows a visitor where the group sits and lets them place themselves on it. For a facilitated session it is the reflection round we are building — the group comes back to react to its own map rather than receive a verdict.

Validate is letting the map be contested, and then watching what it does. Sometimes the group confirms it, and the agreement becomes something they worked through instead of something the tool asserted on their behalf. Sometimes one reply reopens the whole thing, because there was more underneath than the first pass caught. Both are the loop doing its job. For public topics this runs today — anyone can react to each statement, agree, disagree, or pass, and the landscape moves as they do. A shared picture that survives being challenged is worth something to the people who have to act on it; one that was never challenged is decoration, and everyone can feel the difference even when they cannot name it.

Conclude is reading the map’s evidence honestly. A summary is only trustworthy if you can see what sits under it, so each claim already carries the verbatim participant quotes that back it — attributed, but anonymous. What we are adding is honesty about how the group agreed: consensus worked through in a reflection round is not the same as consensus nobody tested, and the conclusion should say which is which. A settled map — reflected on, contested, and evidenced — is a conclusion a group will actually stand behind.

In motion, and at rest

The loop is what a group does in one sitting. But a group that meets more than once should not start from a blank page every time, and that points at a second view of the same material.

The loop is the in-motion view — express, map, reflect, validate, conclude, live. A project is the at-rest view: a place that holds what every session produced — the settled maps, the evidence, the sources people brought in — and hands it forward. The two meet at the map. In motion, the map is the thing saturating and being argued with. At rest, it is the accumulated knowledge a project carries between sessions. One session’s settled map becomes the next session’s starting ground.

Put plainly, the project is the loop’s memory. That is what lets a standing question — a quarterly retro, an ongoing consultation, a decision revisited as conditions change — compound instead of resetting. Run the loop once and you get a good conversation. Run it on a substrate that remembers, and you get an organization’s thinking made visible and improving over time: the same map, picked up where it was left, argued with again, a little truer each round.

This is the part that matters for anyone who facilitates for a living. Your methods are strong in a workshop of eight and they strain at forty — not because the method is wrong but because you cannot hold forty people’s thinking up in front of them at once. So you end up doing the collecting and the summarizing, the mechanical parts, and losing the reflecting, which was the part that was actually yours. Then you cap the group at what one person can hold and call it a principle of good facilitation, when it is really a limit of doing it by hand.

The loop is what removes that cap, and the memory is what makes the removal add up. It is infrastructure for structured group work: the layer that lets a Cynefin session or a change-management consultation run across two hundred people, come back owned by the people who made it, and still be there — accumulated, contestable, evidenced — when the group returns to it next quarter. Consultants have known how to do this in a room for decades. What’s new is that the room no longer has to be small, and it no longer has to forget.