How Consent-Based Decision-Making Works
.svg)
- Consent-based decision-making moves a proposal forward as long as no one raises a reasoned objection, where consensus waits for everyone to agree.
- The range of tolerance is the key idea: a decision does not have to be everyone's first choice, only acceptable to all.
- The process runs in seven steps during a meeting, from appointing a facilitator to announcing the decision.
- A valid objection points to a concrete risk for the group's goals; a personal preference does not qualify.
- A table compares four decision modes: consent, consensus, majority vote, and a role deciding after seeking advice.
- The method has limits: high-stakes topics, urgency, oversized groups, and teams without defined roles.
What if you had a decision-making process where every voice is heard, objections are valued, and decisions are made swiftly? This is the essence of consent-based decision-making, a method at the heart of innovative organizational models like Sociocracy and Holacracy. As opposed to traditional consensus models, consent-based decision-making focuses on finding solutions that everyone can live with.
Consent-based decision-making is becoming increasingly popular in organizations aiming to foster inclusivity, efficiency, and agility. By addressing and incorporating objections rather than seeking full agreement, this approach ensures that all members feel heard and respected, leading to more robust and sustainable decisions.
In this article, we’ll explore the fundamentals of consent-based decision-making, and give you a step-by-step guide to implementing this process.
What is Consent-Based Decision-Making?
Definition
Consent-based decision-making is a structured approach where decisions move forward unless people have objections. This method emphasizes addressing and integrating objections to ensure decisions are "good enough for now" and "safe enough to try."
The method is also called consent-based governance or, more simply, decision by consent: the same process, inherited from sociocracy, in which everyone in the circle carries the same weight to stop a proposal that would put the organisation at risk.
Consent vs. Consensus
While both consent and consensus aim to involve all members in decision-making, they differ fundamentally:
- Consensus requires unanimous agreement, which can be time-consuming and may lead to decision standstill.
- Consent focuses on addressing objections rather than seeking full agreement, allowing decisions to move forward quickly if no significant objections are raised.
For example, in a team meeting using consensus, a single disagreement can halt progress until a full agreement is reached. However, a consent-based approach would ask if any team member has a strong objection and, if not, proceed with the decision while addressing minor concerns through amendments.
Consent is not the only way to settle a decision collectively, and choosing it means knowing what it does better than the alternatives. This table puts four decision modes side by side: what it takes to pass, what can block it, and where each one belongs.
| Decision mode | What it takes to pass | What blocks it | When to use it |
|---|---|---|---|
| Decision modeConsent | What it takes to passNo reasoned objection after a round asking for consent. | What blocks itAn objection pointing to a concrete risk for the group's goals. | When to use itDay-to-day decisions in a team or circle, when you need to move without steamrolling people's reservations. |
| Decision modeConsensus | What it takes to passExplicit agreement from everyone in the room. | What blocks itOne person's disagreement, even without an argument. | When to use itRare, founding decisions, when full buy-in matters more than speed. |
| Decision modeMajority vote | What it takes to passA majority of the votes cast. | What blocks itNothing: the minority is simply outvoted. | When to use itA choice between options that are already framed, when the stakes are low and time is short. |
| Decision modeA role decides, after advice | What it takes to passThe person holding the role decides, after consulting those the decision affects. | What blocks itNothing: the decision happens outside the meeting. | When to use itA domain clearly delegated to a role, or a situation that cannot wait for the next meeting. |
Range of Tolerance
To understand consent, it's essential to grasp the concept of "range of tolerance." This means making decisions that might not be everyone’s first choice but are acceptable enough to move forward. By focusing on what is acceptable rather than preferred, organizations avoid decision bottlenecks and maintain momentum.
For instance, a proposal to change meeting times might not suit everyone perfectly. However, if the new time falls within the acceptable range for all members, the decision can proceed even if it's not the ideal choice for everyone.
Want to know more about the range of tolerance? Have a look at this video 👇
How Does a Consent-Based Decision-Making Process Work?
Consent-based decision-making involves several structured steps. Here’s how this process typically works in a meeting:
.png)
1. Appointing a Facilitator and Secretary
The first step is to appoint a facilitator and a secretary for the meeting. The facilitator's role is to guide the process, keep the discussion on track, and ensure that everyone follows the agreed-upon steps. The secretary is responsible for documenting the proposal, any objections, and the final decision.
2. Presenting the Proposal
Proposals are then presented to the group one by one. Each proposal must be clear, concise, and aligned with the organization’s goals. Anyone in the group can present a proposal, and it should be thoroughly prepared to anticipate potential questions and objections.
3. Clarifying the proposal
Once the proposal is presented, the next step is to open the floor for clarifying questions. This round ensures that everyone fully understands the proposal before moving forward. Participants ask questions to clarify any points of confusion, but this is not the time to express opinions or objections.
Example: "Can you explain more about how this new meeting time will impact our team’s workflow?"
4. Reacting Briefly to the Proposal
After clarifying questions, a quick reaction round allows each participant to briefly share their initial thoughts on the proposal. These reactions should be concise and focused on their immediate response to the proposal.
Example: "I think this proposal could streamline our process, but I’m concerned about the impact on remote team members."
5. Asking for Consent
In this next step, the facilitator asks if anyone has any objection to the proposal. If no one raises objections, the proposal is adopted and you can move to step 7 directly. If there are objections, the process moves to step 6.
6. Dealing with Objections
If objections are raised, they must be qualified and addressed systematically. Valid objections highlight a potential harm or risk to the organization’s goals. If that’s not the case, then they don’t qualify as objections in the first place.
The most common confusion is about what counts as an objection. A personal preference, a vague worry or a plain "I don't feel good about it" do not qualify. Three questions settle it:
- Does the proposal stop the group from doing its work? If the discomfort is about one person's comfort rather than the circle's ability to meet its goals, it is not an objection.
- Does the risk come from this proposal? An objection describes a concrete effect of what is being proposed, not a pre-existing problem or a distant scenario.
- Can you try it and correct later? If the possible mistake would show up early enough and be fixable, the proposal is "safe enough to try" and the objection falls.
An objection that passes all three filters is good news: it reveals a blind spot in the proposal. That is why it gets processed as information that improves the decision, not as an obstacle to work around.
Here are the steps to deal with objections:
- Understand the objection: The objector explains their concern in detail.
- Qualify the objection: The group determines if the objection is reasoned and relevant, and if it fits the description highlighted above.
- Amend the proposal: If the objection is valid, the proposal is amended to address the concern. This might involve tweaking specific parts or adding new elements.
- Check for objections to the amendment: Once the proposal is amended, the facilitator asks if there are any new objections to the revised proposal. If no one objects, then the objection is resolved. Otherwise, the objection process restarts again.
Example: If a proposal to change meeting times conflicts with some members' schedules, an amendment might be to find a time that works for most and provide options for asynchronous participation for those who can’t attend live.
Note that if the amendments are substantial and create a fundamentally new proposal, it may be necessary to restart the whole consent-based decision-making process.
7. Announcing the Decision (and Celebrating!)
Once all objections are resolved, the final decision is announced. You can then celebrate this achievement and acknowledge everyone’s contributions to reinforce the collaborative spirit of the process.
Example Case
Now here’s a practical example to illustrate how consent-based decision-making works.
Let’s say your team is deciding on a new project management tool. A member proposes adopting Tool X. After the clarifying questions round, it’s clear that while Tool X has many benefits, its cost is quite high. During the quick reactions round, members express both support and concerns. An objection is raised about the budget impact, leading to a discussion. The proposal is amended to include a phased implementation plan to manage costs better. The amended proposal is then adopted after confirming no further objections.
Still unsure on how the process works? Watch this video to get further explanation:
The Limits of Consent-Based Decision-Making
Presenting consent as a universal decision mode is the surest way to get it rejected. Four situations put it under strain:
- Complex or high-stakes topics. A reorganisation, a change of business model or a multi-year plan will not be settled in a single round of objections. The process still helps, but it comes at the end, once the topic has been researched and the people concerned consulted.
- Urgency. When a decision has to land within the hour, gathering the circle is not realistic. Organisations that practise consent therefore define, explicitly, the domains where a single role decides alone and reports back afterwards.
- Groups that are too large. Beyond a dozen people, the reaction round drags and attention scatters. Narrowing the circle to the people the decision actually commits beats having everyone attend everything.
- Teams without defined roles. With no clear decision-making scope, every proposal reopens the question of who decides what. That is the job of the governance meeting, which sets roles and their domains before operational decisions start relying on them.
These limits do not disqualify the method, they map out where it works: consent shines on the everyday decisions of a team that knows what it is accountable for. For heavier decisions, it works best inside a collective intelligence framework that prepares the ground before the meeting.
How Can You Implement Consent-Based Decision-Making in Your Organization?
Implementing consent-based decision-making requires a combination of the right organizational model, tools, and support. Here’s how to get started:
The Right Organizational Model
To successfully adopt this process, your organization should embrace a model that supports decentralized decision-making and empowers individuals. For example, these two models offer a comprehensive framework for consent-based decision-making:
- Sociocracy: This model emphasizes circle-based governance where decisions are made by consent within each circle. It supports continuous feedback and adaptation.
- Holacracy: Known for its structured approach to self-management, Holacracy uses integrative decision-making, which is similar to consent-based decision-making, to address objections and improve proposals iteratively.
Depending on your organization’s needs, you can also opt for a more customized approach. It’s all up to you!
The Right Tool: Talkspirit
Using the right tool can significantly facilitate the implementation of consent-based decision-making.
Talkspirit, which has absorbed the Holaspirit feature set, is designed to support self-management practices like Sociocracy and Holacracy. It allows teams to make proposals, discuss them in meetings, and document decisions seamlessly. Moreover, it provides meeting templates that allow you to openly discuss tensions, and a dynamic chart to clearly visualize roles and responsibilities.
The Right Support
Adopting a new decision-making process can be challenging, so it’s important to have the right support. Coaches and consultants can help you conduct specific training and workshops for your team to understand the principles and practices of consent-based decision-making. So be sure to ask them for help!
At Talkspirit, we work with a network of coaches who specialize in implementing models such as Holacracy and Sociocracy. So don’t worry, you’re in the right hands 😉.
To Conclude
Implementing consent-based decision-making is the first step to creating a more inclusive, collaborative and agile workplace. By adopting the right organizational model, using self-management tools like Talkspirit, and seeking the right support, your organization can definitely benefit from this process!
When you eventually try it out, start implementing it on a smaller scale (for example, in one department only). This will allow you to gather feedback to refine the process before applying it to the rest of your organization.
PS: Want to know more about organizational models like Holacracy and Sociocracy, and how to implement them? Download our new white paper packed with expert insights and testimonials 👇
Access White Paper
In our white paper "The Ultimate Guide to Organizational Models", you'll get: a comprehensive overview of innovative organizational models (like Agile, Teal, Holacracy, Constitutional Management, and more), testimonials from pioneer organizations that have successfully adopted it, best practices for choosing, implementing and measuring the effectiveness of our model, as well as digital tools to facilitate the transition.
FAQ
A structured approach where a proposal moves forward as long as no one raises a reasoned objection. It does not look for enthusiastic agreement but for a decision that is « good enough for now » and « safe enough to try ». It comes from sociocracy and is also used in Holacracy.
Consensus requires unanimous agreement, which is time-consuming and can lead to deadlock. Consent addresses objections instead of seeking agreement: with no reasoned objection, the decision passes. Consensus asks « do you agree? », consent asks « do you see a reason not to try? ».
The idea that a decision does not have to be everyone's first choice, only acceptable enough to move forward. Focusing on what is acceptable rather than preferred is what keeps organisations out of decision bottlenecks.
One that points to a concrete risk the proposal would create for the group's goals. Three questions qualify it: does the proposal stop the group from doing its work, does the risk come from this proposal, and can you try it and correct later? A personal preference or a vague worry does not qualify.
In seven steps: appoint a facilitator and a secretary, present the proposal, ask clarifying questions, hold a short reaction round, ask for consent, deal with any objections, then announce the decision. The clarifying round is for understanding only, it is not the moment for opinions or objections.
It fits poorly with complex or high-stakes topics that need prior research, with urgent decisions, with groups of more than about a dozen people, and with teams whose roles are not yet defined. In those cases, prepare the topic beforehand, narrow the circle to the people concerned, or explicitly delegate the decision to a role.
