Decision Roles & Routines — Who Decides What (Cheat Sheet)

Why this matters

Fast, fair, and learnable decisions require clear role names plus simple routines that teams can actually use. This cheat sheet helps teams stop debating ownership and start producing transparent decisions that can be reviewed and improved.

Core decision roles (short, actionable)

• Decider — The person or role with final authority to choose. Meeting behavior: asks clarifying questions, chooses among viable options, announces next steps. Evidence expected: clear decision record and acceptance criteria. Transfer rule: responsibility can be delegated formally (see Transfer rules).
• Advisor — Provides expertise, trade-offs, risk notes, and alternatives. Meeting behavior: brings concise evidence, states recommended option and reasons. Evidence expected: assumptions, constraints, data sources. Advisors do not veto.
• Contributor — Supplies work, data, or recommendations; helps evaluate options. Meeting behavior: prepares required inputs, tests or pilots options where needed. Evidence expected: completed analyses, prototypes, or user feedback relevant to the decision.
• Steward — Guards consistency with standards, policy, and long-term strategy (may be a role rather than a person). Meeting behavior: flags conflicts with standards, suggests mitigations. Evidence expected: policy references, impact notes. Steward can request escalation if decision conflicts with governance boundaries.

Meeting recipes — quick patterns to use

Escalation paths — keep them simple and visible

Define a short chain (local owner → team lead → functional leader → steering committee). Add clear triggers for escalation, such as:

• Legal, safety, regulatory conflict
• Impact above a defined cost or schedule threshold
• Significant cross-team dependency or unresolved risk

Each escalation step should state who must be informed, the expected turnaround time, and what information to include (decision brief, evidence, impact estimate).

Decision record — a minimal template

Store a short, searchable record for every meaningful decision. Use this four-line template:

• ID / Title: Short name and date
• Decider & Owner: Who decided and who will execute
• Outcome & Rationale: Chosen option, key evidence, major trade-offs
• Next Steps & Review: Implementation owner, deadlines, and a review date (if decision should be revisited)

20-minute RACI-to-Decision mapping exercise (run it now)

1. Prep (2 minutes): Pick 5–8 common decisions your team makes (e.g., release approval, vendor selection, feature prioritization, hiring, budget reallocation).
2. Map (12 minutes): For each decision, quickly assign the Decision Role (Decider / Advisor / Contributor / Steward). Timebox 90 seconds per decision. Use a shared board or spreadsheet with columns: Decision, Decider, Advisors, Contributors, Steward, Escalation Trigger.
3. Confirm (6 minutes): Read the list aloud, surface any objections, and resolve them by either assigning the role now or escalating to the team lead. Record any items needing a formal governance rule.

Outcome: A one-page ownership map and a short list of governance rules to add to team norms.

Tips, common traps, and maintenance

• Use role names, not people's names in lasting governance ("Product Lead" vs "Alicia") to avoid brittle ownership when people change.
• Avoid undecided consensus. If consensus isn’t required, the decider should choose based on criteria; consensus can be a helpful advisory input but shouldn’t block a decision unless stated.
• Timebox advisory input and document key assumptions so future reviewers understand the context.
• Keep decision records short and linked to evidence (documents, data, customer feedback). Long rationales belong in attachments, not the record summary.
• Schedule periodic review for decisions that depend on uncertain assumptions (30, 60, 90 days as appropriate).

Signals your decision processes are healthy

• Decisions are made within the promised timescale.
• Decision records exist and are searchable.
• Team members know who to consult and who decides.
• Escalations are rare and follow the stated rules.

Use this cheat sheet as a living team artifact. Copy it into your team playbook, adapt the role names and escalation thresholds, and run the 20-minute mapping exercise once a quarter or when team membership changes.