Better decisions. More thoughtful work.

Use DACI to Separate the Decision Driver from the Approver

Four distinct coloured cards arranged around a blank decision worksheet on an office table.
AI-generated photographic illustration; not documentary photography.

A team can agree that someone will “lead the decision” and still disagree about whether that person may make it. DACI separates the work of moving a decision forward from the authority to approve the outcome.

In Atlassian’s DACI framework, the Driver coordinates the process, the Approver makes the decision, Contributors provide relevant input, and the Informed group receives the outcome. Naming those roles is useful only if the actual authority and working arrangements match them.

Try it on one bounded decision

Imagine a team choosing the date for a customer workshop. The Driver gathers availability, venue options and constraints. The Approver is the person authorised to commit the team to a date. Contributors might include the customer lead and event coordinator. The Informed group includes people who need the final date for their own planning.

This does not mean every contributor votes, or that the Driver must persuade everyone to prefer the same option. It means the decision has an understandable route from evidence to approval.

Before gathering opinions

Write the question, the deadline and the constraints. “Choose a workshop date within the agreed month and budget” is more manageable than “fix the event plan.” Confirm the Approver has the authority needed; a name in a template cannot create it.

Before closing the decision

Record the selected option, the important reasons and any unresolved follow-up. Tell contributors what happened to their input. If the decision is deferred, give the reason and next review point rather than leaving the record looking complete.

Keep the framework proportionate. A small reversible choice may need only a few lines, while a consequential decision may need supporting documents and formal approvals beyond DACI.

Review the process if the Driver becomes an unofficial approver or every contributor is treated as a veto holder. Those patterns recreate the ambiguity the roles were meant to reduce.

The most useful result is a record that a colleague can read later and understand: what was decided, who could decide it, and what evidence was considered at the time.