# DACI: [Question we're trying to answer]? **Status:** Not started / In progress / Decided **Impact:** High / Medium / Low **Due date:** [Date] ## People | Role | Name | |---|---| | Driver (runs the process, gets a decision by the date) | | | Approver (one person only) | | | Must agree (veto for must-meet requirements, such as legal or security; use sparingly) | | | Contributors (voice, no vote) | | | Informed (told the outcome afterward) | | ## Background [One or two sentences: why this decision, why now.] ## Relevant data [Metrics, eval results, customer evidence, incident reviews, cost. Link sources.] ## Decision factors 1. [Factor, and how it will be weighed] 2. 3. ## Options considered | Option | Description | Pros | Cons | Resources and cost | Must-agree requirements met? | |---|---|---|---|---|---| | A | | | | | | | B | | | | | | | C | | | | | | ## Pre-wiring log | Contributor | Date | Position | Concern raised | How the options changed | |---|---|---|---|---| | | | | | | ## Outcome [Decision, decided by (Approver) on (date). Reason in one paragraph. Options rejected and why.] ## Action items | Action | Owner | Due | |---|---|---| | | | | ## Disagreements recorded [Who disagreed, on what, and their confirmation that they commit to the decision.] Format after Atlassian's DACI play, with a "Must agree" role borrowed from Bain's RAPID.