What is it?

Consent-based decision-making is a structured process where a group works through a proposal using rounds of clarifying questions, reactions, and a final consent round. Rather than asking "does everyone agree?" it asks "does anyone have a reasoned objection?" A proposal passes when no one in the group believes it will cause harm or prevent the group from achieving its goals. The key test is simple: "Is this good enough for now, safe enough to try?" This shifts the group away from seeking a perfect solution and toward making progress with proposals that can be revisited and improved over time.

Also Known As

• Sociocratic Consent
• Consent Process
• Consent Decision-Making
• Dynamic Governance (when used as part of a broader sociocratic system)

When to Use It

• When a team needs to make policy decisions, allocate resources, or agree on ways of working
• When you want every voice heard without getting stuck chasing full agreement
• When the group needs to move faster than consensus allows but with more buy-in than a top-down call
• When decisions can be revisited and adjusted later (most operational and strategic decisions)
• When there is a clear proposal on the table, or the group can generate one
• When psychological safety exists or is being actively built, and people feel able to raise concerns
• When the group shares a common aim or purpose that objections can be tested against

When NOT to Use It

• When the decision is urgent and there is no time for rounds (use a delegated decision instead)
• When the group has no shared purpose or goal to anchor objections against
• When the decision is irreversible and high-stakes with no opportunity to revisit (consent works best when proposals can be adjusted over time)
• When trust is so low that people will use objections as a weapon to block everything
• When only one person has the authority or accountability to make the call (forcing consent here undermines both the process and the decision-maker)
• When the group has not been introduced to the distinction between consent and consensus, as they will likely default to consensus behaviours

Consent-based decision-making was developed by Gerard Endenburg, a Dutch electrical engineer, in the 1970s as part of the Sociocratic Circle Organisation Method. Endenburg drew on his experience at a school run by Kees Boeke and Betty Cadbury, which used participatory decision-making, and combined this with principles from cybernetics and systems theory. He applied the method in his own engineering company, Endenburg Electrotechniek, refining it over a decade of real-world use. The approach has since influenced Holacracy, Sociocracy 3.0, and a growing number of organisations worldwide.

What You Need

Group size: 4-20 people (works best with 5-12; above 12, rounds take longer and you may need to be stricter on timing)

Time required:

• 20-60 minutes per proposal depending on complexity.
• Simple proposals can clear in 15-20 minutes.
• Complex or contested proposals may take 45-60 minutes.
• Allow extra time if the group is new to the process.

Space:

• Seating arranged in a circle or U-shape so everyone can see each other
• A wall or flip chart visible to all for writing the proposal and tracking amendments

Materials:

• The proposal written out in advance (on a flip chart, whiteboard, or projected screen)
• Sticky notes or cards for participants to jot down initial reactions
• Markers
• A timer
• A notebook or laptop for the recorder to capture objections and amendments
• A printed one-page summary of the process for groups new to consent

The Process

Setup

1. Write the proposal clearly and post it where everyone can see it. If possible, share it with the group in advance so people arrive having thought about it.
2. Arrange seating in a circle. Consent works in rounds, and people need to see each other.
3. Brief the group on two key roles: the Facilitator (guides the rounds, keeps time, tests objections) and the Recorder (captures the proposal, objections, and amendments as they evolve).
4. If the group is new to consent, spend 5 minutes explaining the core principle: "We are not looking for agreement. We are looking for the absence of reasoned objections. The question is not 'do you love this?' but 'can you work with this?'"
5. Clarify the shared aim or purpose the group is working toward. Objections must be grounded in this aim, not personal preference.

Step 1: Present the Proposal

Time: 3-5 minutes

Purpose: Make sure everyone understands what is being proposed before reacting to it.

1. The proposal owner reads the proposal aloud. Keep it brief and specific.
2. The facilitator checks: "Is the proposal clear as written? We are not discussing it yet, just making sure we all understand what is on the table."
3. If the proposal is vague, ask the owner to tighten it up before proceeding. A fuzzy proposal will produce fuzzy objections.

Watch for: People jumping straight into opinions. Redirect firmly: "We will get to reactions in a moment. Right now, we are just making sure we understand the proposal."

Step 2: Clarifying Questions

Time: 5-10 minutes

Purpose: Fill in information gaps so everyone is working from the same understanding.

1. Go round the circle. Each person may ask one clarifying question or say "no question."
2. Questions must be genuine requests for information, not opinions in disguise. "Have you considered the budget impact?" is a reaction dressed as a question. "What is the estimated budget impact?" is a clarifying question.
3. The proposal owner answers each question briefly. If they don't know the answer, they say so.
4. Do a second round if needed, but keep it tight.

Watch for: The "question that is really a statement." When someone says "Don't you think this will cause problems with...?" gently redirect: "That sounds like it might be a reaction. Can you save it for the next round?"

Step 3: Quick Reactions

Time: 5-10 minutes

Purpose: Give everyone a chance to share their initial response to the proposal before the formal consent round.

1. Go round the circle again. Each person shares a brief reaction: what they like, what concerns them, what they would change. One to two sentences maximum.
2. The facilitator says: "This is your chance to share your gut response. Keep it short. We are gathering perspectives, not debating."
3. The recorder notes any themes or recurring concerns.
4. The proposal owner listens without responding. They may choose to amend the proposal based on what they hear before moving to the consent round.

Watch for: One person dominating. If reactions start turning into speeches, interrupt kindly: "Thank you. Let's hear from everyone and then we can come back to this."

Step 4: Amend (Optional)

Time: 3-5 minutes

Purpose: Allow the proposal owner to improve the proposal based on what they have heard.

1. The proposal owner may adjust the proposal in response to clarifying questions and reactions. They are not required to.
2. If they amend, read the updated proposal aloud and check: "Is the amended proposal clear?"
3. Post the updated version visibly.

Watch for: The proposal owner trying to please everyone. Remind them: "You do not need to address every reaction. Focus on anything that might prevent someone from consenting."

Step 5: Consent Round

Time: 5-15 minutes

Purpose: Test whether any reasoned, paramount objections exist.

1. The facilitator says: "I am going to go round the circle one more time. For each person, I will ask: do you have any objection to this proposal? An objection means you believe this proposal will harm our ability to achieve our shared aim, or will prevent you from fulfilling your role. If you have no objection, simply say 'no objection' or 'I consent.'"
2. Go round the circle. Each person states one of three things:
   • "No objection" or "I consent" (the proposal stands for them)
   • "I have a concern but not an objection" (they are not fully enthusiastic but can live with it)
   • "I have an objection" (they believe the proposal will cause harm relative to the shared aim)
3. If there are no objections, the proposal passes. Move to closing.
4. If there is an objection, do not debate it. Instead, move to Step 6.

Watch for:

• People confusing "I don't love it" with "I have an objection." The facilitator's job is to test this: "Is this a preference, or do you believe this proposal will prevent us from achieving our aim?"
• People consenting when they actually have an objection but feel social pressure. Watch body language. If someone looks uncomfortable after saying "no objection," you might say: "I want to make sure everyone is genuinely comfortable. Is there anything unsaid?"

Step 6: Integrate Objections

Time: 5-15 minutes per objection

Purpose: Improve the proposal so the objection is resolved without losing the proposal's intent.

1. Ask the objector to state their objection clearly: "What specifically about this proposal do you believe will harm our ability to achieve our aim?"
2. The facilitator tests the objection: "If we did nothing, would the situation be worse than adopting this proposal?" This helps distinguish between a genuine objection and a preference for the status quo.
3. Invite the objector to suggest an amendment: "What would need to change for you to consent?"
4. Open it to the group: "Does anyone else have an idea for how we might address this objection?"
5. When an amendment is proposed, check with the objector first, then do a quick consent round on the amended proposal.
6. Repeat if new objections emerge. If the group gets stuck, consider tabling the proposal for further work or delegating it to a smaller group.

Watch for: The group trying to achieve consensus by wordsmithing endlessly. If integration is taking too long, the facilitator can say: "We seem to be moving toward perfecting rather than progressing. Can we find something that is good enough for now and revisit it in [timeframe]?"

Closing

Time: 3-5 minutes

1. Read the final proposal aloud as it stands.
2. Confirm: "This proposal has been consented to by the group. It takes effect from [date/now]."
3. Record the decision, including any conditions, review dates, or amendments.
4. Ask: "When will we review this decision?" Set a specific date. Consent works because decisions can be revisited.
5. Thank the group for their discipline in following the process.

Facilitator Guidance

What Makes This Work

Consent-based decision-making works because it separates personal preference from genuine concern. By anchoring objections to a shared aim, it stops the group from getting stuck on individual tastes and focuses energy on "will this cause harm?" The structured rounds prevent the loudest voices from dominating, and the explicit distinction between consent and consensus gives people permission to let imperfect proposals pass. The real power is in the review date: knowing a decision can be revisited makes people more willing to try something that is not yet perfect. This creates momentum where consensus often creates paralysis.

Common Pitfalls

• Treating consent as consensus: The most common mistake. If the group starts trying to make everyone happy, you have lost the plot. Keep reinforcing: "We are not looking for enthusiasm. We are looking for the absence of harm."
• Skipping the clarifying questions round: Groups want to jump straight to reactions. Without shared understanding, you get objections based on misunderstanding rather than substance.
• Poorly written proposals: Vague proposals produce vague objections. Insist on specificity before starting the process. "We should communicate better" is not a proposal. "We will hold a 15-minute daily stand-up at 9am for the next four weeks" is a proposal.
• Not testing objections: Some objections are preferences in disguise. The facilitator must be willing to gently probe: "Is this an objection based on our shared aim, or is this a preference?" This takes courage but is essential.
• Forgetting the review date: Without a review date, consent feels permanent and people become more cautious. Always set one.
• Letting the process drag: Each round should be tight. If you let clarifying questions run for 20 minutes, the group will lose energy and trust in the process. Use a timer.
• Using consent for everything: Not every decision needs this process. Reserve it for policy decisions and important choices. Day-to-day operational decisions should be made by whoever holds that responsibility.

Adaptations

• Virtual/remote delivery: Use a shared document for the proposal so everyone can see amendments in real time. Go round by name rather than visual order. Use the chat for clarifying questions if the group is large. Mute all except the current speaker during rounds.
• Larger groups (15-20): Shorten reaction rounds to one sentence each. Consider doing clarifying questions in pairs first, then bringing only unresolved questions to the full group.
• Smaller groups (3-5): The process can be more conversational, but keep the round structure. It is tempting to skip rounds with a small group, but the structure is what prevents the loudest voice from winning.
• Shorter timeframes: For simple, low-stakes proposals, compress the process into 10-15 minutes by combining clarifying questions and reactions into a single round.
• As a regular practice: Consent works best when it becomes habitual. Teams that use it weekly find that proposals get tighter, objections get more focused, and decisions happen faster over time.
• Combined with proposal-forming: If no proposal exists yet, use a separate process (such as a round of ideas followed by a small group drafting a proposal) before entering the consent process.

Real-World Applications

Leadership team aligns on hybrid working policy: A leadership team of eight used consent to decide on a return-to-office policy. The initial proposal required three days in the office. Two objections surfaced, both grounded in operational concerns about client-facing roles. The amended proposal allowed client-facing teams to choose their own pattern within a minimum of two days. It passed with a three-month review date.

Product team unblocks a feature prioritisation dispute: A product team of six had been debating which feature to build next for weeks. The product manager brought a specific proposal with a clear rationale tied to the team's quarterly goals. One team member raised an objection about technical debt. The integrated amendment added a "tech debt sprint" after the feature launch. Decision made in 25 minutes after weeks of circular discussion.

Nonprofit board adopts a new funding strategy: A board of 12 used consent to approve a shift from grant-only funding to a mixed model including earned revenue. Several board members had concerns but recognised these were preferences, not objections. One genuine objection about risk exposure led to an amendment capping earned revenue at 30% for the first year. The board set a six-month review.

Agile team agrees on Definition of Done: A development team of seven used consent to establish their Definition of Done. The process surfaced a hidden disagreement about code review standards that had been causing friction for months. The consent round forced the team to articulate the disagreement clearly, and the integration step produced a workable standard that everyone could live with.

Cross-functional group selects a new collaboration tool: A working group of 10 from different departments used consent to choose a project management tool. Rather than voting (which would have produced a winner and several resentful losers), they used consent on a specific proposal including the tool, migration timeline, and training plan. Two objections about data migration were integrated into the timeline. The decision stuck because no one felt steamrolled.