What does it mean that consent-based decision-making?

Decisions proceed unless someone has a substantiated objection — faster than consensus, more inclusive than authority. Consent-based decision-making occupies the middle ground between two common extremes: consensus (everyone must agree) and authority (one person decides). In consent-based decision-making, a proposal proceeds unless someone presents a reasoned, substantiated objection — not a preference, not a concern, but an objection backed by evidence that the proposal would cause harm or move the organization backward. This approach produces decisions that are good enough for now and safe enough to try — enabling organizational velocity while maintaining collective intelligence.

Example: A product organization at a SaaS company, Nexus, struggled with decision paralysis. Their culture valued consensus — but consensus among 15 stakeholders across product, engineering, design, and business development was nearly impossible. Feature prioritization meetings ran three hours and often ended without resolution because one or two stakeholders had preferences that differed from the majority. The company adopted consent-based decision-making. The process worked as follows: a proposer presented a prioritization recommendation with supporting evidence. Each stakeholder could respond in one of three ways: consent (I support this), concern (I have reservations but will not block), or objection (I believe this will cause specific harm). Objections required substantiation: the objector had to articulate the specific harm they anticipated and the evidence supporting their concern. Concerns were recorded but did not block the decision. Objections triggered a focused discussion: could the proposal be modified to address the objection while preserving its core intent? The impact was transformative. Prioritization meetings dropped from three hours to 45 minutes. More importantly, decision quality improved — because objections had to be substantiated, the discussion focused on genuine risks rather than personal preferences. The first quarter under the new process, the team made 28 prioritization decisions that had been stuck in consensus paralysis, clearing a backlog of indecision that had accumulated for months.

Try this: Practice consent-based decision-making on one pending decision in your team. Follow this protocol: (1) A proposer presents the decision with a clear recommendation and supporting reasoning. (2) Each participant responds with one of three responses: consent ('I support this'), concern ('I have a reservation but do not object'), or objection ('I believe this will cause the following specific harm: ___'). (3) For concerns: record them and move forward. Concerns inform future monitoring but do not block the decision. (4) For objections: the objector must state the specific harm they anticipate. The group then discusses: can the proposal be modified to address the objection? (5) If the objection is addressed, the modified proposal proceeds. If the objection cannot be addressed, the proposal is withdrawn or escalated. After the exercise, reflect: How did the consent process differ from your team's usual decision-making? Was the decision faster? Was the discussion more focused? Did the substantiation requirement change the quality of objections?