Method · Decisions
DACI: how to run it
A way to make a group decision clear before discussing it: one Driver runs the process, one Approver makes the call, Contributors give input, and the Informed are told the result.
When it helps
Use it for decisions that involve several teams and keep stalling — choosing a tool, a vendor, a direction — when it is unclear who actually decides.
When to use something else
Skip it for day-to-day decisions one person can make, and for emergencies where waiting for input would cost more than a wrong call.
How to run it, step by step
- Name the decision and the deadline5 min
- What exactly are we deciding, and by when?
- Assign the roles5 min
- One Driver, one Approver, the Contributors, the Informed.
- Lay out the options15 min
- The Driver presents the options with their pros, cons and costs.
- Hear the Contributors15 min
- Each Contributor gives their view and evidence.
- The Approver decides5 min
- The decision, the reason, and who tells the Informed.
What comes out — an example
Made up, to show the shape.
Decision. Which video tool for customer calls, by 15 March.
Driver. Ops lead. Approver. COO. Contributors. Sales, support, IT. Informed. Everyone.
Options. Keep the current tool; switch to a cheaper one; switch to one with recordings built in.
Decided. Switch to the one with recordings — support needs them for training. COO, 12 March.
Where it comes from
Atlassian includes DACI as one of the plays in its Team Playbook.
Questions
What does DACI stand for?
Driver, Approver, Contributors and Informed.
How is DACI different from RACI?
DACI is for making one decision; RACI maps who does what across many tasks.
Can there be more than one Approver?
It works best with exactly one, so it is always clear who makes the call.
Other methods
Try Meetful
Meetings that take their own notes
Free video meetings in the browser: every line of the transcript under the name of who said it, and the summary and action items when you hang up. Nothing to install — guests just open the link.