The Intent Ledger
← All articles

DACI vs RACI: Which Framework Fits Your Team?

DACI vs RACI: Which Framework Fits Your Team?

Use RACI to assign who does the work. Use DACI to settle who decides, and how, on a specific high-stakes choice. The two are not rivals so much as tools for different kinds of confusion: RACI clears up “who is doing what,” DACI clears up “who makes this call.” Most teams need RACI more often, and DACI at the few moments when a decision keeps stalling.

This guide covers what each framework is, how the roles compare, where each one breaks, and how to use them together. It also covers the part both frameworks leave out: what happens to the reasoning once the decision is made.

Theintentledger
Keep the Reason Behind Decisions
The Intent Ledger turns project conversations and feedback into source-backed records of decisions, design intent, risks, and actions.
Explore project memory

TL;DR

  • RACI (Responsible, Accountable, Consulted, Informed) is a matrix for assigning ongoing task and deliverable ownership.
  • DACI (Driver, Approver, Contributor, Informed) is a decision process for one bounded choice, with a single approver.
  • A common approach is to use DACI to reach the decision and RACI to manage the execution that follows.
  • Do not apply either to everything. Over-applying them creates bureaucratic drag.
  • Neither framework records why a decision was made. Pair them with a decision record so the rationale survives.

Table of Contents

What RACI is and what it does well

RACI is a responsibility assignment matrix. You list tasks or deliverables down the side, people or roles across the top, and mark each cell with one of four letters:

  • Responsible: does the work.
  • Accountable: owns the outcome and signs off. Ideally one person per task.
  • Consulted: gives input before the work is done, a two-way conversation.
  • Informed: is told about progress or results, a one-way update.

It is built for work that repeats or can be split into distinct steps. A studio issuing a drawing set, an agency producing a campaign, or a firm running a month-end close all have many hands touching a deliverable. A RACI chart shows who is on the hook for each piece. That is why Quire’s comparison sums it up as a framework for work, not for decisions.

If you manage client-facing professional services, a clear responsibility chart also pays off operationally. This guide to accounting workflow efficiency shows how defined handoffs reduce rework in a service business, and the same logic applies to a design studio’s production tasks. For marketing and content teams, this look at agency content workflows shows how assigned ownership at each stage keeps a pipeline moving.

What DACI is and where it came from

DACI is a decision-making framework. According to ProductPlan’s glossary, it was developed at Intuit as a variant of the RACI responsibility matrix. The roles:

  • Driver: runs the process. Gathers input, frames the options, keeps the timeline moving and makes sure a decision actually happens.
  • Approver: makes the final call. One person, not a committee.
  • Contributors: the people or teams whose knowledge feeds the decision.
  • Informed: those affected who need to hear the outcome.

Notice what changed. RACI’s “Responsible” and “Accountable” collapse into two different jobs: the Driver orchestrates, the Approver decides. That split is the point. DACI is aimed at clarifying authority for specific, bounded choices, such as “which structural system do we take to the client?” or “do we change the facade material?”

DACI vs RACI: side by side

RACI DACI
Purpose Assign ownership of tasks and deliverables Reach one decision with clear authority
Roles Responsible, Accountable, Consulted, Informed Driver, Approver, Contributor, Informed
Scope Ongoing work, many tasks One bounded choice
Who decides Not explicit. “Accountable” implies sign-off Explicit: the Approver
Who runs the process Usually no defined role The Driver
Typical artifact A matrix of tasks by person A one-page decision brief
Lifespan Lasts as long as the project phase Ends when the decision is made
Best for Deliverables with multiple producers Singular, high-stakes choices

The last row follows the rule of thumb in the Quire guide: a deliverable with multiple producers calls for RACI, while a single high-stakes choice that needs a definitive outcome calls for DACI.

Where RACI goes wrong

RACI is popular, so its failure modes are well documented. McKinsey has argued that RACI often makes things worse when organizations use it to clarify decision rights, partly because stakeholders blur “Responsible” and “Accountable.”

Three patterns show up again and again:

  1. Two letters for one person, or none at all. If nobody holds the A, nobody owns the outcome. If two people do, each assumes the other will sign off.
  2. An A without authority. When the Accountable person cannot direct the Responsible one, the issue gets escalated and the team loses time.
  3. A chart nobody opens. A 40-row matrix made at kickoff and never revisited is decoration. The frameworks stop helping when they are applied to every task.

The fix is not a better matrix. It is deciding what the matrix is for. If your real problem is that decisions drift, a task chart will not cure it.

Where DACI goes wrong

DACI has its own traps.

A Driver who changes mid-stream. Practitioners at Heinz Marketing point out that the Driver has to hold the full context of the decision from start to finish. If the role moves from step to step, context erodes at each handoff. Their advice: when accountability needs to change from step to step in a workflow, RACI fits better. When it must stay consistent throughout, DACI does.

Using it for routine work. Not every choice needs a Driver, an Approver and a brief. A DACI for “which font in the presentation” is theater. Reserve it for decisions that cross functions and carry real cost if reversed.

An Approver who is a committee. If five people must approve, you have rebuilt the problem DACI exists to solve.

Does single-point authority really speed things up?

There is a reasonable case that it does. A figure widely circulated in comparisons of these frameworks attributes to McKinsey research the finding that organizations with clear single-point decision authority decide two to three times faster than those with distributed accountability. Treat the multiple as directional rather than a guarantee for your team. The underlying logic is easy to check in your own project: count how many times the same question came up in meetings before someone settled it.

What about RAPID?

You may see a third option in the results. RAPID (Recommend, Agree, Perform, Input, Decide) is built for large cross-functional initiatives, often involving M&A or high-governance settings where several parties hold formal veto power. Quire’s guide notes it is often considered excessive for teams smaller than 50 people. A design studio or a project team of a dozen will rarely need it. Look at RAPID only if multiple functions truly can veto the outcome.

How to choose: a short decision guide

Ask three questions about the situation in front of you.

  1. Is the problem about work or about a choice? Many people producing one deliverable points to RACI. One unresolved choice points to DACI.
  2. Does the owner need to stay constant? If one person must carry context from start to finish, DACI. If ownership legitimately passes between phases, RACI.
  3. What does being wrong cost? Cheap and reversible: skip the framework and let the lead decide. Expensive and hard to undo: write the DACI.

A worked example from a design project

An architecture studio is choosing between two cladding systems for a mid-rise project. The client is sensitive to budget, the structural engineer has concerns about weight, and the project architect favors the more expensive option.

Decision stage (DACI):

  • Driver: the project architect, who gathers cost data, engineer input and precedent images.
  • Approver: the studio principal.
  • Contributors: structural engineer, cost consultant, the design lead.
  • Informed: the client team, the site team, the drafting staff.

The Driver circulates a one-page brief with the options, the trade-offs and a deadline. The Approver chooses.

Execution stage (RACI):

  • Responsible: drafting team updates details; the specification writer revises the spec.
  • Accountable: the project architect owns the revised drawing set.
  • Consulted: the engineer on connection details.
  • Informed: the client and the contractor.

The pattern matches the current advice that DACI reaches the decision and RACI manages the execution. One framework ends, the other begins.

The gap neither framework fills

Here is what a design team finds six months later. The chart says who approved the cladding change. The matrix says who updated the details. Neither says why. Was it cost? A fire-rating comment from the consultant? A throwaway remark in a client call that everybody then built on?

Both frameworks assign roles. Neither captures the reasoning, the alternatives rejected, the risks accepted or the conversation where it all happened. That matters because roles fade as people leave, and junior designers inherit tasks without knowing their origin.

The usual remedy is a decision record: a short, structured entry for each significant decision. Our guide to the eight fields a record of decision should capture lists what to write down. If you want a lightweight format to start with, see the articles tagged decision log template. For work driven by critique rounds, a six-field decision audit trail fits well, and the triad and log approach to collaborative design decisions shows how to start the conversation before the Driver writes the brief.

Our perspective: roles tell you who, records tell you why

We build project memory software for design teams, so we see the aftermath of both frameworks. Teams that adopt DACI usually get faster at deciding. Teams that adopt RACI get clearer about task ownership. Then, months later, they hit the same wall: someone asks why a choice was made and nobody can reconstruct it.

Our view is that the Driver’s brief is the best raw material a team has for a decision record, and it is usually thrown away. The reasoning happens in meetings, critique sessions, email threads and client calls. By the time the Approver says yes, the rationale is scattered across five places and two memories.

That is why we treat a decision as incomplete until it is traceable to the conversation it came from. A framework tells you who held the pen. A source-backed record tells the next person why the pen moved that way. We would rather a team run a simple RACI and keep honest decision records than run elaborate frameworks and lose the reasoning.

A practical rule we use: if a decision was important enough to need a Driver, it is important enough to leave a record with a link back to its source.

, Rajas

Keeping the rationale: where The Intent Ledger fits

The Intent Ledger turns meeting notes, transcripts, critique feedback and client comments into ILM Records: structured, source-backed entries for decisions, design intent, risks, actions, commitments and unresolved questions. Each one traces back to the conversation it came from, so the output of a DACI process, and the actions that follow it in RACI, stay connected to their reasoning.

You can start small with a one-off pack: Working Set at $12, Project Record at $29, Practice Memory at $59 or Studio Ledger at $119. Monthly plans are Working Memory at $29 per month, Living Record at $79 per month and Shared Ledger at $149 per month. See the full list on the pricing page, or read more on the Intent Ledger site.

If you also need to tie drawings and requirements to those decisions, see how to link drawings to decisions with ten fields mapped to ISO 19650 and our piece on the requirements traceability matrix.

A simple way to start this week

  1. List your open decisions. Pick the two or three that have been discussed more than once without closure.
  2. Name a Driver and an Approver for each. One person each. Write them down.
  3. Set a decision date. The Driver circulates a one-page brief with options and trade-offs before it.
  4. Record the outcome and the reason. Link it to the meeting or message where it was settled.
  5. Switch to RACI for delivery. Assign who does, who owns, who is consulted and who is told.
  6. Review at the next design review. Our three-phase design review checklist is a good place to confirm decisions were preserved.

Keep it proportionate. If the process takes longer than the decision would have, you have over-engineered it.

FAQ

Is DACI a replacement for RACI?

No. They answer different questions. RACI assigns ownership of ongoing tasks, while DACI structures one decision with a single approver. Many teams use DACI to reach a decision and RACI to carry it out.

What is the difference between Responsible and Accountable in RACI?

Responsible is the person or people doing the work. Accountable is the one who owns the outcome and signs off, ideally a single person per task. The two are often conflated, which is one of the commonly cited weaknesses of RACI, and the Accountable person needs real authority over the Responsible one.

Is the RACI matrix outdated?

Not for assigning task ownership, where it remains useful. It struggles when used to settle decision rights, which is where McKinsey argues it often creates more confusion than clarity. Use it for deliverables and use a decision-focused tool for decisions.

When should I use DACI instead of RACI?

Use DACI for a single, high-stakes choice where authority is unclear or decisions keep stalling. Choose RACI when a deliverable involves many producers across distinct steps. If neither problem exists, you may not need a framework at all.

Can a small team or freelancer use these frameworks?

Yes, in a lighter form. A freelancer can treat the client as Approver and themselves as Driver, then keep a short record of each decision and its reason. You will rarely need a full matrix, and RAPID is generally overkill below about 50 people.

Sources

DACI vs RACI: Which Framework Fits Your Team?: The Intent Ledger Blog