Daci

DACI is a decision-making framework that assigns clear roles to everyone involved in a decision: Driver, Approver, Contributors, and Informed. By making explicit who drives the process, who has final say, who provides input, and who needs to know the outcome, DACI eliminates the ambiguity that often paralyzes teams or leads to decisions being revisited endlessly.

Why it matters

Decisions stall when nobody knows who owns them. They get relitigated when people feel excluded. They drag on when everyone thinks they have veto power. DACI solves these problems by creating clarity before the decision-making process begins, not after frustration sets in.

For product managers, DACI is particularly valuable because product decisions typically involve multiple stakeholders with competing interests. Engineering wants technical excellence, design wants user experience, sales wants customer requests, leadership wants strategic alignment. Without clear decision rights, these tensions either explode into conflict or quietly undermine whatever gets decided.

The four roles

Driver - The person responsible for driving the decision to completion. They gather input, frame the decision, set timelines, and ensure the process moves forward. The Driver doesn't make the final call but owns the process. There should be exactly one Driver.

Approver - The person with final decision authority. When input has been gathered and options weighed, the Approver makes the call. Like the Driver, there should typically be one Approver to avoid deadlock, though some organizations allow two for major decisions.

Contributors - People whose input and expertise should inform the decision. Contributors provide information, analysis, and recommendations, but they don't have veto power. There can be many Contributors, but including too many slows things down.

Informed - People who need to know the outcome but don't participate in the decision process. They receive communication after the decision is made. This group is often larger than people initially think.

When to use daci

DACI adds value when decisions are consequential enough to warrant the overhead of explicit role assignment. It's particularly useful for:

For quick, routine decisions within a single team, DACI is overkill. A product manager deciding which bug to fix first doesn't need a framework. But deciding the roadmap for next quarter, choosing a technology platform, or determining pricing strategy - these benefit from DACI's structure.

Daci vs. raci

DACI and RACI are often confused because they share letters and serve similar purposes. The key difference is their focus.

RACI helps clarify who does what work on a project. DACI helps clarify who decides what on a specific decision. Many teams use both: RACI for ongoing work allocation, DACI for key decision points.

Making daci work

Several practices help DACI deliver on its promise.

Assign roles early. The value of DACI comes from clarity before the process begins. Assigning roles mid-decision, especially after positions have hardened, creates resentment rather than alignment.

Keep Contributors focused. The temptation is to include everyone who might care. But more Contributors means slower decisions and diluted input. Include people with genuine expertise or stake, not everyone who might have an opinion.

Respect the Approver's authority. Contributors provide input; they don't get to relitigate after the Approver decides. If the wrong person is Approver, that's a role assignment problem to fix for next time, not a reason to undermine this decision.

Document the decision. Record not just what was decided but who played each role and what input was considered. This creates accountability and helps improve future decisions.

Match the Approver to the stakes. The Approver should have authority commensurate with the decision's impact. A feature prioritization decision might have a product manager as Approver. A major pivot might require a VP or executive.

Common pitfalls

Too many Approvers defeats the purpose. If three people have to agree, you've replaced individual accountability with committee paralysis. When organizations insist on multiple Approvers, DACI degrades into the same slow consensus process it was meant to replace.

Driver without authority creates frustration. The Driver needs enough organizational standing to move the process forward, schedule meetings, and hold Contributors accountable for input. A junior person driving a senior decision often struggles.

Skipping the Informed causes downstream problems. People left out of communication feel blindsided and may resist implementation. Taking time to identify and inform affected parties pays off in smoother execution.

Using DACI for everything creates framework fatigue. Reserve it for decisions that genuinely benefit from role clarity. Overuse makes people roll their eyes rather than engage with the process.

When used appropriately, DACI transforms decision-making from a source of organizational friction into a clear, efficient process. The framework's simplicity is its strength - four roles, clearly assigned, consistently applied.