Ask a founder why a past decision was made and you will usually get a clear, confident answer. It is often not the real one.
Memory is generous to the person doing the remembering. Decisions that worked out get remembered as wise. Decisions that did not get remembered as unlucky, or as someone else's idea. Over time, a founder builds a story about their own judgment that is more flattering than accurate.
A decision log is a simple fix. Write down significant decisions at the time you make them, along with your reasoning. Then go back and read it.
What goes in it
Not every decision needs an entry. Daily operating calls would bury the log in noise. The ones that belong are the decisions that are expensive, hard to reverse, or likely to matter a year from now.
In a portfolio, that tends to mean funding or not funding a venture, major hires, entering a new market, significant contracts, pricing changes, and choosing to stop something.
Each entry is short. A few paragraphs at most:
- The decision. What you chose, in one sentence.
- The alternatives. What else you considered, and why you passed on it.
- The reasoning. The main factors that drove the choice.
- What you expect. What should happen if you are right, and roughly when.
- What would tell you that you were wrong. The signs that would make you revisit it.
- How confident you are. A rough sense of certainty, honestly stated.
It takes ten minutes. It is some of the most useful ten minutes in the decision.
Why writing it down helps immediately
The first benefit shows up before the decision is even made.
Having to write down the alternatives makes it harder to pretend there were none. Having to state what would prove you wrong forces you to think about failure before you are emotionally committed. And having to state your confidence often reveals that you are less sure than you sounded in the meeting.
Sometimes the act of writing an entry is enough to slow down a decision that is being made too quickly. That alone would justify the habit.
Why reading it back helps more
The real value comes later, when you review past entries against what actually happened.
Outcomes alone are a poor teacher. A good decision can turn out badly because of things nobody could have predicted. A bad decision can turn out well through luck. If you judge only by results, you learn the wrong lessons from both.
The log lets you separate the two. Did the outcome come from the factors you identified? Did the risks you named actually show up? Were you wrong about something you could have known at the time? Those questions improve judgment. "Did it work?" mostly does not.
Over time, patterns appear. You may find you are consistently too optimistic about timelines, or too cautious about hires, or that a certain kind of opportunity keeps disappointing you. Those patterns are almost impossible to see without a written record.
How to review it
The natural rhythm is quarterly, alongside whatever regular review you already run. For us, the natural fit is the portfolio scorecard. Look at decisions that have had enough time to play out, and for each one:
- Read the original entry before discussing what happened.
- Compare what you expected with what actually occurred.
- Separate what was within your control from what was not.
- Note any lesson that should change how you decide next time.
Reading the entry first matters. If you discuss the outcome first, everyone's memory of the original reasoning quietly adjusts to fit it.
It makes stopping easier
One of the hardest decisions in a portfolio is knowing when to kill a venture. A decision log makes that easier.
If the entry written when a venture was funded recorded what you expected and what would tell you that you were wrong, the question months later becomes simple: did those signs show up? If they did, the decision to stop was effectively made in advance, by a version of you that had not yet become attached to the project.
That is far easier than trying to decide in the moment, when sunk costs and hope are both pulling the same direction.
Honesty is the whole point
A decision log only works if it is honest. Entries written to look good, or edited later, defeat the purpose. The value comes from recording what you actually thought, including the parts that turn out to be wrong.
That requires a certain humility. Reading your own confident predictions from a year ago and seeing how many missed is not pleasant. It is, however, the most reliable way I know to get better at the part of the job that matters most.
The habit is simple. Write it down when you decide. Read it when you know how it turned out. Learn from the difference.