Consensus decision making is an approach in which a group seeks broad agreement among its participants before committing to a decision. It is distinct from majority voting and from authority-based decisions in that the goal is not a winning side but a position the whole group can support, even if not enthusiastically.
Consensus is not unanimity. Most consensus processes allow participants to "stand aside" — to disagree without blocking — so that a small minority does not have veto power. The threshold varies by group culture and decision stakes.
Consensus has clear benefits for buy-in and clear costs for speed. It works well for high-stakes decisions affecting a small group and works poorly for high-frequency decisions affecting a large one.
Why Consensus decision making Matters for Distributed Teams
Many engineering organizations default to consensus when authority would serve them better. The result is decisions that take weeks and please no one.
Knowing when to use consensus and when to use authority is one of the most important skills in engineering leadership.
Frequently Asked Questions
What is consensus decision making?
Consensus decision making seeks broad agreement among participants before a decision is committed. It is distinct from majority voting. Most consensus processes allow participants to stand aside rather than block, preventing a small minority from having veto power.
Related Terms
Decision making
Decision making is the process of choosing among options under uncertainty. In organizational contexts, it is rarely the...
Read definitionCommittee decision making
Committee decision making is an approach in which decisions of a given type are routed through a standing group rather t...
Read definitionDecision velocity
Decision velocity is the rate at which an organization moves from open question to committed answer. It is the time betw...
Read definitionGet the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See consensus decision making in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.