# DACI

A decision-role framework that names a Driver, Approver, Contributors, and Informed participants for an important choice.

- Type: framework
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/daci/>)

## What it means

DACI is a lightweight framework for organizing a decision. The Driver manages the process and gathers evidence; the single Approver makes the final call; Contributors provide relevant knowledge; and Informed participants receive the outcome. It is designed for decisions, not for assigning every task in a delivery plan.

## Why it matters

Cross-functional product decisions often stall because nobody owns the process, consultation has no boundary, or several leaders assume approval authority. DACI separates coordination from final authority, giving contributors a clear channel while creating an accountable endpoint.

## When to use it

Use DACI for consequential, time-bounded choices with several interested functions, such as selecting a target segment, changing packaging, or choosing a platform. Skip it for reversible everyday judgments that a capable team can make directly.

## How it works

1. Write the decision question, constraints, deadline, and success criteria before naming roles.
2. Assign one Driver to run the process and one Approver to make the final decision.
3. Select Contributors for necessary expertise, not as a courtesy list.
4. Collect evidence and recommendations in a shared decision document.
5. Have the Approver decide, record the rationale, and inform affected people.
6. Revisit only when a stated assumption fails or material new evidence appears.

## A practical example

A collaboration product must choose whether to build native transcription or integrate a vendor. The product manager drives the analysis, the product vice president approves, engineering, security, finance, and research contribute, and sales and support are informed once the rationale and transition plan are recorded.

## Where it breaks

Role labels do not create good evidence or psychological safety. A powerful Approver may dismiss expertise, while an overloaded Driver may turn consultation into paperwork. DACI can also add ceremony when the choice is small, easily reversible, or already delegated.

## Common mistakes

- Naming more than one Approver.
- Making the Driver responsible for deciding by default.
- Listing everyone as a Contributor.
- Starting discussion without a precise decision question or deadline.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/daci/#visualization-daci>)

## Sources

1. [DACI: A Decision-Making Framework](<https://www.atlassian.com/team-playbook/plays/daci>) — Atlassian Team Playbook · Framework guide
2. [Four Ways to Better Team Decision Making](<https://www.atlassian.com/team-playbook/examples/making-decisions>) — Atlassian Team Playbook · Practice guide

## Related topics

- [Decision Rights](<https://wiki.soroush.uk/topic/decision-rights/>)
- [RACI](<https://wiki.soroush.uk/topic/raci/>)
- [Stakeholder Management](<https://wiki.soroush.uk/topic/stakeholder-management/>)
