Most people remember their decisions through outcome fog. If it worked, they remember clarity. If it failed, they remember regret. A decision journal restores the missing piece: what you knew at the moment you decided.
Its value is simple: you are not trying to prove you are a great chooser. You are training your judgment loop.
Paul tends to explain himself after the result, which means he often edits the story while it is still warm. Gollius records the decision before the result arrives. That small discipline changes the quality of learning because it separates judgment from hindsight theater.
A decision journal is not for every tiny move. It is for choices that carry some weight, repeat often, or tend to become emotionally distorted later. If the decision has consequences you will want to review, write it down while the future is still unknown.
Why this is different from a to-do list
To-do lists store tasks. A decision journal stores context.
For each meaningful decision, you capture:
- the exact choice you are making,
- the options you considered,
- your best reason at the time,
- expected downside and upside,
- what could invalidate the choice,
- when you will review it.
You can still be wrong. The journal makes it visible why you were right, wrong, or underinformed.
That distinction matters because many people punish themselves for outcomes they could not fully see. A journal does the opposite. It creates a cleaner record so you can ask whether the choice process was sound even when the result was mixed.
It also prevents a common trick of the mind: when the outcome is good, the mind says the process was brilliant; when the outcome is bad, the mind says the process was stupid. A journal gives the process its own standing.
A lightweight format you can keep
Use this format when the decision is real but time-limited:
- Decision:
- Why this matters now:
- Options (minimum 3):
- Preferred option and why:
- Expected result in 2-4 weeks:
- Main uncertainty:
- What would make me change course:
- Review date:
Three to five minutes is enough for most decisions.
You can make the structure even more human by adding one sentence at the top:
- Mood or pressure right now:
This is not to judge emotion. It is to notice whether urgency, fatigue, hunger, pride, or irritation is shaping the decision more than the facts are.
Example:
- Decision: decline a last-minute request to redo a deck tonight
- Why this matters now: I need sleep for an early client meeting
- Options (minimum 3): do it now, do a partial version, decline and propose morning
- Preferred option and why: decline and propose morning, because quality will be higher
- Expected result in 2-4 weeks: fewer exhausted late nights, more consistent output
- Main uncertainty: whether this will annoy the requester
- What would make me change course: if the meeting is truly urgent and the constraint is real
- Review date: Friday afternoon
That kind of entry is short, but it carries enough information to teach.
How to review without reinventing your narrative
When review day arrives, do not judge only the result. Ask three questions:
- Were my observations complete enough at the time?
- Which assumption was most fragile?
- Did I execute the decision consistently?
Then adjust only one behavior: one assumption test, one information source, one default action.
The restraint is important. If you change everything after every review, the journal becomes a stage for anxiety. You are trying to improve the next decision, not redesign your personality after each encounter with uncertainty.
Good reviews sound plain. They are almost never dramatic.
Example: career side decision
Decision: take a part-time contract in addition to a full-time role.
Journal fields:
- expected upside: additional income, new skills,
- main risk: recovery drop and missed deadlines,
- uncertainty: underestimating coordination and admin load,
- review trigger: after six weeks.
At review, the result may show income gain and skill growth, but recurring fatigue. The action is not "I was wrong." The action is "next time I cap workload by schedule, not motivation."
Another example:
Decision: keep working with a client whose work is interesting but whose communication is unpredictable.
Possible entries:
- upside: portfolio value and learning
- risk: emotional drag and delay churn
- uncertainty: whether the communication style can be stabilized
- review trigger: after four deliverables
At review, you might discover that the work itself is strong, but the hidden cost is the amount of attention consumed between tasks. That insight is better than a vague memory of frustration.
The journal turns "I felt bad" into "this pattern costs me 40 minutes of re-orientation per handoff." That is useful because it lets you design around the cost.
Keep it useful, not punitive
Common failure modes are overfilling entries and reviewing only after bad outcomes. Both turn the method into stress.
Use it for meaningful decisions, with a clear review date and one concrete adaptation. If the journal increases shame or rumination, make entries smaller and reduce frequency for one week.
The best entries are not essays. They are snapshots. If you catch yourself writing a defense brief, stop and reduce the page to the essentials:
- what I chose,
- why I chose it,
- what I thought would happen,
- when I will look again.
That is enough to keep the loop alive.
If you want an even tighter version, use a single line:
Decision -> reason -> assumption -> review date
The point is not elegance. The point is repeatability.
Keep The Journal In Service Of Action
The journal is not a courtroom where the past self is prosecuted. It is a training room for judgment.
When a decision has serious stakes, use the journal to clarify the choice, then widen the room with the right people and expertise. Strong judgment does not mean deciding alone. It means knowing what kind of support the terrain deserves.
For ordinary decisions, keep the entry short, choose one review date, and let the review change one future behavior. That is how reflection becomes command instead of rumination.
The Gollius move is simple: decide with enough structure to learn, then revisit with enough honesty to improve. Paul hopes the answer will prove him right. Gollius wants the record to make him better.
One practice and one review
Practice: for the next five meaningful decisions, write the journal entry before telling anyone your conclusion.
Review: at the end of the week, look for one recurring pattern in your assumptions. Are you consistently overestimating speed, underestimating fatigue, or trusting the first option too quickly? Pick one pattern and add one check to the next entry.