RACI vs DACI: Choosing the Right Framework in Project Manager Interviews
RACI and DACI look similar and solve different problems. Here is what each letter means, why one is for executing work and the other is for making decisions, and how to pick the right one in an interview answer.
By The Cala Voice Team ·Two of the most common role-clarity frameworks a Project Manager (PjM) is expected to know are one letter apart, and candidates constantly conflate them. RACI and DACI both assign people to a project so nobody assumes someone else has it covered. But they answer different questions. RACI clarifies who does the work and who owns the outcome. DACI clarifies how a specific decision gets made and who has the final say. Reaching for the wrong one in an interview signals you have used the acronyms without understanding what each is actually for.
The distinction is simple once named: RACI is for executing work across a project, DACI is for driving a single decision to a conclusion. An interviewer who asks how you would clarify roles on a project, or how you would break a stalled decision, is often testing whether you know which of the two the situation calls for.
RACI: Who Does the Work
RACI assigns four roles to each task or deliverable in a project.
Responsible. The people who actually do the work. There can be several Responsible people on one task. This is the "hands on keyboard" role.
Accountable. The single person answerable for the task being done correctly. There is exactly one Accountable person per task, and this is the discipline that makes RACI worth using. Accountability that is shared is accountability that is absent.
Consulted. The people whose input is sought before the work is done or a decision within the task is made. Two-way communication: they give feedback, and it is expected to be incorporated.
Informed. The people kept up to date on progress or completion. One-way communication: they need to know, but their input is not solicited.
The value of RACI is that it makes the seams explicit across an entire project. It surfaces the two failure modes that quietly kill delivery: a task with no Accountable owner, which drifts because everyone assumes someone else has it, and a task with several Accountable people, which stalls because no one can move without the others. Running the grid forces exactly one Accountable per row, which is the whole point.
DACI: How a Decision Gets Made
DACI is not about executing a project. It is about resolving one decision cleanly, and its four roles are built for that narrower job.
Driver. The one person responsible for moving the decision forward: gathering the options, running the process, and keeping it from stalling. The Driver does not necessarily decide; they make sure a decision happens.
Approver. The single person who makes the final call. Naming exactly one Approver is what stops a decision from dying in a committee where everyone has an opinion and no one has authority.
Contributors. The people who provide input, analysis, or expertise to inform the decision. Their voice is heard but they do not decide.
Informed. The people told the decision once it is made, so they can act on it.
DACI exists because decisions stall in a different way than work does. Work stalls when no one owns it. Decisions stall when everyone owns them, when a room full of stakeholders debates without anyone empowered to end the debate. Naming a single Approver resolves exactly that ambiguity. There is a full treatment of how this plays out at scale in the DACI framework for cross-team decisions, which is where it earns its keep in complex organizations.
When to Use Which
The clean way to choose, and to say it in an interview, is by the question in front of you.
Use RACI when the problem is execution: a project with many tasks and unclear ownership, where things are falling through the cracks or being duplicated. RACI maps roles across the whole body of work. It is the default for a Project Manager because delivery is mostly about who owns what.
Use DACI when the problem is a decision: a specific choice that is stuck, contested, or being made by default because no one will own the call. DACI does not map a whole project; it resolves one decision. It is the tool for the meeting that keeps ending without a conclusion.
They also compose. On a real project, RACI governs the ongoing work, and DACI gets invoked for the handful of consequential decisions that need a clean process. A candidate who explains that RACI is the project-wide operating layer and DACI is the decision-specific tool, rather than treating them as competing alternatives, is demonstrating real fluency.
How RACI and DACI Show Up in Interview Questions
Interviewers ask scenarios that reward picking the right framework, not reciting both.
Typical questions: "A project keeps having work fall through the cracks between teams. How do you fix it?" Or "A key decision has been stuck in meetings for three weeks. What do you do?"
What a strong answer does:
For the cracks-in-execution problem, it reaches for RACI, assigns exactly one Accountable person per deliverable, and names that the failure is either missing or duplicated accountability. For the stuck-decision problem, it reaches for DACI, names a single Approver to end the debate and a Driver to run the process, and distinguishes the people who contribute input from the one who decides. Crucially, it picks the framework that fits the problem rather than listing both, and it can say why.
What a weak answer does: uses the two interchangeably, or applies RACI to a stalled decision, where mapping who is Responsible does nothing because the problem is that no one is empowered to decide. That reads as someone who memorized the letters without internalizing what each solves.
Common Mistakes
Conflating Accountable and Approver. RACI's Accountable owns a task's outcome. DACI's Approver makes a decision. Different roles for different problems.
More than one final owner. Both frameworks depend on a single point of accountability: one Accountable in RACI, one Approver in DACI. Naming two defeats the purpose of either.
Using RACI on a decision. A stalled decision is not an ownership-of-work problem. Mapping Responsible parties will not unstick it; naming an Approver will.
Treating them as rivals. They operate at different layers. The strongest answers use RACI for the project and DACI for the decisions inside it.
RACI and DACI in a Project Manager Interview
RACI is the more common of the two for a Project Manager, because delivery is mostly a question of who owns what, but knowing when to switch to DACI is what signals range. Both pair with the RAID log: a dependency or issue surfaced in the RAID log often needs a clear owner, and naming who is Accountable or who is the Approver is how you turn a tracked risk into an actioned one. Picking the right framework for the problem, holding to a single point of accountability, and knowing the two compose rather than compete is a strong signal that you manage clarity by design.
For the full interview process this framework fits into, What Is a Project Manager Interview? Complete Overview for First-Timers covers every stage of the loop and what each round tests.
Cala Voice runs you through execution scenarios built around exactly this kind of role and decision clarity, so you can practice choosing between RACI and DACI out loud before it comes up in a real interview.