Educational Simulation Archive
Trade Review Without Hindsight
REVIEW GUIDE · EDUCATIONAL JOURNALING

Trade Review Without Hindsight

Once you know how a simulated trade ended, you can no longer see the decision the way you saw it then. Review discipline exists to restore that blindness.

Strictly educational archive. Simulated analysis and hypothetical models only.
HYPOTHETICAL SIMULATEDReview Guide 08 / 10
Trade Review Without Hindsight

Hindsight Bias in Journals

Hindsight bias is the tendency to believe, after the fact, that the outcome was predictable all along. In a trading journal it shows up as reviews that read 'obviously the level would hold' — statements nobody can verify because the outcome was already known when they were written.

The bias is corrosive for education specifically: it converts every review into a confirmation exercise. Entries stop producing new information because the reviewer already 'knows' the answer.

Time-Stamped Reasoning

The counterweight is reasoning written with timestamps before the result is visible. The pre-entry note, the mid-trade observation, and the post-session review should carry separate timestamps so each can be read as a product of its own moment.

When reviewing, read the timestamps in order and resist summarizing. The goal is to hear the earlier reasoning in its own voice, including its uncertainty — especially its uncertainty.

Separating Decision Quality From Outcome

Evaluate each entry twice, with two different questions. Question one: 'Given only what was knowable at decision time, was the reasoning sound?' Question two: 'What did the simulator display?' Keeping the questions in that order prevents the outcome from leaking into the quality assessment.

A decision can be sound and display a poor simulated result, or sloppy and display a good one. The journal's value is in separating those cells — a two-by-two table of quality versus outcome.

A Blind Review Exercise

A practical drill: cover the outcome column of the last ten entries and re-read only the pre-entry notes. Write, for each, whether you would take the same decision again. Then uncover the outcomes and note where your re-read judgment disagrees with your memory of the session.

The disagreements are the lesson. They show where outcome-knowledge was silently doing the evaluating — the exact mechanism hindsight bias uses.

Anti-Hindsight Techniques

TechniqueHow It WorksWhat It Prevents
Timed entry reviewReview written before replaying the outcomeRewriting intent after seeing the result
Counterfactual logRecord what you'd have done at each decision point blind'I would have known' claims
Information blackoutHide later-session data during reviewUsing future data to grade past calls
Two-reader passA peer reads only pre-written fieldsNarrative smoothing by the author
Version diffCompare plan vs. review text mechanicallySilent edits of the original intent
Hindsight isn't a feeling — it's an information problem, and it has procedural fixes.

Journal Checklist

  • Was the review written before the outcome was replayed?
  • Is the information available at each decision reconstructed, not assumed?
  • Are 'I would have...' claims supported by pre-written fields?
  • Is there any post-hoc editing of the original entry? (There must not be.)
  • Does the review separate 'was knowable' from 'turned out'?

Review Note

Review decisions at the time they were made, not at the time the outcome became visible. The journal is a time machine only if its timestamps are honest.

Frequently Asked Questions

Only if you let it — procedural fixes exist: review before replay, blackout later data, diff versions. Hindsight is a procedure failure, not a human constant.

At each decision point, write what you'd do with only the information visible then — before unblinding. It turns 'I would have known' into a checkable claim.

Because the author can't see their own smoothing. A peer with only the pre-written fields can mark interpretation drift the author is blind to.

Continue Exploring