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.

When to Use

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

When NOT to Use

• For task assignment or project execution (use RACI instead).
• For individual contributor work allocation (use sprint planning).
• When decisions are truly one-person (no governance overhead needed).

DACI Role Definitions

Key DACI Principles

1. Every decision has exactly one Driver. If two people are driving, nobody is driving.
2. Approvers have veto power. Limit to 1-2 to avoid gridlock.
3. Contributors influence but don't block. Their input is valued but the Driver decides how to use it.
4. Informed means notified, not consulted. Don't confuse notification with input.
5. DACI is about decisions, not tasks. Map decisions, not work items.

Building a DACI Chart

Step 1: Identify the Working Group

Define the team, business unit, or cross-functional group this DACI covers.

Step 2: List Job Titles / Roles

Enumerate all roles involved in product decisions. Common roles:

• Executive Management
• Product Manager
• Product Owner
• Engineering Lead
• UX / Design Lead
• Product Marketing
• Scrum Master
• Sales & Marketing
• Customer Support / Professional Services
• Legal / Compliance

Step 3: Define Decisions

List the key decisions this group makes. Common product decisions:

Step 4: Build Current-State DACI

Map how decisions are made today (not how you want them to be made):

Rules:

• Each row has exactly one

  D

  .
• Each row has 1-2

  A

  maximum.
• Use

  D

  ,

  A

  ,

  C

  ,

  I

  , or blank only.
• Add Notes column for non-obvious assignments.

Step 5: Identify Pain Points

From the current-state chart, identify common failure patterns:

Step 6: Design Target-State DACI

Based on pain points, redesign decision ownership:

• Ensure every row has exactly one D.
• Reduce Approvers to 1-2 per decision.
• Move chronic blockers from A to C or I.
• Add missing Contributors.
• Document changes in Notes column.

Step 7: Create Transition Plan

DACI Health Metrics

Track these metrics to monitor governance effectiveness:

Integration with Other Skills

• Use

  create-prd/

  to document decisions made via DACI in PRD Section 2 (Contacts).
• Use

  identify-assumptions/

  to surface assumptions about decision authority.
• Use

  brainstorm-okrs/

  to align DACI decisions with quarterly objectives.
• Use

  summarize-meeting/

  to capture decision outcomes in meeting notes.

Troubleshooting

Success Criteria

• 100% of recurring product decisions have a DACI row with exactly one Driver
• Decision cycle time reduced by 30%+ after DACI implementation
• <10% of decisions reversed within 30 days of being made

• 80% of team members can identify the Driver for any given decision

• DACI chart reviewed and updated at least quarterly

Scope & Limitations

In Scope: DACI chart creation, current-state mapping, target-state design, transition planning, governance health metrics, pain point identification, decision ownership clarity.

Out of Scope: Task assignment (use RACI), project execution tracking (use sprint planning), individual performance management, organizational design beyond decision governance.

Important Caveats: DACI works best when leadership commits to respecting the framework. Without executive buy-in, Drivers may lack the authority to actually drive decisions. Start with 3-5 high-impact decisions rather than trying to map everything at once.

Integration Points

create-prd/

identify-assumptions/

brainstorm-okrs/

summarize-meeting/

senior-pm/

References

• Productside DACI guidance for product teams
• Inspired by the DACI framework used at Intuit and other product-led organizations