Making better tough decisions - from Consensus to Consent
by Tony Fifoot, ~5 mins reading time
This is part 4 in a series, which started as 4 parts, but then I decided would be 5.
In Part 3, I covered the Advice process: a structured way for anyone to make faster, better decisions by seeking input before deciding. Today is a key piece: Consent. This one is specifically about replacing consensus, and it's where the biggest shift in how your organisation operates tends to happen.
If you've ever sat in a meeting where a decision kept circling because someone always had one more concern, or watched a good idea get slowly diluted until it satisfied everyone but excited nobody, this is for you.
The problem with Consensus (a brief recap)
Consensus sets the default to 'no'. Everyone must say "yes" before moving forward. Any outstanding concern, even a peripheral one, can stall progress. And because the bar is full agreement, the pressure builds to water things down until they're palatable rather than good. You end up with slower decisions, worse decisions, and worse outcomes.
There's also the inclusion paradox I mentioned in Part 2: Consensus looks inclusive but often isn't. Without structure, the loudest and most senior voices dominate. The people closest to the work, who often have the most relevant perspective, self-silence, and everyone leaves feeling vaguely dissatisfied, either steamrolled or unheard, or both.
What Consent actually means
Consent comes from Holacracy's Integrative Decision Making (IDM) process, a structured approach designed to help complex organisations move quickly without losing important perspectives. The core idea is simple but powerful: flip the default.
In consensus, the default is 'no'. In consent, the default is 'yes' - the proposal moves forward unless someone raises a valid objection. That's a fundamental shift in how a group approach a decision.
“The question changes from ‘does everyone agree this is the best option?’ to ‘does anyone have a valid reason why we shouldn’t proceed?’”
Importantly, we start with a named decision owner, someone who holds the authority to make the call. But the group's role shifts from approving to objecting, and only where the objection is genuine and specific.
What makes an objection valid
This is where the “safe to try” test comes in. Not every concern is a valid objection. A valid objection has to meet a clear bar: this decision will cause immediate, hard-to-reverse harm. It will genuinely set us back right away, and recovering from it will be difficult.
Everything else, "I'd prefer a different approach", "I'm worried this might not work", "I’d prefer a different shade of blue", is a hesitation, not an objection. It gets heard and noted, but it doesn't block progress. The person raising it is still asked to commit in the spirit of moving forward and learning.
When a valid objection is raised, it's not ignored. The person objecting works with the decision owner to amend the proposal, not to kill it, but to find a version that's safe to try. The goal is always forward movement, not watering it down, or a stalemate.
“Progress over perfection isn’t reckless. It’s how fast-moving organisations learn and stay ahead. Consent is the mechanism that makes it safe to move.”
The shift that changes everything
Moving from consensus to consent isn't just a process change, it’s a mindset change and changes the size and shape of decisions themselves. When you need everyone to agree before moving, decisions get big. You load them up with analysis, caveats, and conditions trying to achieve certainty before committing. The batch size grows, the feedback loop slows, and the pressure to get it right the first time becomes paralysing.
When the bar shifts to 'safe to try', decisions get smaller. Instead of one large bet that has to be right, you take a series of informed steps toward a goal, each one generating feedback that shapes the next. You move from perceived certainty (which was never real anyway) to genuine learning.
We’ve been using this same approach in product development for ages. This is how fast-moving organisations actually create value. Not through perfect upfront planning, but through shorter cycles of action and learning. Consent is the mechanism that makes that possible. It replaces the need for certainty with something more useful: enough confidence to move, and a clear way to course-correct if needed.
In uncertain markets, this isn't just a nice-to-have. The organisations that learn fastest are the ones that win, and you can't learn fast if every decision requires unanimous agreement before you can take a step - that’s aversion to risk, not managing risk.
What changes in practice
Teams that shift from consensus to consent typically notice a few things quickly. Meetings get shorter because concerns are raised and addressed rather than circled. People feel more genuinely heard, not because they got their way, but because their input was taken seriously without derailing the whole process. Decisions start moving at a pace that matches the environment they're operating in, which has only sped up as AI accelerates the non-decision parts of the workflow.
It also builds psychological safety in a different way than consensus does. When people know their concerns will be heard without grinding everything to a halt, they're more willing to raise them early and openly. That's exactly the behaviour you want with concerns surfaced before a decision, not after.
Where to start
Like the Advice process, consent works best when it's made explicit. Name the decision owner. Share the proposal and context. Give people the chance to raise objections. Test each objection against the 'safe to try' bar. Then commit and move forward.
It takes a few rounds to get comfortable with the distinction between a hesitation and a valid objection - that's normal. But once a team internalises it, the speed and quality of decisions improves noticeably, and the culture starts to shift toward progress over perfection.
In the final article, I’ll provide an overview and cheat sheet of how to use Advice and Consent based decision making in your company.
If you missed Parts 1–3 of this series, links are below.
Your decision making approach costs more than you think