Every experienced trader owns two track records: the one their strategy would have produced, and the one their behaviour did. The distance between them is psychology — and it is not fixed by willpower. It is fixed by naming the failure modes precisely and building guardrails so that discipline costs as little as possible.
The classic failure modes
- Revenge trading — re-entering immediately after a loss, at double size, to "get it back". The loss was an expense; revenge converts it into a sequence.
- Overtrading — after wins as often as after losses. Euphoria and frustration both whisper that the next setup is everywhere.
- Moving stops — the moment of maximum conviction that "it will come back" is precisely the moment the rule exists for.
- Cutting winners early — loss aversion makes a small certain profit feel better than a larger probable one, which quietly destroys the +2R side of your expectancy.
Grade the process, not the outcome
In a probabilistic game, single outcomes lie. A sloppy entry that wins teaches worse habits than a disciplined entry that loses. The professional fix is to grade every trade on plan-adherence — right setup, right size, stop respected — and let the P&L accumulate meaning only over samples of dozens. A trade can be a good decision and a losing ticket on the same day.
The plan and the journal
A trading plan is one page: the setups you take, the sessions you trade, the fixed risk per trade, the daily stop. A journal is the evidence: screenshot at entry, the reason in one sentence, the exit in R, and the emotional state in one honest word. Weekly review turns both into feedback — patterns like "every Friday-afternoon trade loses" are invisible daily and obvious monthly.
Circuit breakers
Decide in advance: a daily loss limit (say 3R) after which the platform gets closed, a forced pause after three consecutive losses, and reduced size after any deep drawdown until equity recovers. These rules are not for the trader you are on a good day. They are for the other one — and every profitable desk employs both.