ORB Trading Strategy Review
Periodic review of an opening range breakout strategy treated as its own discipline: telling a real defect from an ordinary losing run, reviewing on a fixed interval, and retiring a setup properly.
Reviewing and Trading Are Different Jobs
The same person does both, usually on the same day, which is why they blur. Trading is executing a decision that was already made. Reviewing is deciding whether that decision should still stand. Done at the same time, the second contaminates the first, and a rule that is under review while it is being applied is not really a rule. Keeping the two activities in separate slots, with different questions attached to each, is the cheapest structural improvement available to most people running a fixed setup.
A Loss Is Not a Reason to Review
Any approach with a real edge still loses regularly, and the losses arrive in clusters because that is how randomness looks from the inside. A run of bad sessions therefore carries almost no information about whether the strategy has stopped working, while producing an overwhelming feeling that it has. Reviewing at that moment means reviewing under the influence of the one input that is least diagnostic and most persuasive, which reliably produces changes that would not survive a calm reading of the same record.
Schedules Remove the Argument
The alternative is to decide when reviews happen before knowing what they will contain. A fixed interval means the review after a good month and the review after a bad one are the same event, examined with the same questions. It also means the urge to change something in the middle of a difficult stretch has a place to go, which is the next scheduled review, rather than being either acted on immediately or suppressed until it comes out sideways.
Changes Have Costs That Are Easy to Miss
Every alteration to a setup resets the history against which it can be judged. The sessions recorded before the change describe a different strategy, and the new version has no track record at all. Someone who adjusts something every few weeks never accumulates enough observations of any single version to know whether any of them worked. Stability is not conservatism in this context. It is what makes evidence possible.
Reviewing the Strategy Itself
The articles here treat review as its own discipline, separate from execution and separate from strategy design. One deals with distinguishing a setup that needs changing from one that needs leaving alone, one covers the case for reviewing on a fixed schedule rather than after a bad session, and one addresses how to tell when a setup has genuinely stopped working and what retiring it involves.
Latest Guides
Knowing When a Setup Has Stopped Working
Setups do stop working. Conditions change, an inefficiency gets crowded, the instrument that suited the rule behaves differently than it used to. Retirement is a normal outcome and not an admission of anything. The difficulty is that the early stages of a setup genuinely decaying and the middle of an ordinary losing run present in almost exactly the same way, and there is no test that separates them cleanly.
Why the Evidence Arrives Late
Deciding whether a strategy has stopped working means comparing its recent behaviour to its historical behaviour and asking whether the difference is larger than chance would produce. For an approach taking roughly one trade a session, the number of observations accumulates slowly, and the variation between stretches is wide.
The uncomfortable consequence is that by the time the evidence is strong enough to be convincing, a substantial period has already passed. There is no way around this that does not involve reacting to noise. Anyone who identifies decay quickly is also identifying it during runs that were nothing of the sort, and they will not be able to tell which was which.
Signs That Are Worth More Than Results
Because results are slow, the more useful indicators are structural. If the setup depended on a condition and that condition has visibly changed, the argument does not require a performance record. A rule built around a particular instrument's usual range behaving one way is aimed at something that is no longer there if the instrument's behaviour has shifted.
Changes in how the trades fail are also informative in a way the count of failures is not. A setup that used to lose small and occasionally lose large but now loses in a different pattern is behaving differently even if the totals happen to be similar. That is a change in the shape of the thing rather than in its outcome, and shape changes faster than averages do.
What Does Not Count
A run of losses of any length is compatible with an edge that still exists. So is a stretch where the setup fires much less often, which usually reflects conditions rather than the rule. So does the fact that some other approach has been performing better recently.
The most misleading signal is the feeling that the setup has stopped working. That feeling is produced by a losing run whether or not anything has changed, arrives at the same point in both cases, and is the reason so many setups get abandoned just before conditions turn. It is not evidence and it is very hard to treat as though it is not.
Deciding in Advance
The most practical protection is to define the retirement condition when the setup is adopted rather than when it is struggling. A stated threshold, whether in the number of sessions, the depth of a drawdown, or the disappearance of the condition the setup relies on, is a decision made without a position and without a recent loss attached to it.
Written down at the outset, it does two jobs. It makes stopping possible without an argument, and it makes continuing possible too, because a bad stretch that has not reached the threshold is explicitly within what was expected. Half the difficulty of a drawdown is not knowing whether it is normal, and a threshold written in advance answers that question at the point where it is being asked.
Stopping Without a Verdict
Retiring a setup does not require concluding that it never worked, and that framing causes real harm. It invites the interpretation that the time spent was wasted, which makes stopping feel like a loss to be avoided rather than a decision to be made.
A setup that worked and then stopped is the ordinary case. Conditions were suitable, then they were not. Recording the retirement with the evidence that prompted it leaves something usable, because conditions come round again and a setup shelved with a clear note about why can be reconsidered later on its merits. A setup abandoned in frustration leaves nothing behind but the frustration.
Review on a Schedule, Not After a Bad Day
Most reviews of a trading approach are not scheduled. They are provoked. Something goes badly, the record gets opened, and an hour is spent looking for the cause. That process feels rigorous and is structurally biased in a way that is hard to see from inside it, because the thing being examined and the reason for examining it are the same event.
Why the Trigger Corrupts the Review
A review that begins after a loss begins with a conclusion already implied. Something went wrong, therefore something is wrong, therefore the task is to find it. The record is then read as a search for a defect rather than as a description of what happened, and a record read that way will always produce a defect, because any sequence of trades contains patterns if you look for them with sufficient motivation.
The same record read on an ordinary morning, with no particular result in mind, produces different conclusions. Not because the data changed but because the question did. That difference in output from identical input is the whole argument for taking the trigger out of the reviewer's hands.
What a Fixed Interval Changes
Choosing the interval before knowing what it will contain means the review after a good month and the review after a bad one are the same procedure. Good stretches get examined too, which matters more than it sounds, because a strategy that made money for reasons unrelated to its logic is a real risk and nobody investigates it voluntarily.
A schedule also gives the urge to intervene somewhere to go. During a difficult stretch the pressure to change something is considerable, and the two usual outcomes are acting on it immediately or suppressing it until it emerges as an unplanned deviation mid session. A scheduled date is a third option: write the observation down, keep following the rule, and take it up when the review comes round.
Choosing the Interval
The interval has to be long enough to accumulate a meaningful number of sessions and short enough that a genuine problem does not run unchecked. For an approach taking roughly one trade per session, weekly is generally too frequent, because a week contains too few observations to say anything and the review becomes a discussion of individual trades.
Monthly or quarterly gives the sample time to mean something. The exact choice matters less than the fact that it was made in advance and is not renegotiated when a stretch turns bad. An interval that quietly shortens during drawdowns has become a result triggered review again, with a calendar attached for appearances.
What the Review Should Ask
Fixed questions, asked the same way each time, so that answers can be compared across reviews. Whether the rules were followed as written, and where they were not. Whether any rule turned out to be ambiguous in practice. Whether the conditions the setup depends on still describe what is being traded. What the distribution of results looks like, rather than the total.
Notably absent from that list is whether the period was profitable. It is worth knowing and it is a poor place to start, because it dominates everything read after it. A review that opens with the result will interpret every subsequent observation through it, and the observations are the part that carries the information.
Emergencies Still Exist
None of this argues for ignoring something genuinely broken until the calendar allows. A rule that cannot be executed, a defect in how a level is calculated, a change in the instrument that makes the setup inapplicable, all of these get dealt with immediately and none of them require a performance argument.
The distinction is between a defect and a result. Defects are structural, they can be described without reference to profit and loss, and fixing one is not a strategy change so much as a correction. Results are the ordinary output of an uncertain process, and they wait for the scheduled date, however much they do not feel like waiting.
When to Change a Strategy and When to Leave It Alone
The hardest question in running a fixed setup is not what to do when it fails. It is telling the difference between failing and losing, which look identical from close range and require completely opposite responses. Get it wrong in one direction and you keep something that has stopped working. Get it wrong in the other and you abandon something that was working, at the point where it was hardest to hold.
What a Change Actually Costs
The obvious cost of an adjustment is that it might be wrong. The larger and quieter cost is that it resets the record. Every session logged under the previous version describes a strategy that no longer exists, and the new version starts with nothing behind it.
Someone who adjusts something every few weeks is running a sequence of strategies, none of which has been observed long enough to say anything about. The feeling is one of continuous improvement. The reality is that no version ever reaches the point where its results could be distinguished from chance, so improvement is being asserted rather than measured.
Reasons That Justify Changing
There is a category of change that does not require any performance evidence at all, which is the correction of something that was simply wrong. A rule that turns out to be ambiguous in a situation nobody anticipated, a definition that produces different answers depending on how it is read, a step that cannot be executed reliably in the time available. These are defects, and defects get fixed regardless of whether the recent record is good or bad.
A second legitimate reason is a change in the conditions the rule depends on. If a setup was built around an instrument behaving a certain way and it has plainly stopped behaving that way, the rule is now aimed at something that is not there. That is a genuine structural argument and it can be made without reference to profit or loss, which is exactly what makes it trustworthy.
Reasons That Do Not
The most common reason for a change is a recent bad stretch, and it is the weakest. Losing runs happen to strategies with real edges, they happen more often and last longer than intuition allows for, and they feel like evidence because they are vivid and immediate.
Close behind it is the change made because a different approach has recently been performing better. Comparing a strategy in a poor stretch with an alternative in a good one is a comparison between two temporary states, and switching between them systematically means always arriving after the good stretch has finished.
The Test Worth Applying
A useful check is whether the proposed change could have been argued for before the recent results were known. If the reasoning stands on its own, referring to the mechanics of the setup or to a change in what is being traded, it is probably sound. If the reasoning requires the recent record to make sense, it is a response to discomfort wearing the clothes of analysis.
A second check is whether the change would have helped in the specific sessions that prompted it, and whether it would have hurt in earlier sessions that went well. Most adjustments made after a bad stretch are aimed precisely at the trades that just lost, which means they are fitted to a handful of recent events and would have removed unrelated good trades from the history.
Leaving It Alone Is a Decision
Doing nothing does not feel like a choice, which is why it gets no credit and takes more discipline than it should. A stretch endured without alteration is what produces a record long enough to be worth reading, and that record is the only thing that will ever settle the question properly.
There is a middle option that is often more honest than either extreme. Reducing size while continuing to follow the rule keeps the sample accumulating and lowers the cost of being wrong, without changing the strategy at all. It does not resolve anything, and it buys time for the evidence to arrive, which is usually what is actually needed.
