Skip to content
All articles

RACI is broken! Try DARE for Decisions

Dean Jain

Dean Jain

Senior Staff Software Engineer · Enterprise AI, Data & Cloud Architect

· 4 min read

Decision MakingFrameworksLeadership
---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart LR
    subgraph RACI["⚠️ RACI who actually decides?"]
        direction TB
        R["Responsible"]:::neutral
        A["Accountable"]:::neutral
        C["Consulted"]:::neutral
        I["Informed"]:::neutral
        Q["❓ no clear decider"]:::danger
    end
    subgraph DARE["✅ DARE the decider is explicit"]
        direction TB
        D["Decider"]:::good
        AD["Advisor"]:::obs
        RE["Recommender"]:::server
        EX["Executer"]:::gate
    end
    classDef neutral fill:#ECECEC,stroke:#8A8A8A,stroke-width:2px,color:#0F172A
    classDef danger fill:#FFB3B3,stroke:#D14545,stroke-width:2px,color:#0F172A
    classDef good fill:#BFEFC8,stroke:#3FA34D,stroke-width:2px,color:#0F172A
    classDef obs fill:#AED6F1,stroke:#2E86C1,stroke-width:2px,color:#0F172A
    classDef server fill:#A8E6D0,stroke:#2FA37C,stroke-width:2px,color:#0F172A
    classDef gate fill:#D7C3F2,stroke:#8E5BD0,stroke-width:2px,color:#0F172A

Figure 1: RACI assigns responsibility but leaves "who decides" ambiguous; DARE makes the Decider a named, first-class role.

Everyone reaches for RACI to clarify who does what Responsible, Accountable, Consulted, Informed. And then the decision still stalls, because RACI answers every question except the one that matters: who actually makes the call?

“Accountable” sounds like the decider. It really means “on the hook if it fails”, which is not the same thing at all. DARE is the fix a decision-centric framework that puts the decider front and center. If your projects keep stalling in committee, your RACI is the reason.

TL;DR

  • RACI’s fatal flaw: no clear Decider. “Accountable” is about consequences, not authority, so decisions drift and meetings spin.
  • RACI’s other pitfalls: poor stakeholder orchestration, fuzzy delegation, and meetings with no decision owner.
  • DARE makes the decider explicit: Deciders (the votes), Advisors (set context, ask questions), Recommenders (do the analysis, propose options), Executers (implement).
  • Name the decider before the meeting, not during it. Ambiguity about authority is what turns a decision into a debate.
  • The Power of Questions clarifying, elaboration, and reflection questions is how Advisors and Deciders actually extract the truth.

1. Why RACI keeps failing you

RACI isn’t wrong, it’s incomplete. Its four roles are useful for assigning work:

  • Responsible does the task.
  • Accountable answers for it being done.
  • Consulted gives input before/during.
  • Informed told about the outcome.

But read that list again looking for “who decides between options A and B?” It isn’t there. Teams assume Accountable is the decider. But accountability is about who takes the blame, not who holds the authority, and conflating the two is precisely how decisions get stuck. The predictable failure modes follow:

  • No clear “Decider” the meeting ends with “let’s circle back” because no one was empowered to choose.
  • Poor orchestration of stakeholders the Consulted multiply until consensus becomes the (impossible) bar.
  • Poor delegation without a named decider, nobody feels safe to act.
  • Ineffectual meetings a room full of opinions and no mechanism to convert them into a decision.

The fix isn’t a better-filled-in RACI grid. It’s a framework built around the decision instead of around the tasks.

2. DARE: build the roles around the decision

DARE keeps RACI’s clarity but reorganizes it around making the call. Four roles, and the order is the workflow:

---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart LR
    RE["🔬 Recommenders<br/>analyze · explore alternatives"]:::server --> AD["🧭 Advisors<br/>ask questions · set context"]:::obs
    AD --> D["⚖️ Deciders<br/>the votes make the call"]:::good
    D --> EX["🛠️ Executers<br/>implement the decision"]:::gate
    classDef server fill:#A8E6D0,stroke:#2FA37C,stroke-width:2px,color:#0F172A
    classDef obs fill:#AED6F1,stroke:#2E86C1,stroke-width:2px,color:#0F172A
    classDef good fill:#BFEFC8,stroke:#3FA34D,stroke-width:2px,color:#0F172A
    classDef gate fill:#D7C3F2,stroke:#8E5BD0,stroke-width:2px,color:#0F172A

Figure 2: DARE as a workflow. Recommenders propose, advisors sharpen, deciders choose, executers ship.

  • Deciders are the people who actually make the call, the votes. Usually one, and deliberately few. This is the role RACI is missing, and naming it is most of the value DARE adds.
  • Advisors set context and ask the hard questions; they shape the decision without owning it. Advising is not deciding, and that distinction is what stops the room mistaking input for authority.
  • Recommenders do the analysis, explore alternatives, and bring a concrete recommendation. They drive the work that makes a good decision possible.
  • Executers implement once the call is made.

The discipline DARE forces is assigning the Decider before the conversation starts.

When everyone walks in knowing who chooses, the meeting becomes about informing that choice rather than fighting over who gets to make it. Advisors advise freely because they’re not deciding; recommenders go deep because they know a decision will follow. The ambiguity that paralyzed RACI simply evaporates.

A useful default. Keep deciders few, ideally one, keep advisors relevant rather than inviting everyone with an opinion, and make the recommender accountable for surfacing real alternatives instead of the option they already prefer.

3. The Power of Questions

DARE only works if Advisors and Deciders are good at extracting the truth, and that’s a questioning skill. Three types of question do different jobs:

---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart TD
    Q["❓ The Power of Questions"]:::gov
    Q --> CL["🔍 Clarifying<br/>make ambiguous statements clear"]:::gate
    Q --> EL["➕ Elaboration<br/>draw out more, encourage amplification"]:::server
    Q --> RF["💗 Reflection<br/>surface emotion, not just facts"]:::obs
    classDef gov fill:#E0D6F5,stroke:#9B7EDE,stroke-width:2px,color:#0F172A
    classDef gate fill:#D7C3F2,stroke:#8E5BD0,stroke-width:2px,color:#0F172A
    classDef server fill:#A8E6D0,stroke:#2FA37C,stroke-width:2px,color:#0F172A
    classDef obs fill:#AED6F1,stroke:#2E86C1,stroke-width:2px,color:#0F172A

Figure 3: Three question types. Clarify what's vague, elaborate what's thin, reflect on what's felt but unsaid.

  • Clarifying questions make ambiguous or confusing statements clear. “When you say ‘soon,’ do you mean this quarter?” They prevent decisions built on words everyone interprets differently.
  • Elaboration questions draw out more by encouraging amplification. “Tell me more about why that risk worries you.” They surface the reasoning behind a position.
  • Reflection questions focus on emotional sentiment, not information. “How does the team feel about this direction?” They catch the resistance or enthusiasm that never makes it into the data, and that quietly decides whether a decision actually sticks.

Great Advisors live in these questions. They don’t push their own answer; they make the Decider’s thinking sharper and more complete.

Most decision paralysis isn’t a lack of information. It’s a lack of clarity about who chooses.

RACI organizes work. DARE organizes the decision, and that one change, naming the Decider up front, is what gets a stalled initiative moving. Pair it with good questioning, and your meetings stop being debates about authority and start being engines for actually deciding.

Further reading