Skip to content

Decision modes

Rhizome offers several decision modes to suit different situations and requirements. They fall into three categories.

Decision options

Each decision can be configured with options that apply across all modes: Gauge (non-binding preliminary vote), Experiment (binding decision with a built-in review deadline), and Feedback (comment thread after the decision is finalized).

Categories

Discussion-based

These modes center on dialogue. The decision develops through exchange, integration of objections, and collaborative refinement of the proposal.

  • Consent – No one has a serious objection
  • Consensus – Everyone actively agrees
  • Consultation – One person decides after gathering perspectives from relevant stakeholders

Vote-based

Participants express their preferences through voting. The decision emerges from the aggregation of individual preferences.

Other

These modes serve special roles in the decision-making process.

  • Meeting (planned) – Direct dialogue for decision-making, documented in Rhizome
  • Role-based decision – Autonomous decision from a defined role, without a vote

Overview

Mode Category Core principle Speed Commitment
Consent Discussion-based No serious objections Medium High
Consensus Discussion-based Active agreement from all Slow Very high
Consultation Discussion-based Decision after gathering expertise Medium High
Majority vote Vote-based Most votes wins Fast Medium
Distributing points Vote-based Weighting through point budget Fast Medium
Ranking Vote-based Prioritization through rankings Fast Medium
Resistance polling Vote-based Least resistance Fast Medium
Meeting (planned) Other Direct dialogue Variable Variable
Role-based decision Other Authority from role Very fast Medium–High

Choosing a mode

The choice of mode depends on several factors:

  • Impact – How consequential is the decision?
  • Urgency – How quickly does it need to be made?
  • Complexity – How many perspectives need to be considered?
  • Scope of involvement – Who is affected and to what degree?
  • Resources – How much time and energy is available?

The following decision tree provides a starting point:

graph TD
    Start[What decision needs to be made?]
    Start --> Urgent{Is it time-critical?}

    Urgent -->|Yes| Responsibility{Does responsibility<br/>lie with one person?}
    Responsibility -->|Yes| Individual["Role-based decision"]
    Responsibility -->|No| Majority[Majority vote]

    Urgent -->|No| Impact{Fundamental<br/>decision?}

    Impact -->|Yes| FullSupport{Does everyone need<br/>to fully support it?}
    FullSupport -->|Yes| Consensus[Consensus]
    FullSupport -->|No| Consent[Consent]

    Impact -->|No| Options{Multiple options<br/>to prioritize?}
    Options -->|Yes| Intensity{Is intensity of<br/>preferences important?}
    Intensity -->|Yes| Points[Distributing points]
    Intensity -->|No| Ranking[Ranking]

    Options -->|No| Complex{Does it require<br/>discussion?}
    Complex -->|Yes| Meeting["Meeting (planned)"]
    Complex -->|No| Expertise{Does one person have<br/>particular expertise?}
    Expertise -->|Yes| Consultation["Consultation"]
    Expertise -->|No| Default[Consent or<br/>majority vote]

Orientation

This decision tree is a starting point, not a rigid rule. The more familiar the team is with the available modes, the more intuitive the choice becomes.

Frequently asked questions

Can the mode be changed during an ongoing process?

Yes, but with care. Participants with the facilitation role can cancel a proposal and create a new one with a different mode. Previously formulated options are preserved, but the process restarts. It is therefore advisable to choose the appropriate mode from the start.

What if a mode does not work for the team?

Reflect as a team on which modes have worked in which situations. Decision modes are tools – not every tool suits every situation. Trying different modes can help identify the right approach.