Voting / Consensus Decision
Let a defined group weigh in on a decision and apply a rule — unanimous, majority, weighted — to pick the outcome. Good for steering-committee approvals, board decisions, and committee reviews.
On this page
Visual Flow
Rendering diagram…
When to Use This Pattern
Use voting when:
- A decision has multiple legitimate stakeholders
- No single role has the authority to decide alone
- Distributed accountability is wanted ("the committee approved this")
- Examples: architecture review boards, change advisory boards, investment committees, club/member governance, steering committees
Do not use voting when a clear owner should decide. Committees-by-default slow everything down and diffuse responsibility.
How It Works
A voting group is defined for the decision type. A proposal is sent to every member. Each member responds with Approve, Reject, or Abstain. A tallying rule determines the outcome:
- Unanimous: all present members must approve
- Supermajority: e.g. ⅔ or ¾ approve
- Simple majority: >50% approve
- Weighted: each member has a vote weight (board seats, equity, etc.)
A quorum can be required — a minimum number of members must vote for the result to count.
Abstentions are tricky. Decide explicitly: do they count toward quorum? Toward the denominator in "majority"? The rules matter when a vote is close, and you don't want to decide them after the fact.
Implementation Guide
Step 1: Define voters and their weights
Who votes? What weight does each carry? Record it at the moment the vote starts — changes to the group mid-vote create audit nightmares.
Step 2: Pick the tallying rule explicitly
Write it down, including how abstentions and missing votes are treated. Publish it before the vote starts.
Step 3: Set a deadline and a quorum
A vote that never ends isn't a decision. Typical setups: vote window of 3–7 days, quorum of ≥50% of voters. Non-responders default to abstention.
Step 4: Hide running totals (usually)
In sensitive votes, showing the running count influences later voters. Lock vote visibility until the deadline. For routine committee work, open visibility is fine.
Step 5: Publish the outcome with the reasoning
The tally, the rule applied, the quorum status, the final decision, and each voter's position (unless you want anonymous). Skip any of these and the losing side will argue the process.
Tips & Best Practices
- Build in a revote path. A close or contested result should have a way to request a second round with more info.
- Let voters change their mind before close. Public voters change less; anonymous voters change more. Both are fine.
- Rotate membership regularly. Committees that never turn over calcify.
- Track participation rate. A voter who abstains every time isn't a voter. Replace them.
- Don't use voting as a substitute for a decision-maker. If there's a clear owner, let them own it.
Related patterns
Parallel Approval with Threshold
Send approval requests to multiple people simultaneously and proceed when a minimum number approve. Faster than serial chains for peer-level decisions.
Serial Approval Chain
Route a request through a sequence of approvers where each must approve before the next receives it. The simplest and most common approval pattern.
Budget-Tiered Approval
Route purchase requests, expense reports, and financial approvals through different approval chains based on the dollar amount. Low-value requests skip senior approvers; high-value requests get more scrutiny.