DACI

Use when

• A decision needs an owner and RAPID is heavier than the situation warrants.
• The problem is drift rather than disagreement.
• Several decisions of this type recur and need a standard shape.

Do not use when

• The disagreement is substantive. Role clarity will not resolve a genuine conflict about what to do.
• There is genuinely more than one approver with an independent veto — then RAPID’s separation is worth the overhead.

Inputs required

• A decision
• A deadline
• The people involved

Procedure

1. 01

   Name the driver

   One person responsible for reaching a decision by the date. They do not necessarily decide; they own that a decision happens.

2. 02

   Name the approver

   One person with sign-off. If two are proposed, either merge the decision or split it into two decisions.

3. 03

   Name contributors

   Those whose input is genuinely required. Ruthlessly short — every contributor is a scheduling dependency.

4. 04

   Name the informed

   Told after the decision. Being informed is not being consulted, and conflating the two is the most common source of resentment about a decision.

5. 05

   Set the date

   A decision without a date is a discussion. The driver’s job is that date.