DACI Decision Framework

Overview

Clarify decision ownership and reduce decision thrash using the DACI framework (Driver, Approver, Contributor, Informed). Unlike RACI which focuses on task responsibility, DACI is purpose-built for product decisions -- who drives the decision to closure, who has veto power, who provides input, and who needs to know.

The four roles in brief: Driver (exactly one, drives to closure), Approver (1-2 max, holds veto), Contributor (input without veto), Informed (notified, not consulted). Build a chart by mapping current state, finding pain points, designing target state, and rolling out a 30/60/90 transition. See the playbook reference for role rules, the 7-step build sequence, and health metrics.

When to Use

• New team formation -- A new cross-functional group needs clear decision-making roles.
• Decision thrash -- Decisions stall because nobody knows who has authority.
• Scaling teams -- Growth creates ambiguity about who owns which decisions.
• Post-incident -- A failed launch or missed deadline reveals unclear ownership.
• Reorg transitions -- Role changes create governance gaps.

When NOT to Use