Consensus is for existential decisions only — founding documents, core values, irreversible pivots — its cost must match the stakes

Why This Is a Rule

Consensus is the most expensive decision-making framework: it requires every participant to positively agree, takes the most time, consumes the most emotional energy, and produces the most compromise. This cost is justified for precisely one category of decisions: existential ones where executing an outcome some members fundamentally oppose would fracture the group.

Founding documents warrant consensus because a constitution that half the founders reject is a civil war waiting to happen. Core values warrant consensus because values that half the team doesn't share produce irreconcilable conflicts in daily operations. Irreversible strategic pivots warrant consensus because a pivot that alienates key members loses the human capital needed to execute it.

For everything else — operational decisions, tactical choices, tool selection, process changes — consensus is overkill. It slows decisions to the speed of the most reluctant participant, incentivizes lowest-common-denominator compromise, and produces decision fatigue that depletes the group's capacity for the genuinely existential decisions that need it. Use consent (Use consent-based decisions for speed+buy-in — proceed unless someone articulates a specific reasoned objection) for operational decisions and disagree-and-commit (For two-way doors with persistent disagreement, invoke 'disagree and commit' — state your objection, then fully support the decision) for reversible ones.

When This Fires

• When choosing a decision-making framework for a specific decision type
• When someone says "we should all agree on this" — check if the stakes truly warrant consensus
• When consensus-seeking is consuming organizational energy disproportionate to decision stakes
• When designing governance structures that need to specify which decisions require which frameworks

Common Failure Mode

Defaulting to consensus for all group decisions: "We need buy-in, so let's reach consensus." This produces two pathologies. First, trivial decisions consume enormous time as the group negotiates minor preferences toward agreement. Second, genuinely important decisions receive the same process as trivial ones, diluting the signal that "this decision requires everyone's real alignment."

The Protocol

(1) When a group decision arises, classify: is this existential — would executing an outcome that some members fundamentally oppose fracture the group or prevent the mission? (2) If yes → use consensus. Everyone must positively agree. Take the time it requires. This is rare: maybe 2-5 decisions per year for most teams. (3) If no → use a lighter framework matched to the decision's actual stakes: consent-based for operational decisions needing buy-in (Use consent-based decisions for speed+buy-in — proceed unless someone articulates a specific reasoned objection), disagree-and-commit for reversible decisions (For two-way doors with persistent disagreement, invoke 'disagree and commit' — state your objection, then fully support the decision), or delegated authority for low-stakes decisions (Delegate any decision reversible within one week at low cost — retain only irreversible ones for direct judgment). (4) Be explicit about which framework you're using and why: "This is a consent decision, not consensus. We proceed unless someone articulates a specific objection." This prevents consensus creep.