The day after a loss, every strategy appears easy to improve.

The stop was too wide.

The entry was too early.

The session was wrong.

The filter was too weak.

There is always something that could have prevented the latest losing trade.

So we change it.

The next trade loses too.

We change something else.

Eventually, the strategy has been modified so many times that we can no longer explain what improved or what failed.

We wanted a better system.

We removed the evidence needed to understand the original one.

Change feels like progress

Doing nothing during a drawdown feels irresponsible.

The account is declining.

The same rules are still running.

The trader feels expected to act.

So the stop is tightened.

Another indicator is added.

The trading window is reduced.

A new market-regime filter is introduced.

Editing the code provides immediate relief.

The system looks more protected.

At least something has been done.

But emotional relief and strategy improvement are not the same thing.

A change designed to reduce discomfort may not improve long-term performance.

Losses do not arrive on schedule

Strategy losses may be distributed over hundreds of trades in a test.

Live trading does not deliver them evenly.

Several losing trades may arrive together.

Different bots may fail during the same market transition.

What was expected to occur across several months can appear inside one week.

Leverage makes this concentration feel even more significant.

At small size, the week may look like ordinary variance.

At larger size, it feels like structural failure.

The market behavior is identical.

The financial pain changes the diagnosis.

A trader may believe the strategy is being evaluated objectively while actually reacting to the size of the drawdown.

One adjustment creates another

Suppose a losing streak leads to a tighter stop.

The new stop is reached by ordinary price movement.

Loss frequency increases.

The trader responds by adding stricter entry filters.

Trade frequency falls too far.

The session is expanded to create more opportunities.

The expanded session introduces different spreads and price behavior.

Another filter becomes necessary.

The first adjustment was small.

Its consequences created a chain of additional adjustments.

Later, performance improves.

Was it the tighter stop?

The entry filter?

The wider session?

Or did the market simply return to a more favorable regime?

Nobody knows.

The strategy was improved in several places and made impossible to evaluate in any one place.

Preserve the baseline

Testing requires a comparison.

Before and after.

The same market.

The same costs.

The same sizing.

The same time horizon.

When several variables change together, the comparison disappears.

A useful process preserves the original version.

Keep one bot on the old configuration.

Store the previous parameters.

Write one sentence explaining why each change was made.

Define the number of trades or amount of time required before judging it.

Record what the new rule removes, including the winning trades it may also remove.

Improvement is not only the act of adding a better rule.

It is also the discipline of protecting the evidence needed to verify that the rule is better.

I feel the same urge with trading bots

I run several MT5 bots built around different approaches.

Some are rule based.

Some receive TradingView alerts.

Some use machine-learning scores.

Some include language-model judgment.

After a losing day, the code looks full of obvious improvements.

A condition could have avoided this trade.

An earlier exit could have protected that profit.

A different filter could have rejected the setup.

Looking backward makes the answer appear clear.

But a rule designed to avoid one historical loss may remove profitable trades in another market.

Avoiding a particular loss is not the same as improving the full distribution of outcomes.

Without that distinction, a bot gradually becomes optimized for the chart that already happened.

Diagnose before changing

A negative P&L does not identify the broken component.

The problem may be the entry.

The direction was wrong, price was chased, or the setup did not fit the regime.

It may be the exit.

The stop was unsuitable, the strategy gave back profit, or it failed to respond to reversal evidence.

It may be the size.

The position was too large or several systems carried the same hidden exposure.

It may be execution.

Spread widened, orders were delayed, or retry logic behaved incorrectly.

It may be the market environment.

The strategy was designed for movement that was no longer present.

The same financial result can come from different operational causes.

Changing the full strategy before separating those causes often modifies the parts that were working.

Reduce size before rewriting logic

Maintaining the same rules during a losing period can still feel dangerous.

A practical first response is to reduce size.

This is not avoidance.

It protects the ability to observe.

At full exposure, each result carries more emotional force.

Normal variance feels unacceptable.

The need to recover becomes stronger.

Parameter changes become more urgent.

Smaller size reduces the financial pressure without immediately changing the system being evaluated.

The strategy can continue producing evidence.

Losses have less impact on the account.

A favorable regime can return without the original logic having been removed.

During a drawdown, the first goal is not always to find the answer immediately.

It may be to preserve enough capital and mental space to recognize the answer later.

Doing nothing still requires a plan

“Do nothing” can become a dangerous excuse.

A genuinely broken strategy can be allowed to continue under the label of patience.

Observation needs boundaries.

For example:

Keep the logic unchanged for the next twenty trades.

Run at half size.

Record entry, exit, spread, session, and execution quality.

Separate rule-following losses from operational failures.

Stop if the drawdown exceeds a predefined limit.

After the observation window, select only one modification to test.

This is not passive neglect.

It is a controlled period in which changes are delayed so that evidence can remain comparable.

Useful improvements are often boring

Strategy improvement is often associated with major additions.

A new AI model.

A new indicator.

A new entry engine.

A new market.

In production, the most valuable changes may be less dramatic.

Rejecting trades during excessive spread.

Improving retry logic.

Preventing duplicate exposure.

Writing better logs.

Defining restart conditions.

Correcting position-size calculations.

Each change is small.

None creates a completely new strategy.

Together, they remove repeated operational mistakes.

A modest improvement that remains active for years may contribute more than a sophisticated idea that is replaced after the next drawdown.

Activity is not evidence of improvement

A large amount of work can be completed without making the strategy better.

More code.

More backtests.

More parameters.

More filters.

The useful questions remain:

What improved relative to the original?

Did it improve in unseen periods?

Does the result survive transaction costs?

Which profitable trades were removed?

Can the change be explained and repeated?

Changing a strategy is easy.

Keeping it unchanged long enough to learn from it is harder.

That waiting period is not wasted time.

It is what makes the next adjustment interpretable.

The same pattern appears outside trading

A newsletter fails to grow, so the topic changes.

A product receives little attention, so new features are added.

A study method feels slow, so another course is purchased.

Changing the method produces a sense of movement.

But when the method changes before results have enough time to appear, no learning accumulates.

Improvement requires adjustment.

It also requires periods of stability.

Without stable periods, the effect of each adjustment remains invisible.

Preserve before you repair

There is no perfect trading strategy.

Losses cannot be removed completely.

Unexpected clusters will occur.

Rebuilding the system after each one prevents the strategy from developing a reliable history.

The answer is not to ignore poor results.

It is to slow the rate of change when poor results create the strongest urge to act.

Reduce size.

Separate the causes.

Keep the logs.

Preserve the baseline.

Change one variable.

Wait long enough to observe the result.

Before repairing the strategy, protect the process that allows you to learn what needs repair.

Is the next adjustment truly designed to improve the system?

Or is it mainly designed to make the latest loss feel easier to live with?

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit fxaibotlab.substack.com/subscribe