Decision protocols — choose the right way to decide

Decisions are the most important outputs of many meetings. Using an explicit protocol makes decision-making faster, fairer, and easier to uphold. Here are five practical protocols with when to use each.

1. Consent (aka no-blocking)

When to use: Fast operational decisions where people can live with the decision unless they raise a reasoned objection.

How: Propose the decision and ask, "Any objections?" If none or only minor concerns, proceed. If there’s a blocking objection, discuss or defer to another protocol.

Good for: Tactical allocations, minor process changes.

2. Advice & Decide

When to use: One person is accountable but needs input from others.

How: Gather advice from relevant stakeholders (timebox responses), then the decision owner decides and documents rationale and who was consulted.

Good for: Managerial or product-owner decisions where a single accountable person is needed.

3. Delegation (explicit autocratic)

When to use: Rapid decisions or those needing a single authority (eg. emergency response).

How: The group explicitly delegates authority to a named person for a defined scope and time. The delegate reports outcomes afterward.

4. Majority or weighted voting

When to use: When many options exist and a clear, quick group choice is needed; avoid for decisions that need broad buy-in.

How: Define voting rules (simple majority, supermajority), collect votes (anonymous if bias is a concern), and confirm results and next steps.

5. Multi-voting / Dot-voting (for options narrowing)

When to use: Prioritizing many ideas after a brainstorm.

How: Each participant has a small number of votes to distribute among options; top votes move forward to deeper evaluation.

Choosing the right protocol

Consider impact (how many people are affected), urgency, need for buy-in, and available information. Document which protocol you used and why — that reduces friction if the decision is revisited.

Common pitfalls

• Not naming the decision owner — leads to drift.
• Using majority vote for high-impact change — undermines buy-in.
• Skipping the rationale — makes reversal more likely and trust lower.

Tip: For recurring teams, keep a living decisions log that records decision, protocol used, date, owners, and a 1-sentence rationale.