a decision log template you'll actually fill in
most decision logs are abandoned by week three. not from lack of discipline. they just ask for more than a decision is worth at the moment you make it.
the case for keeping a decision log is easy to make and easy to ignore. you make hundreds of consequential calls a year. you remember almost none of them accurately, because memory quietly rewrites the ones that went badly and takes credit for the ones that went well.
without a record you get no compounding. every hard decision arrives as though it were the first.
the reason most logs fail is not motivation. it is field count. a template with twelve boxes gets filled in beautifully twice and then never again, because at the moment you make a real decision you have about ninety seconds of appetite for admin.
six fields, and no more
| field | what goes in it | why it earns its place |
|---|---|---|
| date | the day you decided | lets you see how long things take, later |
| the call | one sentence, active, "i will x by y" | vague entries are useless in review |
| why | one line, the actual reason | this is the field that pays off, because your reasoning is what you will not remember |
| confidence | 1 to 5 | tells you whether you are systematically over or under confident |
| impact | 1 to 5 | lets you separate the calls worth reviewing from the noise |
| review on | a date | without this the log is a diary, not a loop |
then one more, added later, not at the time.
| field | what goes in it |
|---|---|
| outcome | what actually happened, one line, written on the review date |
a worked example
| field | entry |
|---|---|
| date | 2026-07-27 |
| the call | i will move new client pricing to 4,500 a month from 1 september |
| why | costs up, scope has grown, and the last three prospects did not blink at the current number |
| confidence | 4 |
| impact | 5 |
| review on | 2026-12-01 |
| outcome | (blank until december) |
notice how short the why is. one line, written honestly, is worth more than a paragraph written for an audience. nobody else is reading this.
where to keep it
anywhere you will actually open. a spreadsheet with seven columns. a single running note. the back of a notebook.
the format matters far less than the habit, and the habit is fragile early on, so remove every obstacle you can. if opening it takes more than five seconds you will stop.
the review is the whole point
logging without reviewing is journalling. the value arrives on the review date, when you read what you expected and compare it to what happened.
once a month, open the log and look at anything whose review date has passed. fill in outcomes. then ask two questions.
- where was my confidence wrong, and in which direction? most people are systematically off in one direction, and it is usually the same direction every time.
- which decisions sat longest before i made them, and what did those have in common?
after ten or fifteen entries the second question starts producing real answers. you will find you stall on a specific type of call, and it will not be the type you would have guessed.
how to start today
do not backfill. do not build a system. take the decision currently sitting on you, write the six fields, pick a review date, and close the file.
one entry today beats a perfect template you set up next week.
if you want to know what that decision has cost while it has been sitting, the decision fatigue calculator does the arithmetic on your own numbers. and if you are carrying several at once rather than one, that is a different problem with a different fix.