Decision Protocols — A quick reference

Choosing how you decide matters. The right protocol prevents rework and clarifies who is accountable. Below are practical protocols, when to use them, and short scripts you can use in meetings.

Consent (aka "no objection")

When to use: low-to-medium risk decisions where speed and broad agreement matter. Works well for routine operational choices.

How it works: The proposal is presented and everyone who has a serious objection speaks up. If no objections are raised within a short window, the proposal passes.

Script: "Here's the proposal. Are there any objections? If not, we'll proceed—speak up if you see a blocking concern."

Lightweight Consensus

When to use: when you want broad alignment but can tolerate minor reservations. Useful for team norms or recommended approaches.

How it works: Discuss until major concerns are resolved; remaining reservations are noted but do not block. The group records dissenting views and moves forward with an owner.

Script: "Let's surface major concerns and see if they can be addressed. If not, we'll record reservations and assign an owner to monitor outcomes."

Majority Vote

When to use: when options are mutually exclusive and time is limited. Best when voting is fair and all parties accept the process beforehand.

Script: "We'll take a quick vote. Options A/B/C — raise hands or use poll. Highest votes wins; minority views will be documented."

DACI (Driver / Approver / Contributors / Informed)

When to use: complex decisions requiring clear roles and accountability across teams (e.g., product launches, vendor selection).

How it works: Driver coordinates the process, Approver signs off, Contributors provide input, Informed are kept updated.

Script: "Driver X will coordinate, Approver Y will sign off after we've gathered input. Contributors Z will prepare the analysis by Friday."

Delegated Decision

When to use: when the group empowers one person or sub-team to decide (often for efficiency or when technical expertise is needed).

Script: "We delegate the decision to Sam and expect a recommendation and rationale by next Tuesday. We'll review results in two weeks."

Recommendation + Ratify

When to use: a small team recommends and a designated approver ratifies (useful in governance or cross-functional escalation).

Script: "Team will recommend by Thursday; Approver will ratify (or ask for changes) within two business days."

Tip: Before the meeting, add the chosen decision protocol to the invite. That small signal changes participant behavior and reduces time spent arguing process.