4 min read· Updated 2026-09-03
Decision log template
Copy this table. Fill only what you know. Empty is better than fiction.
The template
| Field | What to write | Example |
|---|---|---|
| Date | Day you decided, not the day you remembered | 2026-09-03 |
| Decision | One sentence. The choice, not the debate. | Charge per invoice, not per seat. |
| Status | Decided / Revisit / Superseded | Decided |
| Context | What was true that day | Freelancers, pre-PMF, two weeks of runway anxiety. |
| Options considered | What you rejected, with a reason each | Seats (familiar, scares indies). Usage (fair, billing complexity). |
| Why this | The real reason, including the quote or constraint | “I don’t chase invoices, it feels rude.” |
| Owner | Who can reopen it | Alex |
| Revisit if | A tripwire, not a calendar ritual | If activation drops after the billing change. |
| Outcome | Fill after you ship or wait | Reminder feature drove 2 upgrades. |
| Sources | Links to the thread, scribble, or call note | Voice note 3 Sep; support screenshot. |
Rules that keep it honest
- One decision per row. “Rethink pricing” is not a decision.
- Write it the day you decide.
- Outcome is required later. A log without outcomes is a diary.
- If reversing it would cost less than a week, skip the row.
More context: what a decision log is.
In Scribble Flow
You do not have to keep this as a spreadsheet.
- Capture the messy version - just capture.
- Turn it into a decision in Memory - make something of it.
- Ask later: Why did we choose this? Sources come back with the answer.
- After ship, add the outcome next to the work.
Founders: keep every idea, and why you shipped it. Start a free desk · Pricing