Consent Decision-Making, and Why It Is Not Consensus

Most groups that say they work by consensus are actually working by exhaustion. The meeting runs long, the people with the most stamina or the least at stake outlast the others, and the decision that emerges is the one nobody had the energy to keep objecting to.

Consent is the fix, and the difference is one question.

The question that changes everything

Consensus asks: do you agree?

Consent asks: do you have an objection?

That looks like a small distinction. It is not. It moves the burden.

Under consensus, a proposal has to win everyone over. Every preference, taste and mild misgiving is a veto, because agreement is the bar. The result is that proposals get watered down until they offend nobody and accomplish nothing, or the group simply stops proposing.

Under consent, a proposal proceeds unless someone can name a reason it would cause harm or move the group backwards. Preferences are heard but they do not block. The bar is "good enough for now, safe enough to try", not "the best thing anyone can imagine".

What counts as an objection

This is where groups fail, so be strict about it.

An objection is a reason the proposal would harm the group's ability to do its work or meet its purpose.

It must be about the proposal, not about your preference. It has to be argued, not just felt. And the person raising it has to be willing to help find the fix.

These are objections:

• "This commits us to spend in month two that we do not have in month two."
• "This makes me the only person who can approve refunds, and I am away in August."
• "This conflicts with the agreement we made with the landlord in writing."

These are not objections. They are preferences, and they belong in the discussion round, not the objection round:

• "I would have done it differently."
• "I don't love it."
• "I think there's a better option we haven't explored."
• "I'm not comfortable with it." (Unless you can say what harm follows. Sometimes you can, and then it is an objection. "Not comfortable" alone is a feeling, and feelings are real data but they are not yet an argument.)

The honest test: if you cannot describe what goes wrong, you do not have an objection. Say your preference, let the group hear it, and let the proposal go.

Running the round

The structure matters more than it looks. Do it in this order, and do not let it collapse into open discussion.

1. Present the proposal. One person, briefly. No debate yet.

2. Clarifying questions. Questions only, answered by the proposer. Not "have you considered" (that is an opinion wearing a question mark). Just: what does this mean, what does that word cover, how much.

3. Quick reactions. One round, each person, short. This is where preferences live. No cross-talk. The proposer does not defend anything, just listens.

4. Amend or withdraw. The proposer may change the proposal based on what they heard, or pull it. Their call, nobody else's.

5. Objection round. Each person in turn: objection, or no objection. That is the whole answer. If someone objects, they state the harm, briefly.

6. Integrate. Work the objection into the proposal until it no longer holds. The objector helps. This is a collaboration, not a negotiation.

The rounds are not bureaucracy. They exist because open discussion reliably hands the decision to whoever talks most, and a round gives the quiet person a moment that is structurally theirs.

"Good enough for now, safe enough to try"

Write this on the wall.

Most decisions that stall are stalling because the group is trying to make them permanently right. Almost nothing needs to be permanently right. It needs to be reversible, or cheap enough that being wrong is survivable.

So attach two things to every proposal:

A review date. "We do this, and we look at it again on 1 March." An objection that means "I don't trust this forever" often dissolves when forever becomes eight weeks.

A named owner. Someone whose job it is to notice if this is going badly before the review date.

A proposal with a review date and an owner is a much smaller thing to consent to than a proposal that will apparently last until the heat death of the universe.

Where it goes wrong

Treating discomfort as an objection. The group gets stuck exactly where consensus got stuck. Ask the question: what specifically goes wrong? Sit in the silence while they answer it.

Treating an objection as an attack. The objector is doing the group a service by naming a risk out loud. If objecting is socially expensive in your group, people will stop, and you will discover the risks later and more expensively.

Skipping the reactions round to save time. You will save six minutes and then spend an hour on the objection that would have surfaced as a mild reaction.

Letting the proposer defend during reactions. The moment the proposer starts arguing, the round becomes a debate and the remaining people stop saying what they think.

Never revisiting. If review dates pass unexamined, "good enough for now" quietly becomes permanent, and people learn that consenting is a one-way door. Then they start objecting to everything.

What good looks like

A proposal reaches the objection round in nine minutes. Two people had reactions that changed it. One person objected on a real risk, and the objection was integrated by adding a spending cap rather than by abandoning the idea. The decision has an owner and a date in March.

Nobody was talked into anything, and nobody needed to be.

Try this week

Take the next decision your group would normally "discuss until we all agree" and run the six steps exactly as written, including the rounds. Before the objection round, read out the definition of an objection.

Then notice how many of the things that usually block a decision turn out to be preferences.