Decision-Making Framework — Lightweight decision rights and a DACI-lite template

Confusion about who decides is one of the most common causes of delay and rework. A lightweight approach clarifies four roles for each decision: Driver, Approver, Contributors, and Informed (DACI). You don’t need formal bureaucracy—use the pattern selectively for unclear or cross-team decisions.

Roles explained

• Driver — The person responsible for driving the work, synthesizing input, and drafting a recommended decision.
• Approver — The person who makes the final call (may be a manager or product owner).
• Contributors — People who provide input, data, or analysis required to reach a good decision.
• Informed — People who should be told the outcome and any impacts after the decision.

When to use DACI-lite

• Cross-functional trade-offs (e.g., prioritizing a feature that affects ops and support).
• Decisions with budget or resource implications.
• When prior decisions repeatedly get revisited or overturned.

Quick template to record a decision (use one page in your team wiki)

• Decision: Short description.
• Driver: Name.
• Approver: Name.
• Contributors: Names/roles.
• Context and constraints: Key facts, timeline, and risks.
• Options considered: 2–3 succinct alternatives and pros/cons.
• Decision and rationale: What was chosen and why.
• Next steps and owners: Who does what by when.

Practical tips

• Don’t use DACI for low-risk, everyday choices—save it for cross-cutting or high-impact decisions.
• If the approver rejects a recommendation, require a short written rationale to preserve learning and avoid repeated rework.
• Record decisions publicly to reduce repeated debates and make onboarding easier.

Clear decision rights reduce friction and create faster execution. Use this DACI-lite pattern as a simple guardrail for the decisions that most often slow your team down.