A decision journal is a short record of a consequential choice, written before you know how it will turn out and reviewed after the signal is clear. The useful entry is not a diary of every preference. It is a way to keep the decision, the reasoning, the expectation, and the lesson in the same place.
Use one for choices that carry a real trade-off, contain uncertainty, or are likely to return in another form. Record what you knew, what you expected, and what would have changed your mind. Then review the call without turning the result into a verdict on your character.
What a decision journal is for
Most people keep task lists. Fewer keep a record of why they chose one path over another. That missing record makes it easy to rewrite the past. A result arrives, and the original reasoning becomes tidier, more confident, or more obvious than it was.
The Alliance for Decision Education's guide to keeping a decision journal describes the practice as a personal record of significant decisions that includes expected outcomes and later reflection. That is the useful center of the method: capture the thinking while it is still honest, then compare it with what happened.
A decision journal helps you learn three separate things:
- Whether you made a sound call with the information available.
- Whether your expectations were clear enough to be checked.
- Whether a pattern in your process deserves a different rule next time.
It does not promise perfect decisions. It gives you a fairer record of the work behind them.
Which decisions deserve an entry?
Do not journal every lunch order or minor scheduling choice. That turns a useful practice into administration. Start with decisions that meet at least two of these conditions:
- The choice changes how you will spend the next few weeks.
- Two or more options are credible, but each has a different cost.
- The outcome is uncertain enough to surprise you.
- You expect to face a similar decision again.
- You may later confuse a lucky result with good judgment, or a hard result with a bad process.
A career move, a major project commitment, a change in direction, a difficult boundary, or a decision to stop investing in something can earn a page. A low-stakes repeat choice usually does not need one.
Before you start researching, you can also use this stop rule for knowing when you have enough information to decide. The journal begins when the decision becomes specific enough to record.
Use a five-minute entry before the call
The entry should be short enough to write before the day gets busy. Use the same fields every time so the review is easy to read later.
| Field | What to write | Why it matters |
|---|---|---|
| Decision | State the choice in one sentence with a clear verb. | It keeps the entry from becoming a cloud of concerns. |
| Context | Name the goal, constraint, deadline, and people affected. | It preserves the conditions under which the call was made. |
| Options | List the real alternatives and the trade-off you accept. | It shows what you compared, not just what you chose. |
| Expectation | Write what you expect to happen and how confident you are. | It gives the future review something concrete to check. |
| Revisit rule | Set a review date or name the signal that would change the call. | It prevents endless reconsideration and forgotten learning. |
Write the expectation as a testable sentence. "This should help" is too soft. "If I choose the smaller launch, I expect to learn whether the offer is clear within four weeks" gives you something to revisit.
Confidence is not a performance score. It is a way to show how much uncertainty you knew you were carrying. A low-confidence call can still be the responsible choice when the alternatives are worse or the decision cannot wait.
Review the reasoning, not only the result
Return to the entry when the decision has had time to produce a meaningful signal. Do not review too early just because you are uncomfortable. A short-term wobble is not always an outcome, and a quick win is not always proof that the reasoning was strong.
Use four questions:
- What happened? Record the observable result without turning it into a story.
- What did I expect correctly? Keep the parts of the original reasoning that held.
- What surprised me? Name the assumption, constraint, or outside event you did not carry.
- What will I change next time? Change one rule, question, threshold, or review habit.
This is where the journal becomes more than documentation. The point is not to collect proof that you were right. It is to separate a thoughtful decision from a favorable outcome, and a weak process from an unfavorable outcome. You are building judgment, not a highlight reel.
When new evidence changes the path, write the change plainly. Changing your mind without losing credibility starts with naming what changed, what still holds, and what the new decision is.
Keep the journal small enough to survive real work
Choose one home for it: a notebook, a plain document, or a notes file. The tool is less important than the return path. Give each entry a date, a short title, and a review trigger you can find again.
Keep the entry to one screen when possible. If the decision needs a full brief, link to that brief and keep the journal record focused on the call. A journal is not a second project-management system. For team decisions that need shared ownership, consequences, and revisit rules, use a project decision log instead.
Set a light review rhythm. Once a month, read several entries together and look for a pattern: decisions made too late, assumptions left unnamed, the same kind of evidence ignored, or a review date that never arrives. One entry can teach you something. A group of entries can show you what your process keeps repeating.
A decision journal example
Imagine you are deciding whether to spend another month refining a project or release a smaller version now.
- Decision: Release the smaller version to a defined group by the end of the month.
- Context: The core work is usable, but the larger version has an uncertain audience and a growing scope.
- Options: Keep refining, release the smaller version, or pause the project and document why.
- Expectation: The smaller release should reveal which part people understand and where the next month of work belongs.
- Revisit rule: Review after the first meaningful set of responses, not after the first anxious hour.
That entry does not make the release succeed. It makes the decision visible. If the result is weak, you can ask whether the offer, audience, timing, or execution was wrong. If the result is strong, you can see which assumptions were useful instead of claiming the outcome was inevitable.
Make the next decision easier
A decision journal is a uniform for your judgment: a few repeatable fields that help you arrive with less noise, make the call, and return to the evidence. The Self Made Journal is built around the same practice: useful ideas should return you to real work. Keep your record private when privacy protects honesty. Share the relevant decision when other people need context or ownership. Self-made work still benefits from teachers, collaborators, teams, and clear outside perspective.
If you want a quiet layer for the long middle between decision and outcome, the Standard Issue Hoodie is built from heavyweight black fleece with a clean white embroidered mark. It is a uniform for returning to the work, not a substitute for it.
Start with one decision that matters. Write the call before the result edits your memory. Then come back and learn from the record.
0 comments