Template

Decision Record Template (DRI, context, outcome)

A concise, fillable decision record to capture context, options considered, decision rationale, owner (DRI), implementation plan, success metrics, review cadence, and related artifacts. Use to reduce re-litigation, speed implementation, and preserve institutional learning. Includes examples and guidance for product, hiring, and budget decisions.

Interactive Tool

Decision Record

Use this decision record to capture the essential information your team needs to act, learn, and revisit outcomes. A short, consistent record helps teams move forward with clarity and prevents re-litigation. Use one record per meaningful decision (product choices, hires, budget allocations, process changes, vendor selections, etc.).

When to use this: decisions that affect multiple people, teams, timelines, budgets, or risk levels; decisions you may need to review later; decisions that require a named owner and implementation plan.

Examples: Product: choose A/B test winner; Hiring: approve open senior engineer requisition; Budget: allocate Q3 marketing funds. Each example should include context, alternatives considered, rationale, owner, and metrics you will use to judge success.

Optional short identifier (e.g., DEC-2026-045) to help cross-reference this record in docs and dashboards. Leave blank to let the system or your team assign one.
A concise title that makes the decision discoverable (who/what/when/where).
Date the decision was made. Use YYYY-MM-DD for consistency.
Explain why this decision matters now, the constraints, relevant history, and the key objectives it supports. Keep this short (3–6 sentences) but specific.
List the meaningful options you considered. For each, note the main pros, cons, and estimated impact (one per line or use bullets).
State the chosen option clearly so someone reading later knows what to do next without ambiguity.
Explain why this option was chosen and the trade-offs. Include key assumptions, unresolved risks, and who accepted those risks.
Name and role of the directly responsible individual who will drive implementation and be answerable for follow-through.
High-level next steps, key milestones, owners, and an approximate timeline. Link to detailed project plans if available.
How will we know the decision succeeded? Include 1–3 measurable indicators and target values where possible.
Date to revisit this decision and its outcomes (YYYY-MM-DD). Pick a sensible cadence based on expected time-to-impact.
Names or teams consulted and a short note on whether they raised objections or offered support.
Links to meeting notes, specs, RFCs, designs, tickets, budgets, or other documents that informed the decision.
A simple assessment of the decision's risk for prioritizing review and communication.
Does this decision require formal approval?
Current approval state (if applicable).
Any additional context, follow-up tasks, or links to retrospective notes.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.