DAVCI Decision Rights
Define clear decision rights using the DAVCI framework.
When to Use
When you need to clarify who decides, approves, and must be consulted on a decision.
The Framework
| Role |
Definition |
Rules |
| D - Decider |
Single person accountable for outcome |
Exactly one per decision |
| A - Approver |
Can override the Decider |
Optional; cannot be the D |
| V - Veto |
Can block for specific domain |
One per domain; time-boxed |
| C - Consulted |
Has input before decision |
Keep to 5 or fewer |
| I - Informed |
Needs to know after decision |
Keep targeted |
The Process
1. Define the Decision Object
Be specific about what's being decided:
- Clear title
- Concrete deadline
- Decision type (Strategy, Scope, Design, Technical, Process, Risk, Commercial)
2. Assign Roles
Decider (D):
- Who is accountable for the outcome?
- Must be one person only
Approver (A):
- Does D need air cover for risk/budget/politics?
- If yes, name person one level up
Veto (V):
- Which domains apply? (Security, Legal, Privacy, Brand, Compliance)
- One person per domain
- Set veto window (default: 48 hours)
Consulted (C):
- Who has unique information to improve the decision?
- Cap at 5; merge by role if needed
Informed (I):
- Who must act after or needs awareness?
- Keep targeted to those who need it
3. Add Decision Metadata
- Deadline: Date and time
- Escalation: If blocked 24h, escalate to whom?
- Success test: One checkable sentence
- Comms plan: Channel, audience, timing
Output Format
Decision: [title]
Deadline: [date/time]
Type: [Strategy/Scope/Design/Technical/Process/Risk/Commercial]
D: [name, role]
A: [name, role] or None
V: [Domain - name, window hours]
C: [role/name]; [role/name]
I: [role/name]; [role/name]
Escalation: [name, role]
Success test: [single checkable sentence]
Comms: [channel + audience + timing]
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
1---2name: davci3description: Define clear decision rights - Decider, Approver, Veto, Consulted, Informed. Use when clarifying who decides.4---56# DAVCI Decision Rights78Define clear decision rights using the DAVCI framework.910## When to Use1112When you need to clarify who decides, approves, and must be consulted on a decision.1314## The Framework1516| Role | Definition | Rules |17|------|------------|-------|18| **D - Decider** | Single person accountable for outcome | Exactly one per decision |19| **A - Approver** | Can override the Decider | Optional; cannot be the D |20| **V - Veto** | Can block for specific domain | One per domain; time-boxed |21| **C - Consulted** | Has input before decision | Keep to 5 or fewer |22| **I - Informed** | Needs to know after decision | Keep targeted |2324## The Process2526### 1. Define the Decision Object2728Be specific about what's being decided:29- Clear title30- Concrete deadline31- Decision type (Strategy, Scope, Design, Technical, Process, Risk, Commercial)3233### 2. Assign Roles3435**Decider (D):**36- Who is accountable for the outcome?37- Must be one person only3839**Approver (A):**40- Does D need air cover for risk/budget/politics?41- If yes, name person one level up4243**Veto (V):**44- Which domains apply? (Security, Legal, Privacy, Brand, Compliance)45- One person per domain46- Set veto window (default: 48 hours)4748**Consulted (C):**49- Who has unique information to improve the decision?50- Cap at 5; merge by role if needed5152**Informed (I):**53- Who must act after or needs awareness?54- Keep targeted to those who need it5556### 3. Add Decision Metadata5758- **Deadline:** Date and time59- **Escalation:** If blocked 24h, escalate to whom?60- **Success test:** One checkable sentence61- **Comms plan:** Channel, audience, timing6263## Output Format6465```66Decision: [title]67Deadline: [date/time]68Type: [Strategy/Scope/Design/Technical/Process/Risk/Commercial]6970D: [name, role]71A: [name, role] or None72V: [Domain - name, window hours]73C: [role/name]; [role/name]74I: [role/name]; [role/name]7576Escalation: [name, role]77Success test: [single checkable sentence]78Comms: [channel + audience + timing]79```8081## When Not to Use8283Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
itseffi