Community Governance

What Consent-Based Decision Making Actually Looks Like

Consensus rewards the loudest preferences. Consent rewards the principled objection. Here's how the practice actually works on a tired Tuesday evening.

diversity_3By The Steward·Nov 09, 2025·7 min read

The First Time I Saw It Done Right

It was a Tuesday night in February. Eleven of us in a converted barn, deciding whether to spend €4,000 on a new biomass boiler. I had read three books on consent-based decision making by then. None of them prepared me for how slow it felt.

Consent-based decision making is the practice of asking, "Is this proposal safe enough to try, and good enough for now?" That's it. You're checking for principled objections that, if ignored, would harm the group. You're not chasing perfection. You're not chasing unanimous love.

It took us forty-seven minutes to approve the boiler. Three people had concerns. One had a real objection (we hadn't checked the warranty terms). We paused, checked, came back, decided. By 9:15pm we had a decision everyone could live with and nobody felt steamrolled.

That's the whole game.

The Difference From Consensus

People mix these up constantly. Consensus asks, "Does everyone agree?" Consent asks, "Does anyone object?" Those questions have different gravitational pulls.

Consensus rewards the loudest preferences. The person who really, really wants the dark green walls will outlast the person who mildly prefers cream. After two hours, you get dark green walls and a quietly resentful minority.

Consent flips it. The default is "we move forward unless someone has a reasoned objection." A preference for cream walls doesn't qualify. A concern that the dark green paint contains a chemical you're allergic to does.

This sounds like semantics. It isn't. It changes who carries the burden of speaking up, and it speeds everything up by maybe 60%.

What an Actual Round Looks Like

Here's the rhythm we use, almost every time. Borrowed from sociocracy and gently bent to fit a tired Tuesday evening.

1. Present the proposal. Two minutes. No discussion yet. Just the shape of what's being proposed and why. 2. Clarifying questions. Five minutes. People ask things like "what's the budget?" or "who'd maintain it?" These aren't reactions. They're information-gathering. 3. Reaction round. Each person, in order, says one or two sentences about how they feel. No interruption. No debate. 4. Amendment round. The proposer adjusts the proposal based on what they heard, if anything needs adjusting. 5. Consent round. Each person, in order, says "consent," "stand aside," or "object." Objections come with a reason and a willingness to help find a path forward.

That's it. The whole structure slows you down at the right moments and speeds you up at the wrong ones.

What Counts as a Real Objection

This is where most groups get tangled. Someone says, "I object," and the room collapses into argument because nobody knows what an objection is.

A real objection has three properties. It names a specific harm to the group or the work. It's grounded in a value or principle the group has already agreed to. And the objector is willing to participate in finding an alternative.

"I don't like green" is a preference. "I don't have a good feeling about this" is a feeling. "I think this will violate our financial transparency agreement, and here's how" is an objection.

You will have to coach people on this. For about a year. After that, it gets easier.

The Quiet Power of Stand Aside

The most underused tool in consent-based decision making is the stand-aside. It means, "I'm not going to block this, but I want it on the record that I have reservations."

Stand-asides are gold. They let dissenters stay honest without halting the whole community. They also create a paper trail so that if the decision goes sideways six months later, you don't have to argue about who warned whom.

We had a stand-aside on a kitchen renovation in 2024. The person who stood aside was right (we did go over budget by €1,800). Because she had named her concern at the time, the group could acknowledge it without drama and learn from it. No "I told you so" was required. The record told you so.

Where Groups Get Stuck

Three failure patterns I've seen in roughly a hundred sessions:

  • The endless clarifying question. Someone uses "questions" as a way to argue. The facilitator has to gently say, "That sounds like a reaction. Hold it for the next round."
  • The proposer who keeps amending. A proposal that mutates twelve times in one meeting isn't a proposal anymore. Cap amendments at two. If it needs more, take it back to a working group.
  • Objections that aren't named. Someone is uncomfortable but won't say why. You can't process what isn't on the table. The facilitator's job is to gently invite the words out.

If you're new to facilitating these, expect to fail at all three for the first six months. That's normal.

When Consent-Based Doesn't Work

It isn't for everything. Three places I'd avoid it:

Operational decisions where someone has clear domain authority. The kitchen lead doesn't need a consent round to decide which dish soap to buy. Empower roles. Use consent for the high-stakes, group-binding stuff.

Emergencies. If the roof is leaking, you don't run a sociocratic round. You stop the leak. Decide the policy later.

Decisions where one person bears all the consequences. If someone is choosing how to use their own room, the group probably doesn't need to consent.

Tooling It Without Killing It

Most groups try to run consent rounds in WhatsApp threads or in person with no record. Both fail eventually. WhatsApp turns into noise. In-person with no record means three months later, you can't remember what you decided or why.

We use ARA's Council module for our Sanctuary, and it's removed about 70% of the meta-confusion. Each Proposal has a clear owner, a stated objective, the amendment history, and a visible vote of Consent / Stand-Aside / Block. New members can scroll back through old proposals to understand how the community reached its current shape. That alone is worth it.

A note on culture: tools won't save a group that hasn't internalized the principle. If your community thinks "objection" means "tantrum," no software will fix it. Start with the practice. Then add the scaffolding.

One Tuesday at a Time

Consent-based decision making is slow at first. Then it becomes the fastest thing your community does, because nobody is litigating old decisions or staging quiet sabotage. Trust compounds.

That biomass boiler is still running, by the way. Three winters in. The person who raised the warranty objection back in February was right; we needed those terms. We saved €600 on a service call last year because of it. Worth every minute of the round.

#Governance#Consent#Decisions#Sociocracy
JNL-gov-1
Build with ARA
The shared digital home for intentional communities.
Start Your Sanctuary

More from Community Governance