Close with decisions, owners and a record

Jo reads the decision from what is written, not from memory and not in a paraphrase: "Items 2, 3, 5 and 8, in that order." Reading from the wall means the words being agreed are the words that will be recorded. Then Jo names the rule: "That is a decision by consent; the objections raised on item 5 were resolved by the amendment written during the consent round." Naming the rule tells everyone why this is a decision and not a sense of the room, and it ties back to the contract from session 1, where the rule was said aloud at 15:00.

Who reads matters. Session 4 modelled handing the close to the person who already spoke most: across the 40 real AMI meetings, the mean Gini of airtime rose from 0.198 to 0.236 on that model, and the summary arrived in the dominant voice. The facilitator reads the close from the wall because the facilitator has no stake in how it sounds.

"Any objections?" asked to a tired room at 16:21 produces silence, and Kaner's index carries a line worth remembering: silence is not an agreement. A check that works asks each person briefly, in a round, or uses a scale. Kaner's guide indexes a gradients of agreement scale (p.338) that lets people say how much they support a proposal, from wholehearted support through reservations to a block, instead of a yes or no; the exact wording of its points is in the book and not reproduced here.

The scale earns its place at the close because it reveals the person who will comply in the room and resist outside it. Someone at "I have serious reservations but will not block" is someone the owner of that item should talk to on Monday.

An owner is a person who said yes, out loud, before leaving. Assigning work to someone who is not present, or to a team, produces an action nobody feels. Jo asks for each item: "Who will own this?" and waits for a name, then asks that person: "What is the first step, and by when?" The date is a calendar date, not "next sprint", and the first step is small enough that the owner knows what they will do on Monday morning.

At Larkfield the owners come from both teams on purpose: item 2 to Ravi of Platform, item 5 to Mara of Growth. That split is a content decision the group makes; Jo only asks the question. It is also the practical form of shared responsibility: each team now owns part of the roadmap the other team wanted.

Once actions leave the room with owners and dates, following them through a programme, status reporting and escalation is project-management work, taught in AI Project Management, Meetings to actions. The facilitator's job ends at a clean handover: the record goes to whoever tracks the work, and the facilitator does not quietly become the project manager.

In: the decision in the words read from the wall; the rule and who took part; every objection raised and how it was resolved; parked items with where they will be handled; each action with owner, date and first step; any reservations people chose to record; and the review date. Out: who said what in the debate. The record is of the decision and its reasoning, not a transcript, and a record that quotes the argument restarts it.

Objections and their resolution are the most valuable lines months later. When someone asks "why did we drop item 6?", the answer is in the record, in the group's own reasoning, and nobody has to reconstruct it from memory.

Sociocracy 3.0's consent pattern lets a proposal go ahead when it is good enough for now and safe enough to try until the next review. That bargain only holds if the next review happens. Without a date in the record, "safe to try" quietly becomes permanent, and people who withheld an objection because the decision was reversible discover it was not. Writing the review date into the record, with an owner for calling the review, is what makes it reasonable to ask a group for consent rather than unanimity.