Team Decision-Making Methods: Consensus, Consent, RACI and DACI

How consensus, consent, RACI, DACI and RAPID work, where each fits, and how to match a decision method to how reversible the decision is.

Collaboration Center · Last reviewed October 23, 2026 · 6 min read

Many team arguments are not really about the decision. They are about how the decision is being made. One person thought they were being consulted, another thought they had a veto, and a third assumed the manager would just decide. When the process is unclear, even a good decision can leave people feeling ignored.

The fix is to agree on the method before the debate starts. This guide explains four widely used approaches, namely consensus, consent, RACI and DACI, along with a close relative called RAPID and a simple way to sort decisions by how reversible they are. None of them is best for everything. The skill is matching the method to the decision.

First, sort decisions by how reversible they are

Before picking a method, ask how costly it would be to undo the decision. In his 2015 letter to Amazon shareholders, Jeff Bezos described two kinds of decisions. Some are "consequential and irreversible or nearly irreversible – one-way doors – and these decisions must be made methodically, carefully, slowly, with great deliberation and consultation." Most others are reversible "two-way doors" that "can and should be made quickly by high judgment individuals or small groups."

He also warned that as organizations grow, they tend to apply the heavy process to everything, with the result being "slowness, unthoughtful risk aversion, failure to experiment sufficiently, and consequently diminished invention." In his 2016 letter, he added: "Most decisions should probably be made with somewhere around 70% of the information you wish you had." He also described "disagree and commit," in which someone with conviction acknowledges the disagreement and asks colleagues to back the decision anyway: "will you gamble with me on it? Disagree and commit?"

You don't need to run a large company to use the idea. For a small team, a quick question such as "Is this easy to reverse?" can tell you whether to use one of the lighter methods below or one of the more deliberate ones.

Consensus: agreement everyone can live with

Seeds for Change, a workers' co-op that offers training and facilitation for community groups and co-operatives, describes consensus as "a creative and dynamic way of reaching agreement between all members of a group." The aim is a solution that everyone actively supports or at least can live with, and the defining principle is that "no decision is made against the will of an individual or a minority."

Consensus is not the same as everyone loving the outcome. Seeds for Change describes a range of responses, from agreement, to agreement with reservations, to standing aside ("I can't support this proposal...but I don't want to stop the group"), to a block, which is a fundamental objection that stops the proposal.

The organization also lists conditions that make consensus work, including a common goal, commitment to the process, trust and openness, sufficient time, a clear process, active participation and good facilitation. That list doubles as a warning. If you are short on time or trust, consensus can stall.

Consensus fits decisions about shared values, ground rules and anything where lasting buy-in matters more than speed.

Consent: good enough for now, safe enough to try

Consent decision-making asks a different question. Instead of "Does everyone agree?" it asks "Does anyone have a reasoned objection?" Sociocracy 3.0, a freely licensed collection of patterns for collaboration, defines it as "a (facilitated) group process for decision-making: invite objections, and consider information and knowledge revealed to further evolve proposals or policies."

The key is the difference between an objection and a concern. In Sociocracy 3.0's terms, an objection is an argument that reveals consequences or risks the organization would prefer to avoid, or shows a worthwhile way to improve the proposal. A concern is an assumption that cannot yet be backed by enough reasoning or evidence to count as an objection. Proposals are accepted "when they are considered good enough for now and safe enough to try until the next review." Objections stop a proposal until they are resolved. Concerns are noted but do not block.

Consent works well for policies, process changes and experiments, especially when you can set a review date.

RACI: who does what on a piece of work

RACI is a responsibility chart. For each task or deliverable, you mark who is Responsible, Accountable, Consulted and Informed. It is most useful for mapping recurring work and handoffs, rather than for a single decision.

For example, imagine a seven-person accounting office building its year-end client checklist:

Responsible: the staff accountant who drafts the checklist
Accountable: the office manager who signs off and owns the result
Consulted: the two senior accountants who review it for gaps
Informed: the front desk, who will field client questions

A good rule of thumb is one Accountable person per row. If two people are accountable, in practice neither is. Keep the Consulted list short, because every name there adds time.

DACI: roles for a specific decision

DACI applies the same idea to one decision. The Atlassian Team Playbook, a free set of team exercises, defines four roles:

Driver: "the person responsible for corralling stakeholders, collating all the necessary information, determining the scope of the decision, and getting a decision made by the agreed date"
Approver: the single person with final authority to make the decision
Contributors: "people who have subject-area knowledge and can make recommendations – i.e., they have a voice, but not a vote"
Informed: "people whose work may be affected by the decision, and should be informed once it's been made – i.e., no vote, no voice"

A useful habit is to write the DACI roles at the top of a short decision document, along with the options, the deadline and the eventual outcome.

A close relative: RAPID

Bain & Company's RAPID framework (a registered trademark of the firm) uses five roles. Recommend "drives the process, gathering relevant input and developing a recommendation for the decider." Agree is used sparingly for people whose input must be reflected in the proposal. Perform covers those "accountable for implementing the decision once it is made." Input provides "expertise, experience, or information that shapes the recommendation." Decide "makes the final decision and commits the organization to action." If your team often discovers too late that legal, finance or operations needed to sign off, RAPID's Agree role addresses exactly that gap.

Choosing a method

A simple starting point:

Quick, reversible decisions: one named decision owner, with brief input. Write it down and move on.
Important decisions with a clear owner: DACI or RAPID, so input is gathered without blurring who decides.
Team policies, processes and experiments: consent, with a review date.
Shared values and ground rules: consensus, when you have the time and trust it needs.
Recurring work with many hands: RACI, to clarify ownership and handoffs.

Whatever you choose, say it out loud at the start: "This is a consent decision" or "Maria is the approver; we're contributors." Then record the decision, who made it and why, somewhere the team can find it later.

Key takeaways

Agree on how a decision will be made before debating what it should be.
Sort decisions by reversibility, and save heavy processes for the ones that are hard to undo.
Consensus seeks agreement everyone can live with; consent proceeds unless there is a reasoned objection.
RACI clarifies roles across ongoing work; DACI and RAPID clarify roles for a single decision.
Name one decision owner or approver, and record the decision and its reasoning.

Sources

Spotted something out of date? Let us know.