Framework · DesignOps & capacity · 3 min read
DACI
Four roles (Driver, Approver, Contributors, Informed) that you name before a cross-domain decision is discussed, so everyone knows who decides and who only gives input.
Moves the decision forward: gathers input, prepares options, keeps the date.
Typically: the design-system designerMakes the final call. Exactly one person, named first.
Typically: the UX leadGive knowledge and input before the decision. They don't vote.
Typically: domain designers, frontend leadHear the decision once it is made, with the reason.
Typically: all product managersUse it when
- A decision touches several product teams, for example a new component standard in the design system.
- The same topic keeps coming back to meetings because nobody is sure who has the final word.
- You are delegating a decision to a designer and want to make clear what they own and what you still approve.
How to use it
- Write the decision as one question. Make it specific and add a due date: "Which data table pattern do all products use from next quarter?" Output: a one-line decision statement with a date.
- Name the Approver first. Pick one person who has the authority and will live with the result. If two people both want to approve, escalate until one person owns it. Output: one name in the Approver field.
- Name the Driver, Contributors and Informed. The Driver moves the work forward and is often not the most senior person. Contributors are the people whose knowledge you need. Informed are the people affected by the result. Output: a filled DACI table, shared before the first meeting.
- Collect input, then present options. The Driver gathers input from Contributors and brings 2–3 options with pros and cons. Contributors give input; they don't vote. Output: an options list with trade-offs.
- Decide and record it. The Approver decides on or before the due date. The Driver writes down the decision, the reason and what was not chosen, then tells the Informed group. Output: a recorded decision in a place everyone can find. About 15 minutes.
Worked example
An internal operations platform with 6 product teams. Each team built its own data table, and users switch between three different ways to sort and filter. The UX lead sets up a DACI before the topic goes to the design-system council.
| Field | Filled in |
|---|---|
| Decision | Which data table pattern do all six products adopt? |
| Due date | End of this month |
| Driver | Design-system designer |
| Approver | UX lead (one person) |
| Contributors | Designers from 3 domains, frontend lead, accessibility specialist |
| Informed | All product managers, support team |
| Options considered | A: keep team tables, align only the visuals. B: one shared table component with sort, filter and bulk actions. C: shared component for new screens only. |
| Decision | Option B for new screens now; existing screens move over within two quarters. |
| Reason | Users work across products every day. One pattern removes relearning and duplicate maintenance. |
| Not chosen, and why | Option A keeps three interaction models. Option C delays the benefit for the most-used screens. |
Watch out for
- More than one Approver. "The UX lead and the head of product approve together" is two approvers. Pick one, and make the other a Contributor.
- Contributors who think they vote. If you count opinions, you have a committee, not a DACI. Say at the start that input shapes the options, and the Approver decides.
- Filling it in after the fight. DACI helps when roles are named before the discussion. Set it up at the start of the work, not when people already disagree.
- No record of the decision. If the outcome lives only in a meeting, it will be reopened. Write it down and tell the Informed group.
Template
Copy this into your wiki page or decision log and fill it before the first meeting.
Decision:
Due date: Status: Not started / In progress / Decided
Driver:
Approver (one person):
Contributors:
Informed:
Options considered:
A: Pros: Cons:
B: Pros: Cons:
C: Pros: Cons:
Decision:
Reason:
Not chosen, and why:
Decided on: Informed on: