Skip to content
CyclepediaThe trading encyclopedia
ITENESPT-BRFRDE
Learning path Bronze Understand and protect

Trade lesson: evidence and verification

A trade lesson connects evidence, comparison, and a verifiable action; it does not turn one profit or loss into a certain causal claim.

On this page

Who this is for — Readers who want to turn the review of a trade into an observable action without deriving a general rule from P&L alone.

A trade lesson is the controllable output of a review: it connects evidence, comparison with a prior rule or expectation, a provisional hypothesis, and a future verifiable action. It is not a certain explanation of why the market moved, and every trade need not produce a new rule.

The statement “I lost, therefore the entry was wrong” uses the outcome as evidence of decision quality. “The order was submitted before the condition specified in the plan” instead describes a verifiable discrepancy. The conclusion insufficient evidence, no change is valid when the record does not support a comparison or the case is isolated.

In plain terms — A useful lesson states what was observed, which action will change in a defined situation, and how application of that change will be checked.

From event to verification

Four steps for constructing a verifiable lesson The diagram connects trade evidence, comparison with the rule, a conditional action, and verification across comparable cases. Evidence → comparison → action → verification 1. EVIDENCE Rule and ticketFills and timesContemporaneous notes 2. COMPARE ExpectedObservedRecorded discrepancy 3. ACTION If situation X,then action YObservable criterion 4. VERIFY Comparable casesAction applied?Retain or revise The lesson remains an operating hypothesis until new observations support or contradict it.
A useful review ends with a future check, not a certain explanation of the past. Use the keyboard or pointer to explore.

Anatomy of an observable lesson

Field Question Cautious output
Evidence What do orders, fills, timestamps, and notes show? Facts separated from interpretations
Reference Which rule or expectation was valid beforehand? Identifiable version and criterion
Classification
mistake
 Label supported by the record
Hypothesis Which explanation deserves a check? Provisional proposition, not declared causation
Action What will I do when a defined condition recurs? Observable “if X, then Y” instruction
Verification Across which next comparable cases will I check it? Criterion chosen before seeing new outcomes

This structure is a Cyclepedia editorial operationalization. Research on after-event reviews and debriefs comes from organizational, training, and experimental contexts: it supports structured review but does not establish that a journal produces trading profits.

Review procedure

  1. Preserve the facts first: setup, orders, executions, costs, and the applicable rule.
  2. Write expected and observed events separately, without using P&L as the explanation.
  3. Classify the process; when data or the rule is missing, record not assessable.
  4. Formulate at most one bounded change for the observed problem.
  5. Translate it into a conditional action. Research on implementation intentions examines plans that specify when, where, and how to act; it does not guarantee a trading outcome.
  6. Define in advance which cases will count as comparable and which evidence will retain, revise, or reject the lesson.

Example — Retrospective narrative: “the breakout trade closed at a loss, so breakouts do not work.” Verifiable lesson: “the rule required condition A, but the order was sent first. If A is absent at the cutoff in a future comparable case, I do not submit the order; I record application and outcome separately.” The number of cases and review window belong in the plan and are not chosen after results are known.

Successes, losses, and no lesson

Review is not limited to losses. Ellis, Mendel, and Nir's laboratory study examined after-event reviews following successful and failed experiences and found that what was learned depended on the type of review. A profitable trade with a deviation therefore also warrants analysis; an adhered-to loss does not require a change.

It is valid to close the review with no new lesson when the rule was applied, the outcome falls within expected variability, and no new evidence emerges. Changing the procedure after every trade makes consistent comparison impossible.

Limit — The outcome of one trade does not by itself identify a general cause or validate a rule. A lesson describes a bounded operating experiment; it is not financial advice, a forecast, or a promise of improvement.

Sources

Suggest an edit My proposals