How to keep track of your decisions (and never re-debate them)
There is a sentence that costs a fortune in meetings: "wait, what did we decide again?". A decision was made three months ago, everyone agreed, and yet here it is back on the table. You re-debate it. You reverse it. Often in the other direction.
The problem is not that you write nothing down. It is that keeping track of a decision is not the same as writing it somewhere. Here is why, and the concrete method, with an example, to record your decisions so you never replay them.
Why decisions get lost, even when they are written down
A decision rarely lives in the right place. It is made in a meeting, a message thread, a call, a corner of a document. Three months later, three things have vanished:
- the why: you sometimes remember the what, almost never the reasoning that led to the decision;
- the options you ruled out: you often re-debate a path you had already studied and rejected, for lack of a record;
- the context: what was true at the time of the choice (a customer signal, a constraint, a number) is no longer attached to the decision.
The result: the decision is "somewhere", but it does not resurface at the moment you need to remember it. A filed document is not a memory. Retrieving information and remembering information are two different things. This is why startups forget their decisions and pay for the same choice several times, a form of decision debt that piles up in silence.
What "keeping track of a decision" really means
Keeping a decision is not archiving a line that says "decided: we go with X". It is keeping enough context so that, later, nobody needs to re-debate it. In practice, a well-kept decision fits in a small block, often called a decision record, or decision log, that answers four questions.
The method: keep a decision in 4 parts
For every decision that matters, write these four parts. It takes two minutes and saves you weeks.
1. The decision itself
One clear sentence, in the present tense, no ambiguity. Not "we think maybe". A decision is a made choice.
2. The why
The reasoning, in two or three sentences. This is the most valuable part and the most often forgotten. The why is what prevents re-debate: when someone wants to reopen the subject, they first hit the reasons that led to the choice.
3. The options you ruled out
Write down what you considered and rejected, and why. Without this, you will sooner or later re-debate a path you had already studied.
4. The source
What is the decision connected to? A customer signal, a number, a technical constraint, a conversation. Tying a decision to its source makes it verifiable: in six months, you can trace back to what justified it, instead of trusting your memory.
A concrete example
Here is what a real decision looks like, kept across the 4 parts:
Decision. We charge based on usage rather than a flat subscription.
Why. Our first ten customers have very different volumes. A flat price penalizes the small ones (who leave) and undercharges the big ones. Usage aligns the price with the value received.
Options ruled out. A single flat subscription (ruled out: does not fit heterogeneous usage). Three fixed tiers (ruled out for now: too early, not enough data to set the thresholds).
Source. Feedback from the onboarding calls of June 8 and 12, and the usage-volume table for the first 10 accounts.
Two minutes of writing. And the day someone proposes to "go back to a flat price, it's simpler", you do not start from zero: you have the why and the already-ruled-out paths in front of you. To move faster, start from a ready-to-fill decision record template.
A decision is not frozen: it evolves
A decision record is not set in stone. Context changes, a customer signal contradicts an assumption. The rule: keep the history (the original decision, what changed, the new decision) instead of rewriting the past. That way you see not only what you decided, but how your thinking evolved.
The real test: does it resurface at the right moment?
Keeping a decision is useless if you have to remember to go look for it. The goal is not a beautiful archive, it is that the right decision comes back on its own when the subject resurfaces: when someone proposes to reopen the question, when a new hire needs to understand a choice, when a customer signal touches a past decision.
That is the role of a living business memory: not just to store your decisions, but to connect them to their sources and bring them back at the right moment. That is what we build with Verbasil.
Key takeaways
- Keeping track of a decision is not writing it down: without the why, the ruled-out options and the source, it gets re-debated.
- Keep each important decision in 4 parts: the decision, the why, the options ruled out, the source.
- Stack the changes instead of rewriting.
- The end goal is not to archive, it is that the decision resurfaces at the right moment.
FAQ
What is a decision record (decision log)?
A small block that keeps a decision and its context (the choice, the why, the ruled-out options, the source), so you do not have to re-debate it later. See the definition of decision log.
Where should I keep my decisions?
The medium barely matters at first. What matters is the structure (the 4 parts) and, above all, that the decision resurfaces when it should. A filed document you forget to reopen does not do that job.
Do I need a tool for this?
Not to start: the 4-part method works in a plain document, or with a decision record template. A tool becomes useful when you want your decisions to connect automatically to their sources and resurface at the right moment, without any effort from you.
How do I avoid re-debating a decision?
Keep the why and the ruled-out options. That is what cuts it short: when someone wants to reopen the subject, they first find the reasons for the choice and the paths already ruled out.