Skip to content
Playbook
BeginnerCEOFounderHR

The decision log: the single highest-ROI operating habit

A decision log captures what was decided, by whom, why, and what alternatives were considered. Two hours a week to maintain — and it pays back the first time…

7 min read
On this page
60-Second Summary
  • Format: decision, owner, date, options considered, rationale, reversibility.
  • One log per team. Reviewed at quarterly retros.
  • Reversible decisions get a lightweight entry; irreversible decisions get the full template.
  • The point is not perfection — it's not having the same argument three times.

Most teams re-argue the same decisions every 6 months. The decision log doesn't make decisions better — it makes them traceable and re-argument unnecessary.

The format

FieldNotes
TitleVerb-led, specific. 'Move comp cycle from Q1 to Q3.'
DateDecided on
OwnerSingle accountable person
Context2-3 sentences on the situation
Options consideredAt least 2, usually 3
Decision + rationaleWhy this option
ReversibilityOne-way door / two-way door
Review triggerDate or signal that would revisit

When to log

  1. Any decision that future-you might be asked to justify.
  2. Any decision involving >2 stakeholders.
  3. Any decision that involves trade-offs you might forget.
  4. Don't log every Jira ticket — log the choices behind the tickets.

Reviewing the log

  • Quarterly retro: which decisions held up? Which would we reverse?
  • Onboarding doc: 'these are the decisions that shape how we work.'
  • Pre-mortem reference: 'last time we discussed X, here's what we decided and why.'
  • Knowledge transfer: when a manager moves on, the log is half the handover.
The single rule

If a decision shows up in a 1:1 as 'wait, why did we do that?' more than once, it needed a log entry.

Written by Pawan Joshi.Sources cited inline.
First published 16 Jun 2026See site changelog →