📎 Webclip
Consensus-Driven Development
Consensus-driven development is presented as a better way for software teams to make decisions than majority-rules voting. The article says voting often leaves resentment, concentrates influence, and fails to ensure that everyone truly agrees, while consensus asks each person to accept and support the final decision.
Reading notes#
- Software teams face many opinionated choices, from language and coding style to patterns, naming, and features, so they need a way to move the discussion forward.
- Voting often reflects hierarchy and influence rather than shared agreement, and it can leave people holding grudges, feeling shut out, or resisting the result.
- Consensus requires everyone’s input and an explicit commitment to abide by the decision even if it is not each person’s favorite.
- To build consensus, the leader should set expectations, frame the impact of the decision, and keep a time limit for low-impact topics.
- The article recommends opening the room for free-form opinions first, then checking how far apart the positions are.
- Competing views should be encouraged so that disagreement and missing details are brought into the conversation.
- The discussion should stay positive and constructive, and everyone who wants to speak should be heard.
- Possible ways to reach agreement include general agreement, deferring to the most committed champion, having champions debate, taking turns, and using voting only as a last resort.
- Voting in this framework is used to measure how close the group is to consensus, not to replace consensus with majority rule.
- A decision is not settled until dissenters can say they can live with and support it.
- The article says consensus works best when the choices are similar and no option is clearly best or worst, and when the decision is actually suited to a group process.
- A strong leader is still needed to guide the conversation and keep the level of discourse up.
