Most traders review their results. Very few review their reasoning. That gap is where behavioral drift hides — the slow accumulation of habits you cannot name because you never wrote them down.

This article teaches you how to keep a trading decision journal. By the end you will be able to capture, at the moment of each decision, the reasoning and emotional state behind it. Over time that record turns invisible patterns into something you can actually work on.

Why the journal matters

A results log tells you what happened. A decision journal tells you why you did what you did — which is the only information that can change your behavior. If you only track outcomes, you reward and punish the wrong things. A well-reasoned decision that ends in a loss looks identical to a panicked guess that ends in a loss. A lucky impulse looks identical to a disciplined entry. Without a contemporaneous record of your thinking, you cannot tell the difference.

The problem compounds over weeks. Memory rewrites itself to match outcomes. You remember your winners as calculated; you remember your losers as bad luck. A journal written at decision time, before you know the result, is the only record that resists this rewriting.

This is not a personality exercise. It is a data problem. You are trying to build a pattern library of your own behavior, and you cannot build a pattern library from data you never collected.

The mental model: the black box recorder

Commercial aviation has a strong safety record not because pilots never make errors, but because every flight generates a data trail that survives the crash. When something goes wrong, investigators do not rely on memory or reconstruction. They play back the exact sequence of events, instrument readings, and cockpit conversation that preceded the outcome.

Your decision journal is the black box recorder. You cannot fix what you never logged. A trading session that ends with no written record of why you made each decision is a flight where the black box was left on the runway. The data existed — your reasoning existed, your emotional state existed — but it is gone the moment you close the platform and the outcome attaches to the memory.

The goal is not to judge entries in real time. The goal is to preserve the data so that you can analyze it later, the same way investigators play back a recorder after the flight, not during it.

What to capture, and when

Timing is the critical variable. The journal entry must be written at decision time — not after the result is visible, not in the post-session debrief, not the next morning. The moment you know the outcome, your recollection of your reasoning starts to bend toward it. Write before you know.

Six fields cover what matters:

  1. Thesis. In one sentence: what is the trade based on? Not "it looks good" — the specific condition or observation that triggered the idea.
  2. Trigger. What exactly prompted you to act now rather than wait? Price level, pattern, time of day, a feeling — name it precisely.
  3. Risk. Where does the thesis break? What would have to happen for the original reasoning to be wrong?
  4. Invalidation point. If the market does X, you exit. Write X down. This is not the same as a stop-loss level — it is the logical condition that means your reasoning was incorrect.
  5. Confidence level. Low, medium, or high — and one phrase saying why. If you cannot explain the confidence level, that is worth noting too.
  6. Emotional state. One honest word: calm, anxious, bored, frustrated, eager, detached. This field feels optional. It is not.

Six fields, written in under two minutes. That is the whole system. The analysis comes later.

The weekly review: turning entries into patterns

Raw entries are not yet useful. Once per week, read back through every entry from the prior week alongside the outcome. You are not judging individual trades — you are looking for patterns across the emotional state field and the thesis field together.

Three questions structure the review:

  1. Which emotional states appeared most often in losing entries? Which in winning entries?
  2. How often does your stated thesis match your stated trigger — and how often are they different things?
  3. How often did you exit at your stated invalidation point versus at a different point? If those diverge consistently, your stated reasoning and your actual reasoning are not the same thing.

The point is not to find a single lesson. The point is to see a pattern repeat enough times that you cannot ignore it.

A hypothetical example

Suppose a trader begins logging the emotional state field honestly. Over four weeks, she notices that roughly half her losing entries contain the word "bored." The thesis fields on those entries are thin — vague observations rather than specific conditions. The triggers are mostly time-based: "market has been quiet for an hour," "nothing has happened all morning."

She has not discovered that boredom causes losses. She has discovered something more specific: when she is bored, she writes a thin thesis. When she writes a thin thesis, she enters on a weak reason. When she enters on a weak reason, she has no clear invalidation point, so she holds too long or exits too early depending on how the position feels in the moment.

The fix she implements is not "don't be bored." It is: any entry where the thesis is fewer than ten words gets no position until the thesis can be expanded. She now has a rule she can apply in real time, derived from her own data — not from a book, not from advice, from her log.

That is what a journal is for. Not introspection for its own sake. Pattern identification that produces a concrete process change.

Common mistakes

  • Writing after the outcome. This is the single most common error and it destroys the entire value of the exercise. If you know the trade is up 3%, your "thesis" becomes a rationalization of a winner. Write before you know.
  • Logging only bad trades. You need the winning entries too, or you have no baseline. Behavioral drift can show up in how you handle winners just as clearly as in how you handle losers.
  • Using the journal as a confession booth. The goal is analysis, not self-punishment. An honest entry that reads "I entered because I was bored and impatient" is useful data. Shame attached to it is noise that makes you less likely to write the next honest entry.
  • Waiting for a perfect format. A notebook, a spreadsheet, a voice memo — the medium does not matter. The discipline of logging at decision time matters. Start with any format and refine it after you have been doing it for two weeks.
  • Reviewing entries too frequently. Looking at yesterday's entry and drawing conclusions is premature. Patterns need volume to be visible. Review weekly at minimum; monthly gives you better signal.

Simulator exercise: the Speed Run pause drill

Abu Terminal's Speed Run compresses real market history into a decision-by-decision replay. Most users respond to each prompt on instinct — which is exactly what the drill is designed to surface. To train the journal habit inside the simulator, modify the way you play:

  1. Before you select any option in a Speed Run scenario, pause and write one sentence in your journal — physical or digital — stating your reasoning. Not "looks bullish." The specific condition visible in the scenario that is driving your choice.
  2. Write your emotional state in one word. You are replaying history at speed, under mild time pressure — what are you feeling?
  3. Then make your selection.
  4. After the Speed Run ends, open the debrief panel and compare what the debrief shows about the sequence of events to the reasoning you wrote before each decision. Pay attention to where your stated reasoning and the market's actual behavior diverged — and to whether the divergence bothered you at the time or only in retrospect.

The simulator is not trying to replicate a live account. It is trying to make your decision-making visible to you at a pace where you can actually watch it. The journal habit transfers directly: the pause-and-write discipline in a Speed Run is the same muscle you are building for live sessions.

Run the same historical scenario twice — once without writing, once with. The second run tends to produce different decisions, not because the scenario changed, but because articulating a thesis before choosing forces a small, real review that instinct skips.

Reflection prompts

At the end of any session — simulator or live — three questions are worth sitting with:

  1. Which entry today am I least comfortable re-reading, and why?
  2. Did my exits follow my stated invalidation points, or did I invent new reasons in the moment?
  3. If I showed today's entries to someone else with the outcomes removed, would my reasoning look disciplined or improvised?

These are not comfortable questions. They are useful ones.

Self-check

Before moving on, check your understanding:

  1. When should you write a journal entry — before or after knowing the result? Before. Once the outcome is visible, your memory of your reasoning starts to bend toward it.
  2. What is the emotional state field for? Pattern identification. Over time it reveals which states correlate with which types of decisions, giving you a rule you can apply before the next entry, not just after.
  3. Why is the weekly review more useful than reviewing individual entries? Individual entries are data points. Patterns require volume. A single "bored" entry is noise. Eight "bored" entries across three weeks in the same type of losing setup is a signal.

Closing

Most behavioral patterns in trading are not hidden. They are just unrecorded. The same mistake can repeat thirty times without ever becoming visible if you are only tracking outcomes and not the reasoning that produced them. A decision journal does not make you a better trader by itself. It makes the data available so that you can do the work of becoming one.

Start with the six fields. Write at decision time. Review weekly. The pattern will show itself — usually within a month, sometimes faster. What you do with it is the actual work.

Educational simulator content, not financial advice.