Most teams use the same approach for every decision: whoever speaks loudest wins, or the most senior person decides. Both produce bad outcomes over time. High-performing teams match the decision-making process to the decision type — using structured voting for multi-option choices, DACI for decisions needing clear ownership, consensus for decisions requiring deep buy-in, and the advice process when one person should move fast but with input. This guide covers the five most useful frameworks and when to use each.
Framework 1: Majority vote (and ranked choice)
Majority vote is the simplest framework: everyone eligible to vote picks their preferred option, and the option with the most votes wins. It works well when the options are clear, the decision affects all voters equally, and you need a result quickly. The limitation is that majority vote can elect a "minority favourite" when there are many options — an option that only 30% of people want can win when votes are split across several alternatives. Ranked choice voting (instant-runoff voting) solves this by letting voters rank options in order of preference. The winner needs to achieve genuine majority support through elimination rounds. Use ranked choice when you have 4+ options and want to find the option with the broadest support.
Framework 2: DACI (Driver, Approver, Contributors, Informed)
DACI is a decision-making model that clarifies who does what in a decision process. The Driver owns the process — they run the decision, gather input, and are accountable for reaching a conclusion. The Approver has final say — often a senior stakeholder who can veto or approve. Contributors are consulted for input and expertise but don't have a vote. The Informed group is notified of the outcome but not involved in making it. DACI works best for operational and strategic decisions that need clear ownership — when you need one person accountable and one person with final authority. It prevents decisions from being made by committee while still gathering appropriate input.
Assign roles before starting
Before beginning any significant decision, explicitly name the Driver, Approver, Contributors, and Informed parties. This prevents ambiguity about who makes the call.
Driver collects input from Contributors
The Driver gathers structured input — this could be written input, a meeting, or a structured vote — from the Contributors. The goal is to surface considerations, not to reach consensus.
Driver proposes a decision
Based on input, the Driver proposes a specific decision with reasoning. This moves from "discussing options" to "here is what I recommend and why."
Approver reviews and decides
The Approver either approves the recommendation, requests changes, or exercises their veto. Once approved, the decision is final.
Framework 3: RACI — and why DACI is usually better for decisions
RACI stands for Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), Informed (notified of progress). RACI is primarily a project management model for assigning task ownership — it answers "who is doing what?" rather than "who decides?". For group decisions specifically, DACI is cleaner because it explicitly separates the person who drives the decision process (Driver) from the person who has final say (Approver). In RACI, the line between "Responsible" (doing the work) and "Accountable" (owning the outcome) is often blurred in the context of decisions. Use RACI for project task assignment. Use DACI for group decision-making.
Framework 4: Consensus decision making
Consensus does not mean unanimous agreement — it means the group reaches a position that everyone can actively support or at least live with. Consensus is the right framework when the decision affects everyone deeply and buy-in is critical for implementation. Decisions about team values, working norms, office location, or major strategic pivots benefit from consensus because implementation fails when key people feel overridden. The risk of consensus is that it takes time and can produce watered-down compromises. It also tends to over-index on whoever speaks most confidently. Structured anonymous voting can help: after a consensus discussion, run a private vote to check whether consensus actually exists or whether people are just going along with the loudest voice.
Frame the decision and options
Make sure everyone understands what is being decided and what the realistic options are. Ambiguity kills consensus processes.
Structured discussion with equal voices
Give every participant an equal voice in the discussion. Use round-robin input or written contributions to prevent vocal individuals from dominating.
Temperature check with private voting
Use anonymous voting to check genuine support levels. If the vote reveals that "consensus" was actually reluctant compliance, surface and address the objections.
Document and commit
When consensus is reached, document the decision explicitly. Consensus decisions fail when people re-litigate them later because there's no written record.
Framework 5: The advice process
The advice process is used in decentralised and self-managing organisations (popularised by Frederic Laloux's Reinventing Organizations). The principle is: anyone can make any decision, as long as they first seek advice from people who will be affected or who have relevant expertise. The decision-maker is not required to follow the advice — but must seek it and genuinely consider it. The advice process combines fast decision-making (one person decides) with broad input (many people consulted). It builds trust by giving everyone a voice without requiring consensus. It works best in teams with high trust and clear accountability. It breaks down when senior leaders ignore the advice or when the decision is so consequential that it needs formal approval.
How to choose the right framework
Match the framework to the decision type:
Use majority/ranked vote when: you have clear options and need a fast result
Product prioritisation, event selection, team name, vendor choice — any decision with defined options benefits from structured voting. Ranked choice is best with 4+ options.
Use DACI when: the decision needs clear ownership and one accountable person
Strategic direction, hiring decisions, budget calls — decisions where ambiguity about who's in charge causes problems. DACI names the Driver and Approver explicitly.
Use consensus when: buy-in is critical and the decision affects everyone deeply
Team values, working norms, office policy, major cultural decisions — anything where implementation fails without genuine support from the whole team.
Use the advice process when: you want speed with input, in high-trust teams
Day-to-day operational decisions, cross-functional calls, anything one person can reasonably own with input from those affected.
Combine frameworks for complex decisions
A major strategic decision might use DACI for ownership (one Driver), consensus process for the discussion, and ranked choice voting to surface genuine preferences before the Approver decides.
Frequently asked questions
There is no single best framework — it depends on the decision type. DACI works well for operational decisions with a clear driver. Consensus works for high-stakes cultural decisions where buy-in matters. Majority vote works for choosing between clear options. Most high-functioning teams use different frameworks for different decisions.
DACI stands for Driver, Approver, Contributors, Informed. The Driver owns the decision process. The Approver has final say. Contributors provide input. Informed parties are notified of the outcome. DACI is useful for decisions that need clear ownership and a single accountable person.
RACI is primarily a task and project management model. DACI is specifically a decision-making model. DACI is usually more useful for group decisions because it explicitly separates the Driver (runs the process) from the Approver (final say).
Use consensus when the decision affects everyone and genuine buy-in matters for implementation — for example, team working norms, values, or major strategic direction. Avoid consensus for decisions that need to be made quickly.
The advice process lets anyone make any decision — but they must first seek advice from people who will be affected or who have relevant expertise. The decision-maker isn't required to follow the advice but must seek and consider it.
Structured voting gives every participant a private, equal voice. It prevents the HiPPO effect, surfaces genuine preferences through anonymous mode, and produces a documented result. It works best for choosing between defined options after discussion.