Use consent-based decisions for speed+buy-in — proceed unless someone articulates a specific reasoned objection
For operational decisions requiring both speed and buy-in, use consent-based decision making: present a proposal and proceed unless someone articulates a specific reasoned objection (how it would prevent achieving goals), rather than seeking consensus (positive agreement from everyone).
Why This Is a Rule
Consent-based decision making (from sociocracy and holacracy) occupies the sweet spot between autocracy (one person decides, no buy-in) and consensus (everyone agrees, no speed). The mechanism is elegantly simple: someone presents a proposal, and the question isn't "does everyone agree?" but "does anyone have a reasoned objection — a specific way this would prevent us from achieving our goals?"
The burden of proof shifts from the proposer (who must convince everyone to agree) to the objector (who must articulate why the proposal would cause harm). This shift is dramatic: most proposals survive because while people might prefer a different approach, they can't articulate how the current proposal would prevent goal achievement. "I'd do it differently" is not an objection. "This would cause X, which prevents us from achieving Y" is.
This produces dramatically faster decisions with genuine buy-in because participants have had the opportunity to object and have either raised legitimate concerns (which are addressed) or acknowledged that the proposal is "safe enough to try." The framing "safe enough to try, good enough for now" replaces the perfectionism trap of consensus.
When This Fires
- For operational decisions where both speed and team buy-in matter
- When consensus-seeking is producing delays without improving decision quality
- In meetings where "let's discuss this more" has become the default outcome
- When teams need a structured alternative to both top-down decisions and endless deliberation
Common Failure Mode
Treating consent as consensus with different words: "Does anyone object?" followed by uncomfortable silence that's interpreted as consent when it actually reflects conflict avoidance. Real consent-based process requires active checking: "Sarah, you look uncertain — do you have a specific concern about how this would prevent us from achieving our goals?" Active facilitation prevents false consent.
The Protocol
(1) Proposer presents a clear, specific proposal. Not a question ("what should we do?") but a proposal ("I propose we do X"). (2) Clarifying questions only — no reactions yet. Ensure everyone understands the proposal. (3) Reaction round — each person shares quick reactions (not objections). This surfaces concerns without blocking. (4) Objection round — each person states whether they have a specific, reasoned objection: "This proposal would prevent [goal] because [mechanism]." (5) If no objections → proceed. The proposal is "safe enough to try." (6) If objections → integrate: modify the proposal to address the specific concern, then re-check. The objection must be specific and goal-preventing — "I prefer something different" is not an objection.