Consensus¶
Consensus seeks a solution that all participants actively agree with. Unlike consent, it is not enough for objections to be absent. Consensus requires a genuinely shared decision.
How it works in Rhizome¶
All participants contribute their perspectives and discuss objections. The group refines the proposal until everyone agrees. This may require multiple rounds of discussion and revision.
Objections and vetos¶
Participants can click "No objection" or raise an objection. Objections must include a rationale — optionally with a proposed solution. Objections can be replied to, for example by the facilitation or the proposal's creators.
The person who raised an objection can edit it, mark it as resolved, or delete it independently.
In addition to objections, there are vetos. A veto blocks the process entirely: a decision cannot be completed successfully as long as a veto exists on the current version. The veto must either be withdrawn or resolved through a new version of the proposal. Unlike an objection, the facilitation cannot declare a decision valid while an active veto remains.
Versions¶
When the facilitation wants to integrate an objection, they can create a new version of the proposal via the three-dot menu on the proposal. The title, description, and deadline can be adjusted — for example when an objection was raised shortly before the deadline.
When a new version is created, all previous participations are reset. All participants are asked to respond again. This turns consensus into an iterative, versioned process.
Proposing alternatives¶
Since a consensus process always concerns a single proposal, it can happen that an objection cannot be resolved by adjusting the existing proposal. In this case, participants can propose an alternative. Rhizome then automatically initiates a resistance poll that compares both proposals. The facilitation can then continue the consensus process with the favored proposal.
Extended decision rules¶
Quorum¶
For consensus, the quorum defaults to All must participate, since consensus by nature requires a response from every participant. If this is not practical — for example, because a group member is on extended leave but is still formally part of the group — the quorum can be reduced to a specific number or percentage.
| Option | Description |
|---|---|
| All must participate (default) | Every member in the group must respond |
| Number | A specific number of participants must respond |
| Percentage | A defined share must respond — preset options are 50%, 66%, or a custom value |
| No quorum | The decision is valid regardless of how many participants respond |
This flexibility allows organizations to use consensus even when full participation is not guaranteed, while remaining transparent about the actual scope of agreement.
For a complete reference of all available rules, see Special rules.
Use cases¶
Use consensus for fundamental decisions that affect the entire team or the identity of your organization. The process takes more time than other modes, but it produces a high level of shared commitment to the outcome.