Strategic Decision Log Template
A structured log entry for one strategic decision — what was decided, why, who signed off, when, and the key assumptions that might later break. Output: a printable record.
Who it’s for: Founders, CEOs, and functional leaders who want their team to understand why a decision was made — six months after the Slack thread disappeared.
1 · Header
The non-negotiable metadata. A decision log without these is just a memoir.
2 · The decision
State it plainly. If you can’t name the decision in one sentence, you don’t have one yet.
Name the other two or three options and why each lost. Without this the log can’t be used as precedent.
3 · The reasoning
Why we picked this path. The version a new hire should read in six months to understand the company’s logic.
Data, quotes, examples. Named, dated.
4 · Assumptions
The bets behind the decision. If one of these turns out to be wrong, we revisit — which means naming them now, before they’re embarrassing.
5 · Review schedule
When we revisit, and what would force an earlier revisit.
The events that mean “check this decision now, don’t wait.”
Read it honestly, not charitably.
A decision log is only valuable in retrospect. Six months from now, when someone asks “why did we choose board-ready over operator-focused?”, this page answers without the decision-maker needing to remember. That means the reasoning has to read clearly without context.
The alternatives considered and assumptions sections are the two most useful ones. Future teams care less about what you decided and more about what else you ruled out — and which bets you were making. Skip either and the log is a diary.
Three moves you can make this week.
- Share this page with one stakeholder not in the decision. If they can’t reconstruct the reasoning from the page alone, add what’s missing.
- File it where decisions are meant to live. Not in a Slack thread, not in a personal Notion. A shared index, with the date in the filename.
- Put the revisit date in a calendar. Decisions without scheduled reviews become invisible. A calendar reminder is the difference between a log and a museum.
Why these questions, in this order.
Teams lose most of their strategic context not because decisions are wrong, but because they go unlogged. A year later, someone asks “why did we decide X?” and the answer is a shrug. The shrug is the cost.
The structure here — decision, alternatives, reasoning, assumptions, review — matches the sections a future reader actually needs. Most decision logs skip assumptions, which is where the real value sits: a decision based on assumption A is one kind of thing; a decision based on assumption B is another. If the assumption moves, the decision should move with it.
Naming a revisit date before the decision cools sounds bureaucratic; it is the single habit that separates companies that iterate on strategy from companies that ossify.
Run the full Strategic Context.
The shared memory that makes every other tool smarter over time.
- One-Page Positioning WorksheetFill in audience, category, differentiator, proof, and emotional response in one page.
- Competitor Battle Card TemplateBuild one battle card: claims, reality, your response, with coverage score built in.
- Messaging Hierarchy BuilderCategory, pillars, proof. Build a three-level messaging pyramid you can print.