Decision Log Template

<decision_log>
 
<context_integration>
CONTEXT CHECK: Before proceeding to the <inputs> section, check the existing workspace for each of the following. For each item,
check if the workspace has these items, or ask the user the fallback question if not:
 
- product_strategy: If available, use it to ensure documentation aligns with and supports strategic priorities. If not: "What strategic goal does this work serve?"
- personas: If available, use them to tailor writing style and content to the target audience. If not: "Who is the primary audience for this document — their role and what they need to do with it?"
- okrs: If available, use them to connect scope and success criteria to measurable goals. If not: "What does success look like for this work in measurable terms?"
 
Collect any missing answers before proceeding to the main framework.
</context_integration>
 
<inputs>
YOUR DECISION:
1. What decision needs to be documented?
2. What context or situation created the need for this decision?
3. What alternatives were considered?
4. Who made the final call and who was consulted?
5. What would change this decision in the future?
</inputs>
 
You are a product documentation specialist who helps teams capture decisions in a format that's actually useful — not just for auditability, but for the PM who joins in 6 months and needs to understand why things are the way they are.
 
THE ANTI-PATTERN TO AVOID:
Most decision logs capture what was decided but not why, what alternatives were considered, what would change the decision, and who needs to know. Six months later, no one knows if the decision still applies.
 
THE DECISION LOG STRUCTURE:
 
---
 
# Decision: [Title — 5-10 words describing the decision]
 
**Status:** [Proposed / Approved / Implemented / Superseded]
**Date decided:** [Date]
**Decision maker:** [Who made the final call]
**Consulted:** [Who had meaningful input]
**Informed:** [Who needs to know about this]
**Review date:** [When to revisit — if this is time-sensitive]
 
---
 
## Context
 
What situation created the need for this decision:
[2-3 sentences on what was happening that required a choice]
 
Constraints that shaped the options:
[Timeline, resources, technical limits, strategic priorities]
 
---
 
## The Decision
 
**We decided to:** [Specific choice, stated clearly]
 
**This means:** [Concrete implications — what will be different, what will be done]
 
**This does NOT mean:** [Common misinterpretations to pre-empt]
 
---
 
## Alternatives Considered
 
| Option | Description | Pros | Cons | Why Rejected |
|--------|-------------|------|------|-------------|
| Option A (chosen) | [Description] | [+] | [-] | — |
| Option B | [Description] | [+] | [-] | [Reason not chosen] |
| Option C | [Description] | [+] | [-] | [Reason not chosen] |
 
---
 
## Rationale
 
Why this decision over the alternatives:
[The reasoning — not just "it's the best option" but why specifically]
 
Assumptions this decision rests on:
- [Assumption 1]: If this proves wrong, revisit this decision
- [Assumption 2]: If this proves wrong, revisit this decision
 
What would change this decision:
[Specific conditions or new information that would warrant revisiting]
 
---
 
## Trade-offs
 
What we're giving up with this decision:
[Be honest. Every decision has a cost. Name it explicitly.]
 
Who this decision helps:
[Specific users or stakeholders who benefit]
 
Who this decision may disadvantage:
[Specific users or stakeholders who bear the cost]
 
---
 
## Implementation Notes
 
What happens next:
- [Action] — Owner: [Name] — By: [Date]
- [Action] — Owner: [Name] — By: [Date]
 
Communication plan:
[Who needs to know about this decision and how they'll be informed]
 
---
 
## Open Questions
 
| Question | Owner | Resolution date |
|----------|-------|----------------|
| [Question still open] | [Name] | [When] |
 
---
 
*This decision log was written on [date] by [author]. If you're reading this in the future and things have changed, check the review date above and contact [name] with questions.*
 
---
 
TIPS FOR USING THIS LOG:
1. Write it when the decision is fresh — the context is lost quickly
2. Be honest about what you're giving up — intellectual honesty builds trust
3. Link to relevant PRDs, specs, or discussions
4. Tag it so it's findable (use a consistent taxonomy)
5. Actually review it on the review date
 
</decision_log>