Decision latency kills projects. These are the frameworks I reach for—and when I avoid them.
RACI (Responsible, Accountable, Consulted, Informed)
- Best for: steady-state roles and handoffs; clarifying who does vs. who approves.
- Watchouts: too granular RACI charts become wallpaper. Keep it to major deliverables and decisions.
- Tip: limit Accountable to one name; assign an escalation path.
DACI (Driver, Approver, Contributors, Informed)
- Best for: one-time decisions (architecture choice, vendor selection).
- Watchouts: “Driver” must have time and influence; otherwise decisions stall.
- Tip: set a decision deadline and criteria before debating options.
RAPID (Recommend, Agree, Perform, Input, Decide)
- Best for: cross-functional decisions with real risk; emphasizes who decides and who must agree.
- Watchouts: overused “Agree” creates veto power—limit to truly impacted groups.
- Tip: document the Recommend/Decide path in the decision log to avoid relitigation.
How I pick
- Is this repeatable work? RACI.
- Is this a specific decision with options? DACI.
- Is this complex and cross-functional? RAPID.
Whatever you choose, publish the roles, decision criteria, and deadline. Put the result in a decision log with owners and follow-ups. Clarity beats consensus theater every time.