Decision methods¶
Rhizome offers several methods for making decisions together. You don’t need to know them all to get started.
When creating a decision, the form asks you, step by step, what you already know – who is making the decision, how binding it is, and what it concerns – and suggests a suitable method based on this. The pages here explain what lies behind these methods, should you wish to find out more.
!!! Tip: "Method and procedure are two different things" The method specifies how a decision is reached – that is what this page is about. The procedure specifies how binding the result is: binding, indicative or experimental. Both are selected separately.
You do not select a third setting at all: [**Feedback**](../../reference/feedback.md), the comment thread after completion, is included as standard in every method – enabled for consultation and role-based decision, otherwise disabled, but can be enabled retrospectively.
The three categories¶
If you select All methods in the form, they will be sorted accordingly.
Discussion-based¶
Making a single option acceptable to everyone – it’s about addressing objections, not about votes.
Coordination-oriented¶
Finding the most popular options from any number of choices – each person makes their own assessment.
- majority vote – the option with the most votes wins
- Least resistance – the option with the least resistance wins
- Ranking – the proposals are ranked
- dot poll – a points budget is allocated
Role-based¶
One particular person makes decisions delegated – the group provides different insight.
- Consultation – decision based on advice
- Role-based – decision based on one’s role
At a glance¶
| Method | Category | Core principle | Suggestions |
|---|---|---|---|
| Consent | Discussion-based | No objection = accepted | exactly one |
| Consensus | Discussion-based | Everyone actively agrees | exactly one |
| majority vote | Voting-based | The option with the most votes wins | at least two |
| Resistance check | Voting-based | Least resistance wins | at least two |
| Ranking | Voting-based | Rank proposals | at least two |
| dot poll | Voting-based | Allocate points | at least two |
| Consultation | Role-based | Decision based on advice | any |
| Role-based | Role-based | Decision based on role | any |
The last column is the most common stumbling block: consent and consensus deal with exactly one proposal, whilst the voting modes require at least two. Rhizome points this out before you submit.
Frequently Asked Questions¶
Do I need to know the method beforehand?¶
No. Answer the questions on the form and accept the proposal – it’s based on the number of proposals you’ve made and is usually accurate. You can read more about it later.
Can I change the method whilst a process is running?¶
Not within a single decision. However, you can cancel it and create a new one – the proposals will be retained and can be carried over. Whether cancelled, unsuccessful or successful – you can also create a Remix of the decision by making a new decision based on the same or a modified set of proposals. You can adjust the deadline, the procedure and the mode for each instance.
Often, this isn’t necessary at all: within a single topic, several decisions can be made simultaneously. Instead of switching topics, simply rephrase the question slightly.
What if a method isn’t right for the team?¶
Decision-making methods are tools. Take a look back now and then to see which ones have worked well for you – and give the others a go before you write them off. The pulse check is a good way to do this: it doesn’t commit anyone.