Slippage memory
One ugly fill can change the way a trader behaves for days. A stop slips four pips on a news spike. From then on, entries are hesitant, stops are placed wider than the plan, and the size drops.
The hesitation is understandable. It also creates a distorted version of the strategy, one that the original testing never covered. Wider stops with smaller size are not the same system.
The flinch tends to fade after a few weeks, but by then the damage to the results has been done. A strategy that works on its original parameters may seem broken, and the trader starts changing it.
A cleaner approach is to separate cause from effect. Was the slippage a one-off, caused by an event that the strategy should avoid? If so, add a filter and move on. If it reflects a persistent cost, adjust the model and retest.
Letting a single event rewrite the rules is a recipe for inconsistency.
Has a single bad fill ever led to a change in strategy that turned out to be unnecessary?
Slippage memory
Slippage memory
It’s Fairman 
-
FXS Prop Desk
- Posts: 1689
- Joined: Wed Oct 07, 2026 9:52 am
Re: Slippage memory
The distorted strategy point is well put. One antidote is to look up the actual slippage distribution from the log after an ugly fill. Seeing that the four-pip slip was one of a few in hundreds of trades puts it back in proportion, and the original plan can resume at normal size.
FXS Official Team | The Idea Lab & Strategy
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: Slippage memory
Yes, and it cost me more than the slip itself did. I had a stop on EURJPY jump almost six pips during a Bank of Japan headline, and for the next couple of weeks I kept nudging my stops wider and halving size without really admitting I was doing it. My win rate went up a little but the average winner shrank, and the month ended worse than if I had just taken the hit and carried on.
What I do now is keep a small spreadsheet that only tracks slippage per trade, entry and exit separately. After a bad fill I look at the last two hundred rows before I touch anything. Nearly every time the bad one turns out to be an outlier tied to a scheduled event I should have been flat for anyway.
So the change I made was a calendar filter, not a new stop distance. Ten minutes either side of high impact releases on the currencies I trade, and the flinch went away because the cause was handled.
What I do now is keep a small spreadsheet that only tracks slippage per trade, entry and exit separately. After a bad fill I look at the last two hundred rows before I touch anything. Nearly every time the bad one turns out to be an outlier tied to a scheduled event I should have been flat for anyway.
So the change I made was a calendar filter, not a new stop distance. Ten minutes either side of high impact releases on the currencies I trade, and the flinch went away because the cause was handled.