The Decision Journal: Improve Your Decision-Making
·
Updated: January 27, 2026
·8 min read

The decision that changed how I think about decisions happened in a conference room three years ago.
I was watching my manager deliberate over a critical project. Six months of work and three teams were on the line. Before deciding, she pulled up a simple document—a log of past decisions. Not just what was decided, but what she expected to happen, why she believed it would work, and what actually occurred months later.
She scrolled to a similar decision from a year ago. "See this? I was convinced we'd ship in three months. We took five. But look here—I correctly identified the API integration as the biggest risk. I just underestimated how much."
I was struck by her honesty. Most leaders would have said "I knew it would take longer" after the fact. But here was proof of what she actually thought at the time.
That day, I started keeping my own decision journal. It transformed how I approach every important choice.
POST-DECISION REVIEW (fill in later) Actual Outcome: [What happened] Process Grade: [A-F, judging the process not the result] What I Learned: [One key insight]
It costs 15 minutes up front but saves hours later by eliminating rework and second-guessing. Plus, you build a library of patterns that speeds up future decisions. Can you do this solo?
Absolutely. I do my pre-mortems alone most of the time. Once a month, I ask a trusted friend to review my "counter-evidence" sections for blind spots. What if the outcome is bad?
Grade the process, not the result. A good process with a bad outcome means you got unlucky. A bad process with a good outcome means you got lucky. Focus on improving the process. Which tool is best?
I use Google Docs. Other people swear by Notion's databases or Obsidian's linked notes. The method matters more than the app. Start with whatever you'll actually use.
Want to build better decision systems into your weekly routine? Check out How to Organize Your Week for a complete weekly review framework. When decisions don't go as planned, developing a growth mindset can help you extract lessons without harsh self-judgment.
The Problem with How We Usually Decide
Once I started paying attention, I noticed something: we constantly rewrite history in our heads. A product launch succeeds, and suddenly everyone "knew it would work"—even though half the team was skeptical before launch. A hire doesn't work out, and the same people who approved the candidate now say they "had concerns from the start." This isn't dishonesty. It's how human memory works. Our brains automatically reconstruct the past to make sense of the present. Psychologists call it hindsight bias, and everyone does it. The problem? If you can't remember what you actually thought before a decision, you can't learn from it. You just get better at telling yourself convincing stories. A decision journal breaks this cycle. It's a timestamped record of what you actually believed before you knew how things would turn out.What Goes in a Decision Journal
When I started my journal, I kept it simple. Three core elements:- What I believed would happen
- Why I believed it (my reasoning and assumptions)
- What I planned to do about it
Five Decision Traps a Journal Helps You Avoid
After a year of journaling, I identified five patterns that repeatedly threw my decisions off track:1. Judging Decisions by Results Alone
I made a hire that looked perfect on paper. Six months later, the person quit. Bad decision, right? Not necessarily. When I reviewed my journal entry, I saw that my reasoning was sound. The role was clearly defined, the candidate's experience matched perfectly, references were strong. What I couldn't predict: the candidate's spouse got a dream job in another country. Good process, unlucky outcome. The lesson: keep refining the process, don't beat yourself up over things you couldn't control. Journal fix: Record your reasoning and probability estimates before you know the outcome.2. The Planning Fallacy
My team estimated a feature would take three weeks. It took seven. Looking back at my journal, I found the same pattern repeated. We were systematically optimistic about timelines, especially for projects with external dependencies. Now I add a "base rate" check: what do projects like this usually take? That outside view often reveals my inside view is wishful thinking. Journal fix: Track your estimates vs. actuals. After 10 entries, you'll see your personal bias clearly.3. Confirmation Bias
I was excited about a new tool for the team. I spent hours reading positive reviews, watching demos, imagining how it would improve our workflow. What I didn't do: actively search for reasons it might fail. When I added a "counter-evidence" section to my template, I forced myself to write three reasons the decision might be wrong. It's uncomfortable. It also saves me from charging into bad bets. Journal fix: Before finalizing any decision, write three reasons you might be wrong.4. Availability Heuristic
A dramatic recent event distorts how you see risk. One security incident, and suddenly security is "the top priority" for six months—even if other risks are statistically more likely. My journal shows me when I'm overweighting recent or vivid examples. If I made a similar decision six months ago without that concern, it's a signal to check whether the new information actually changes the calculus. Journal fix: Review similar past decisions before making new ones.5. Emotional State Blindness
Some of my worst decisions came when I was tired, stressed, or running on adrenaline from a recent success. Now I log my emotional state alongside the decision. It's a two-word check: "stressed/rushed" or "calm/rested." When I review decisions that went wrong, there's often a pattern. Journal fix: Note how you feel when you decide. Patterns emerge.A Simple Decision Journal Template
Here's the template I use. One page, no fluff: DECISION JOURNAL ENTRY Date: [When you're making the decision] Decision: [What you're choosing to do] Expected Outcome: [What you think will happen] Confidence Level: [High / Medium / Low] Key Reasoning:- Reason 1: [Why this will work]
- Reason 2: [Supporting evidence]
- Reason 3: [What makes you confident]
- [Three reasons this might be wrong]
POST-DECISION REVIEW (fill in later) Actual Outcome: [What happened] Process Grade: [A-F, judging the process not the result] What I Learned: [One key insight]
When to Use It (And When Not To)
I don't journal every decision. That would be exhausting and unsustainable. Use the journal for:- Decisions that are hard to reverse
- Choices involving significant money, time, or relationships
- Situations where you've been wrong before
- Any decision you'll want to review in 6+ months
- Easily reversible choices
- Low-stakes daily decisions
- Situations where speed matters more than precision
Making Better Decisions in Practice
Beyond the journal itself, here are tactics that improved my decision quality: Write the post-mortem before deciding. Imagine the decision failed. What went wrong? This "pre-mortem" surfaces risks you'd otherwise overlook. Seek disconfirming evidence. Before major decisions, ask: "What would change my mind?" Then actually look for that information. Create a decision-making checklist. Not for every choice, but for recurring decisions (hiring, project prioritization, vendor selection). Checklists prevent you from skipping steps when you're rushed. Involve a devil's advocate. Ask someone to argue against your preferred option for 10 minutes. Make it safe to poke holes. Sleep on hot decisions. A 24-hour pause filters out decisions driven by temporary emotion.Common Questions
Is this worth the time?It costs 15 minutes up front but saves hours later by eliminating rework and second-guessing. Plus, you build a library of patterns that speeds up future decisions. Can you do this solo?
Absolutely. I do my pre-mortems alone most of the time. Once a month, I ask a trusted friend to review my "counter-evidence" sections for blind spots. What if the outcome is bad?
Grade the process, not the result. A good process with a bad outcome means you got unlucky. A bad process with a good outcome means you got lucky. Focus on improving the process. Which tool is best?
I use Google Docs. Other people swear by Notion's databases or Obsidian's linked notes. The method matters more than the app. Start with whatever you'll actually use.
Start Simpler Than You Think
If I could go back and give myself one piece of advice, it would be this: Start simpler than you think you need to. Your first version will feel embarrassingly basic. That's perfect. Use it for three months before adding any complexity. My first entries were just three bullets:- What I'm choosing
- Why I think it'll work
- What I'll watch for
Want to build better decision systems into your weekly routine? Check out How to Organize Your Week for a complete weekly review framework. When decisions don't go as planned, developing a growth mindset can help you extract lessons without harsh self-judgment.
Was this article helpful?
Related Posts

AI & Tech· 6 min
AI Won't Replace Your Job—But It Will Replace How You Think
The real threat isn't job loss—it's cognitive atrophy. AI will change how you think, and you need to be intentional about which changes you accept.
Read

AI & Tech· 6 min
The New Digital Divide Is Not AI Access—It's Judgment
Everyone can use AI now. The gap isn't access—it's knowing what to ask, when to trust the output, and when to think for yourself. Judgment is the new literacy.
Read

AI & Tech· 7 min
Why Most People Are Using ChatGPT Wrong
ChatGPT isn't an answer machine—it's a thinking partner. Learn why treating AI as a shortcut backfires and how to use it to sharpen your own judgment instead.
Read

AI & Tech· 6 min
The Quiet Skill That Will Matter More Than Prompt Engineering
Everyone's learning prompt engineering. But the skill that actually drives AI value is problem framing—and almost nobody is developing it.
Read
Explore more topics: