Trade outcome versus the quality of the decision process — how to judge decisions independently of the result

A trade that follows the plan can end in a loss, while an entry made without checking the conditions can turn a profit. In this article's illustrative examples, EUR/USD turns five pips short of the target, while another position, opened against the rules five minutes before a data release, earns USD 300. If we change the plan after the first and approve the second, we are judging decisions solely by their results. We will show how to separate execution compliance from financial outcome, assess the process against prior criteria and recognise when evaluating the rules requires a much longer series of observations.

Four combinations of process and outcome — the most expensive one is the profit that arrives against your own rules.

Hide the result long enough to apply the prior criteria

Suppose two reviewers receive the same order record, but only one sees the profit. If their process verdict changes solely because of that extra column, they are no longer assessing the same information set. A simple review exercise is to classify the recorded conditions first, save that verdict and then reveal the result. This is a way to expose a change in judgement, not a proven cure for outcome bias.

Our invented protocol requires a checklist recorded before submission, a volume no greater than 0.20 lot and no active entry ban. All three are mandatory; one passed condition cannot compensate for another that failed. The four decisions below are fictional, and their USD results are already net of all assumed costs. No other cash adjustments occur. We assess compliance with these rules, without assuming that the rules themselves identify a profitable strategy.

Keep an unresolved record separate from a known failure

Hypothetical review records, before using the outcome column
DecisionPrior checklist recordVolumeActive entry banNet result
AComplete0.15 lotNo−18 USD
BComplete0.25 lotNo+42 USD
CMissing evidence0.10 lotNo+11 USD
DComplete0.20 lotNo+9 USD

A and D have confirmed passes for all stated conditions. Equality with the volume ceiling is permitted, so D passes. B has a confirmed volume breach. C passes volume and the ban check, but the missing checklist evidence leaves its overall status unresolved. Do not convert it into either a confirmed pass or a proved omission merely to complete a two-category chart.

Averaging the three conditions could give B a seemingly favourable score while hiding a breach of a mandatory condition. That is why this protocol uses a gate, not a compensating average. A different scoring design would need to say which criteria are optional and why. The classifications above remain the same when the result column is covered.

Reveal the money and retain both kinds of record

The full net total is −18+42+11+9=44 USD. The two confirmed-compliant decisions together lost 9 USD, the known breach earned 42 USD, and the unresolved case earned 11 USD. Those sums do not show that breaking the rule improves performance. The groups contain different decisions, and no comparison design or representative sample was supplied.

The result also does not resolve C’s missing evidence. A profitable unknown remains unknown until the relevant record is recovered. Baron and Hershey’s original outcome-bias experiments examined how knowledge of an ending changed evaluations in hypothetical medical and gambling scenarios. They did not validate this trading protocol. The reason for keeping the columns separate is to make clear which evidence supports a compliance finding and which describes the financial result.

Name the denominator before reporting improvement

Of the 4 decisions, 3 are assessable as a confirmed pass or failure, giving evidence coverage of 3/4=75%. Among those 3 assessable decisions, 2 pass, giving 2/3≈66.67% confirmed compliance. Across all 4 decisions, the share with a confirmed pass is 2/4=50%. These are different summaries of the same record, not competing answers to one question.

Report the unresolved count beside any rate. Dropping C without disclosure makes it easier to mistake a change in documentation for a change in behaviour. Keep the original verdict, the later evidence and any revised status with their dates. Compliance review can identify an execution issue while leaving rule quality open; evaluating the rule needs a separate analysis of opportunities, outcomes, costs and alternatives. The detailed lesson develops that separation. A loss should not automatically reverse a documented pass, and a profit should not automatically erase a known breach.

Three exercises with worked answers

The exercise data are hypothetical. Choose an answer, then check the calculation.

1. What is the process status of decision C on the available record?

Volume and entry-ban checks pass; the prior checklist evidence is missing; net result is +11 USD.

Show the answer and explanation

C. Keep an unknown category and seek the record. Do not infer the missing process from the cash outcome.

  • A. A result does not establish the missing prior condition.
  • B. Missing evidence does not prove what happened.
  • C. Correct: the missing mandatory-check evidence leaves the overall classification unresolved.
  • D. Two passes cannot supply evidence for the remaining mandatory condition.
2. What is the net total across all four decisions?

Net results: −18 USD, +42 USD, +11 USD and +9 USD.

Show the answer and explanation

D. Include every stated result once. The total does not establish that the breached rule should be removed.

  • A. That is the total of the confirmed-compliant subgroup only.
  • B. That is the known-breach result only.
  • C. That omits the negative result while adding the gains.
  • D. Correct: −18+42+11+9=44 USD.
3. What is the evidence coverage for a confirmed overall verdict?

Three decisions have a confirmed pass or failure; one is unresolved; four decisions were reviewed.

Show the answer and explanation

B. Coverage concerns whether the record permits a confirmed verdict, not whether that verdict is a pass.

  • A. That is the share of all decisions with a confirmed pass.
  • B. Correct: 3/4=75%.
  • C. That is compliance among assessable decisions, with another denominator.
  • D. That silently treats the unresolved decision as resolved.

Continue to the two separate review loops

The detailed lesson preserves the illustrations and research on outcome and hindsight bias. The introductory record separates compliance, missing evidence and net results before assessing the broader rules.

1. Two trades, four possible verdicts

Start with the first one. You open a long on EUR/USD at 1.0820, after a bounce off a demand zone described in your catalogue of setups. Stop loss at 1.0780, target at 1.0900 — both placed before the click, risk at the level written into the plan beforehand. Price goes north, reaches 1.0895 and turns. Five pips short of the target. It comes back to 1.0780 and you are stopped out.

Was that a bad decision?

No. It was a decision taken according to a condition that was in force before entry, with risk limited in a way planned in advance. The fact that it fell five pips short of the target changes nothing about the information you held when you clicked. It changes only the result — and the result of a single trade is one draw from a distribution, not a verdict on the accuracy of the choice.

The second trade from the same week. Illustrative example: Friday at 14:25 in platform time, five minutes before a labour-market release scheduled for 14:30. You do not check the calendar. You go long GBP/USD on a candlestick pattern from the fifteen-minute chart, with no protective order, in a size larger than your plan allows. The data comes out weak for the dollar, sterling rises sixty pips, you close with three hundred dollars of profit.

Was that a good decision?

Also no. The entry condition was never checked, the position size did not follow from a rule, and a position without a protective order has no defined risk — you cannot say how much you could have lost, because no level existed at which you would exit. Had the data come out the other way, the only limit on the loss would have been the moment you managed to react by hand. The profit proves nothing here beyond the fact that the distribution has two sides and this time you landed on the favourable one.

Matrix of process quality and trade outcome Four rectangles arranged in two columns and two rows. The columns describe the outcome: left a profit, right a loss. The rows describe the process: the top one compliant with the plan, the bottom one non-compliant. Quadrant one, top left on a green background, is a compliant process with a positive outcome, the process verdict is positive and the result does not change it. Quadrant two, top right on a yellow background, is a compliant process with a negative outcome, the verdict is still positive, described as the one most often wrongly punished. Quadrant three, bottom left on a light red background, is a non-compliant process with a positive outcome, the verdict is negative, described as the hardest to recognise. Quadrant four, bottom right on a darker red background, is a non-compliant process with a negative outcome, the verdict is negative, the only one legible on its own. Below the matrix a grey bar carries the caption that the process verdict recorded in the rows is formed without knowing the column. OUTCOME Profit (+) Loss (−) PROCESS Compliant Breached QUADRANT 1 Compliant process, positive outcome Process verdict: positive The result does not change it QUADRANT 2 Compliant process, negative outcome Process verdict: positive A loss does not prove a breach QUADRANT 3 Breached process, positive outcome Process verdict: negative Profit does not justify a breach QUADRANT 4 Breached process, negative outcome Process verdict: negative A loss alone does not reveal the process The process verdict (rows) is formed without knowing the column.
Four combinations of process quality and outcome. The "outcome" column does not enter into the verdict on the row — process criteria must be checkable even while the result is still unknown.
QuadrantIllustrative exampleVerdict and its justification
1. Compliant process, positive outcomeEntry condition met and recorded before the click, exit levels placed, target reached without interfering with the positionPositive. The result does not raise it — it would be identical had price turned five pips short of the target
2. Compliant process, negative outcomeThe same trade, except that price turns short of the target and exits at the stopPositive, unchanged. This is the quadrant where the decision to change the rules is most often taken — usually with no grounds, because a single observation says nothing about them
3. Breached process, positive outcomeEntry without checking the calendar, position larger than the plan, no protective order — a profit after the data releaseNegative. The result may encourage repetition of the breach, but profit does not establish safety; the missing condition and protection remain visible in the record
4. Breached process, negative outcomeEntry after the move, without a condition from the catalogue, with the stop moved while the position was openNegative. The only quadrant where both verdicts agree — and precisely for that reason the least instructive

Those two trades sit in quadrants 2 and 3 of this matrix. Quadrant 4 is recognised without difficulty: you broke a rule and you paid, the conclusion writes itself. Quadrant 1 causes no trouble either. The problem is the other two — because there the verdict issued by the result is the opposite of the verdict issued by the process, and the result is visible immediately, whereas the process had to be described earlier for you to be able to return to it.

Quadrant 3 deserves particular attention during review: a breach is accompanied by a profit. That result may obscure the departure and encourage repetition, but the example does not establish that this will happen in a particular trader. The profit is immediate and visible, whereas the consequences of omitting a protective order cannot be assessed from this one trade. If the behaviour repeats, examine its premises and execution rather than assume carelessness or a particular learning mechanism. The favourable outcome is real; it does not establish the quality of the process.

Compliance with the process is not the same as edge. A trader can run an exemplary process on a set of rules that has no edge — the process scorecard will then be full of top marks while the account shrinks. Compliance is a necessary condition for judging the rules honestly, not a sufficient condition for their profitability. The answer to the question of whether the rules themselves make sense belongs to article 8.2 and cannot be replaced by better execution discipline.

The opposite overcorrection is equally expensive. The sentence "the result does not matter" is false: the result is information, only about something other than it appears to be, and it requires a different number of observations. We return to this in section 8, where I show a situation in which the result says a great deal about the process.

2. Outcome bias — judging a decision by its result

The phenomenon has a name and it has a study. Outcome bias is the shift in how the quality of a decision is judged under the influence of information about its result, with the information available at the moment of choice held constant. The point is not that we know more after the fact — the point is that the same decision, described identically, receives a different score simply because a different ending has been appended to it.

Study card. Jonathan Baron and John Hershey, "Outcome bias in decision evaluation", Journal of Personality and Social Psychology, 1988, 54(4), 569–579[1]. A series of experiments in which participants rated the quality of decisions described in short scenarios — medical ones (consent to surgery with known risk) and gambling ones (a bet with a known payoff distribution). Only the ending was manipulated: the description of the decision, the available information and the probabilities stayed the same. Participants: students in the United States; the medical scenarios and gambles were hypothetical. The first study involved 20 University of Pennsylvania undergraduates paid for their participation time. Finding: the same decision was rated more highly when it happened to end well — including by raters who explicitly declared that the outcome should not affect the rating. Limitations: this is a laboratory experiment on descriptive scenarios, not a study of traders; what I carry over from it is the evaluation mechanism, not the effect size or its scale in the market — [EXTRAPOLATION].

It is worth noting what this definition does not cover, because trading texts push three different things under the same name.

This is not inference from a small sample. Judging a set of rules after three trades instead of two hundred is a problem of statistical power, described as the law of small numbers by Amos Tversky and Daniel Kahneman in 1971[4] — the respondents there were professional researchers, and they still systematically overestimated the repeatability of results obtained on small samples. The mechanism is covered by article 10.1. You can commit both errors at once and usually do, but the countermeasures differ: for a small sample, waiting before concluding helps; for outcome bias, waiting does not help at all.

This is not a rational updating of belief. If after a trade you learn something that could not have been known earlier — that the instrument behaves differently at this hour of the day, that your entry condition was defined ambiguously — the update is correct. The criterion is simple: does the new information concern the rule, or only the result.

This is not a recency effect. Overweighting the most recent observations (recency bias) concerns which data you take into account. Outcome bias concerns the criterion by which you judge them. The catalogue of the cognitive biases themselves is kept in article 10.3.

In practitioner literature the same error is sometimes called resulting — a term popularised by Annie Duke, a poker player and the author of a book on decisions under uncertainty[7]. The name is convenient and it caught on, but the register has to be flagged: this is a concept from a handbook, not the finding of a study. The popularity of the term proves nothing — the proof is the work of Baron and Hershey, not the number of people repeating a slogan.

3. Hindsight bias — why yesterday's chart is a bad teacher

Outcome bias has a younger brother that spoils learning from history even more effectively. Hindsight bias is the systematic inflation, once the result is known, of the belief that the result was predictable — including a false memory of having predicted it beforehand.

Study card. Baruch Fischhoff, "Hindsight ≠ foresight: The effect of outcome knowledge on judgment under uncertainty", Journal of Experimental Psychology: Human Perception and Performance, 1975, 1(3), 288–299[2]. Participants (students) were presented with descriptions of historical events and clinical cases with uncertain endings and asked to estimate the probability of several possible resolutions. Some of them were told in advance how the case had ended. Finding: the groups informed of the ending assigned it a markedly higher probability — including when they were asked to judge as though they did not know it. Status: the effect has been replicated many times; a 2004 meta-analysis by Guilbault and colleagues covered more than ninety studies and confirmed its existence, while pointing out that the average effect size is small and depends on how it is measured[3]. Limitations: laboratory, descriptive tasks, no financial stakes — the [EXTRAPOLATION] to trading concerns the mechanism, not the scale.

The manifestation in trading is banal and therefore dangerous. You open last week's chart. You see the breakout, the pullback, the continuation. Everything is in place, every level exactly where it should be. The difficulty is that you are looking at a chart whose right edge no longer exists. On Thursday at 11:40 that same chart ended in the middle of a candle, two other scenarios stood beside it, and the entry condition was either met or not — and which of those was visible at the time cannot be reconstructed from memory after the fact, because memory has been overwritten by the ending.

The same chart, two readings. Thursday, 11:38. Price tests the zone for the second time in two hours, the higher timeframe remains in a downtrend, a medium-importance data release is forty minutes away. At least three scenarios are in play: a bounce off the zone, a break with continuation, consolidation into the release. The catalogue condition is met for the first of them. Friday, 18:00, the same candle — now in the middle of the chart. You can see that the zone held and that the move went further than the target assumed. The second reading is true and useless for judging the decision: it contains no information about what was visible at 11:38, only about what emerged from it. The question that makes sense on Friday is a different one — whether the catalogue condition really was met on Thursday. The answer to that is not on the chart. It is in the record made before the decision, or it does not exist at all.

This is where the sentence that shows up most often in a weekly review comes from: "it was obvious, after all". It was not. It was one of several scenarios that looked comparable at that moment, and it became obvious only once the right-hand side of the chart had been drawn in.

Hindsight bias should not be confused with ordinary knowledge acquired later. If after two hundred trades you notice that your entry condition behaves differently in the first hour of the session, that is a conclusion from data, not an illusion — provided you do not claim you knew it before collecting the data. The line runs exactly there: between "now I know" and "I knew".

A practical safeguard is to record the information and the condition before the outcome is known. This does not guarantee impartiality, but it provides a reference independent of later recollection. Compare it with the execution history rather than rely solely on memory or a promise to be more honest in the next review.

4. Self-attribution — the profit is mine, the loss is the market's

The third mechanism does not distort the judgement of a single decision, but the reckoning of a whole series. Self-attribution is an asymmetry in assigning causes: successes are explained by internal factors (skill, preparation, feel), failures by external ones (the market, the broker, the news, bad luck).

Study card. Amy Mezulis, Lyn Abramson, Janet Hyde and Benjamin Hankin, "Is there a universal positivity bias in attributions?", Psychological Bulletin, 2004, 130(5), 711–747[5]. A meta-analysis covering 266 studies of attribution asymmetry. Finding: the average asymmetry is large (d ≈ 0.96) but varies strongly across age groups, cultures and task types — which makes it a group-level regularity, not a constant describing every individual. Caveat: Dale Miller and Michael Ross had already shown in a 1975 review that part of this asymmetry can be explained by the way information is processed rather than by defence of one's self-image[6]. The dispute about the mechanism is unresolved; the observation of the pattern itself is well documented. Populations: mostly non-trading — [EXTRAPOLATION].

The consequence for a trader is arithmetic, not moral. If profits go to the "skill" account and losses to the "conditions" account, then after a few dozen trades the picture of your own process is skewed in one direction regardless of what the process actually looked like. The gap between declared and actual accuracy grows with it — what article 10.3 describes as poor calibration, as opposed to plain overconfidence.

Beware the other side of the same coin: the sentence "take every loss on yourself" is not a countermeasure, only an inversion of the error. Some losses really do come from conditions you had no influence over, and attributing them to yourself distorts the reckoning just as badly. The countermeasure is not severity towards yourself, but a criterion fixed earlier than the event it is meant to judge.

5. The pre-decision record — a reference for assessment

The mechanisms described can influence evaluation once the outcome is known. That is why part of the journal should be written before the order: it preserves the information available when the decision was made. A post-close entry is also needed, but it cannot replace the prior plan. Separating these records helps assess execution without relying solely on later reconstruction.

A record of a decision has three time layers: what was created before the click, what was written down while the position was open, and what was appended after the result became known. The full construction of a journal built on this split — the complete set of fields, the breach codes and the review protocol — is described in article 10.8; here only one thing is needed from it.

The first layer precedes the outcome, so it should be retained without later alteration. Record new information or a revised plan separately, with the time and the reason. The same information reconstructed only after a position closes may already contain confidence or a rationale fitted to the ending. That need not be deliberate falsification; memory is susceptible to reconstruction. The earlier record allows discrepancies to be identified, although it does not remove every source of judgement error.

Procedure: the minimal pre-decision record. Trigger: the intention to place an order. Action: three fields — entry condition, degree of conviction on a 1–10 scale, exit level — written anywhere with an automatic timestamp, before the click. Completion criterion: the entry exists and carries a timestamp earlier than the opening of the position; after that the entry is closed and not subject to editing. Audit: every week you compare the number of entries with the number of positions in the account history. How you will know it is not working: if after four weeks the share of trades without an entry is not falling, the problem is not in the content of the form but in when and where it is being filled in. What to do then — and why shortening the form further is precisely what does not help at that point — is settled by the entry audit procedure in article 10.8.

A separate note about scales. The degree of conviction serves to compare your own entries against each other, not to measure anything — the limitations of self-report scales, and the apparent precision they introduce, are discussed in article 10.8.

6. The process scorecard — criteria checkable without knowing the result

To limit judgement of the process by its outcome, define criteria that a reviewer can assess without knowing the profit or loss. If an answer requires the result column, the criterion also concerns the outcome. This is a useful test for a compliance scorecard; it does not guarantee complete impartiality or replace a separate assessment of the rules.

Five questions that pass this test:

  1. Was the entry condition met before entry — according to the description in the catalogue, and not according to a justification appended later?
  2. Did the position size follow from a rule in force before the session? The rule itself and its level come from section 9 — here you check only whether it was applied.
  3. Were the exit levels placed before entry, and did any later changes comply with the plan?
  4. Was the decision taken inside a time window in which you are allowed to trade under your own plan?
  5. Were the premises documented before the click?

Each of these questions has a "yes" or "no" answer and each can be checked against the order history and against the first layer of the record. None requires knowing the result. That is the difference between a process scorecard and a subjective mark of "that trade was fairly good".

What this evaluation does not tell you. First — it is issued by the same person who took the decision, so it is self-report data, not an external measurement. Second — the absence of an entry about a breach does not mean there was no breach; it means it was not recorded, and the entries that go unrecorded are most often exactly the ones that would have been most useful. Third — high compliance does not translate into results and should not be presented as if it did: it says only that the rules were executed, so they can be judged honestly. Fourth — order matters: a scorecard filled in after seeing the result should be treated as weaker data than the same scorecard filled in earlier, and it is worth noting that in the journal.

There is one more way of evaluating a process that looks sensible and is a trap. It is tempting, after fifty trades, to split them into compliant and non-compliant, compare the results of the two groups and treat the difference as proof that the process works. Such a comparison describes an association between compliance and outcome, rather than proving an effect of the process. It is not necessarily outcome bias when compliance criteria were fixed in advance; it does require attention to differences between the groups and cautious inference.

Breaches may coincide with losing streaks, the end of a session, larger positions or particular market conditions. Compliant and non-compliant groups may therefore differ from the moment they are formed. The direction also needs checking: earlier losses may affect later actions, breaches may affect subsequent outcomes, and both may have common causes. Splitting fifty observations into two groups cannot by itself distinguish these possibilities. Use criteria defined beforehand and account for differences in conditions.

The process metric that makes no appeal to the result is simply the frequency of breaches and its distribution over time: how many decisions out of ten carried a full set of five "yes" answers, how that number changes from week to week, after which events it drops. These are questions whose answers require no look at the result. The construction of the journal itself, the breach codes and the review protocol are described in article 10.8; designing the procedures meant to limit those breaches — article 10.7.

Five observable process criteria with yes, no or missing-data responses; financial outcome is recorded separately.
An illustrative scorecard of the article’s criteria. It checks execution against the prior plan; it neither grades emotions nor proves that the rule has an edge.

7. How many observations before the result means anything

Since the result is information, the question remains how much of it is needed. The answer is uncomfortable and it is worth seeing it calculated rather than hearing it as advice about patience.

Take the simplest quantity a trader observes: the share of trades that end in a profit, that is the win rate. Assume that successive trades are independent and that the true win rate is constant. Both assumptions are violated in practice and I return to that below; under such assumptions, however, the arithmetic is at its most optimistic, so the conclusions are all the stronger.

The standard error of the observed win rate is:

SE = √( p × (1 − p) / n )

For a true win rate of 50%, the normal approximation gives the following ranges covering approximately 95% of observed proportions. They are rounded; an actual proportion in a finite sample takes discrete values:

Number of tradesStandard errorApproximate win-rate range (about 95%)
2011.2 ppfrom 28% to 72%
507.1 ppfrom 36% to 64%
1005.0 ppfrom 40% to 60%
2003.5 ppfrom 43% to 57%
4002.5 ppfrom 45% to 55%
10001.6 ppfrom 47% to 53%

Reading this table is simple. A set of rules with a true win rate of 50% can, after twenty trades, produce a reading in the broad approximate range of 28–72%; possible readings are multiples of 5 percentage points. After a hundred, a reading of 41% and a reading of 59% are both still within the norm — and that is precisely the range in which a trader usually decides to change something.

Distribution of the observed win rate for three sample sizes Three density curves on shared axes. The horizontal axis shows the observed win rate in the sample from twenty to ninety per cent, the vertical axis shows density with no scale. Two dashed vertical lines stand at fifty per cent and at fifty-five per cent, where the true win rate lies. All three curves peak in the same place, exactly at fifty-five per cent, and differ only in width and height. The dashed curve for a sample of twenty trades is the lowest and widest, running from about twenty-two to about eighty-eight per cent, with its peak just above the horizontal axis. The curve for a hundred trades is clearly narrower and taller, spanning roughly thirty-five to seventy-five per cent. The curve for five hundred trades is the narrowest and tallest, closed roughly between forty-four and sixty-six per cent. The larger the sample, the higher the peak and the smaller the spread. Sample hit rates when the true rate is 55% Observed hit rate in the sample Density 20% 30% 40% 50% 60% 70% 80% 90% 50% true hit rate 55% n = 20 n = 100 n = 500
The distribution of the observed win rate when the true win rate is 55%, for three sample sizes. At twenty trades a reading below 50% is common, even though the rules are better than a coin flip. The curves show density under the normal approximation: the wider the spread, the lower the peak. Axes calibrated on the standard error of a proportion.

The practical question, however, is a different one: how many trades does it take to tell a 55% win rate from a 50% one? For a one-proportion test, at a significance level of 0.05 and 80% power, it works out at roughly 620 trades in the one-sided version and roughly 780 in the two-sided one. A simulation check for a one-sided normal-approximation proportion test (α = 0.05), so that the formula is not the only argument here: drawing 200,000 series of trades with a true win rate of 55% (seed 20260810), the difference is detected in 24% of runs at 100 trades, in 64% at 400 and in 88% at 800.

What this calculation does not say. It does not say that six hundred trades bring certainty, or that a smaller sample can provide no evidence. The sample size describes a specified test power for a particular difference; it is not a universal threshold of knowledge. Nor does it say anything about profitability, because the win rate alone does not determine it: a set of rules that wins three trades out of four can have a negative expected value if the average win is sufficiently smaller than the average loss; that calculation belongs to article 8.2. Finally: the assumption of a constant win rate is a computationally convenient fiction. Market conditions change faster than six hundred observations can be gathered, so a sample that is statistically sufficient may already describe a different period. That is an argument for judging execution more often than the rules, not for judging the rules faster.

It is worth recalling here the calculation from article 10.1: at a 50% win rate, a run of five losses in a pre-specified sequence of trades has a probability of (0.5)⁵, that is about 3%, while the probability of such a run occurring anywhere within 100 independent trades is about 81%. A losing streak alone therefore does not establish failure — it can also occur under unchanged rules.

An analogy that puts this in order: an actuary at an insurance company does not change the tariff after one large payout. He changes it when the loss ratio departs from the assumption across the whole book of policies. He is not braver than the trader — he simply has a sample of the right size from day one. After a month the trader has a dozen or so observations and the same need to draw a conclusion.

Exact distribution for an illustrative model of twenty independent trades, each +1R or −1R, with a 55% win rate. Mean total is +2R; a negative total occurs with about 24.9% probability. The assumptions do not describe a real system.
An illustrative exact distribution for twenty ±1R outcomes at a 55% win rate. A +2R mean coexists with about 24.9% probability of a loss; the assumptions are not evidence of a real rule’s edge.

8. Two loops: judging execution and judging the rules

Execution and the set of rules need separate reviews, with different criteria, frequencies and sample sizes. Confusing them can lead to settings being changed after a few losses without checking whether the rule’s basis has changed. The distinction organises the analysis, but it does not automatically resolve every execution or strategy problem.

The two evaluation loops set side by side Two rectangles of the same size lying side by side, with no arrows or connections between them. Each has a heading and six description rows arranged in the same order. The left rectangle on a light blue background is the execution loop: it asks whether the trader did what he wrote down, runs weekly, works on a few to a dozen or so decisions, judges compliance rather than the result, does not need to know the outcome, and in its last row names as owner this article together with the article on the journal. The right rectangle on a light purple background is the rules loop: it asks whether the set of rules makes sense, runs rarely, once every several months, requires hundreds of trades, applies a statistical criterion, needs results in series, and in its last row names section eight as owner. EXECUTION LOOP What: did I do what I wrote down When: every week Material: a few to a dozen decisions Criterion: compliance, not result Outcome needed: no Owner: this article and 10.8 RULES LOOP What: does the rule set make sense When: rarely, once in many months Material: hundreds of trades Criterion: statistical Outcome needed: yes, in series Owner: section 8
The two evaluation loops differ in frequency, material and criterion. The question "should I change the rules" asked at the rhythm of the execution loop has no chance of getting a sensible answer.

The execution loop runs weekly and needs no results: in it you check the five criteria from section 6 and count how many decisions carried a full set of "yes" answers. The rules loop runs on hundreds of trades, requires a series of results and statistics, and its tools — edge assessment, historical testing, simulation — belong to section 8. The second loop cannot be sped up by discipline, just as a missing edge cannot be repaired by better execution.

Separating the reviews does not mean always waiting for a large sample when new information arrives. The following counterexample shows the limit of that principle.

When the result says a great deal about the process. Suppose that across successive trades the planned exit level and the level actually realised differ systematically in one direction — the exits come out worse, regardless of instrument, direction and time of day. That is not variance, and inferring from it is not outcome bias, because you are not judging a single result but a repeatable difference between plan and execution. The result plays the role of a measurement of execution here. There are at least two possible causes and they have to be separated before anything is changed: your own behaviour (moving orders, closing before the level) or the conditions of execution, meaning slippage and spread widening. You will recognise the first from the second layer of the record and the second from the order history; the tools for measuring excursions while a position is open, including MFE and MAE, are described by the workshop in section 15, and the assessment of execution conditions at a broker — by section 12. How you will know the conclusion was premature: if the discrepancy disappears once the observations are split by time of day or by instrument, it was not an execution pattern but the effect of a single time window.

Separate two questions: “What was the financial outcome?” and “Did I execute the plan according to the agreed criteria?” The plan and entry conditions can be assessed before the position opens. The full execution, including later modifications and the exit, can only be assessed after those actions, by comparing the earlier record with the order history without using profit or loss as the criterion for compliance. A separate review of a longer series assesses the economic basis of the rule.

The same distinction becomes much harder to maintain when successive decisions stop being a response to the market and become a response to the previous loss. That is the subject of the article on revenge trading and tilt (10.5): what observably changes in behaviour before the sequence goes too far.

Illustrative long EUR/USD trade: entry 1.1000, low 1.0990, high 1.1020, exit 1.1005. MFE is 20 pips, MAE 10 pips and the result before costs 5 pips.
One explicitly hypothetical trade path distinguishes MFE, MAE and outcome. These measures alone assess neither plan compliance nor a psychological cause of the decision.

FAQ — trade outcome and decision quality

Can I judge my rules after twenty trades?
Twenty trades may reveal an execution problem or provide information for a review, but usually give an imprecise hit-rate estimate. In a model of independent trials with a true hit rate of 50%, the spread is about 28–72% in the normal approximation, with readings in steps of 5 percentage points and a standard error of 11.2 percentage points. A few decisions can be checked separately against the written plan. Assessing rules from a series of results requires an appropriate sample and assumptions; new, relevant information may justify an earlier review.
How does outcome bias differ from hindsight bias?
Outcome bias concerns decision evaluation: the same decision may receive a higher score when it ended well. Hindsight bias concerns perceived predictability or memory of an earlier belief: after the ending is known, it seems more predictable or consistent with the earlier forecast. The first changes the evaluation criterion; the second changes the representation of prior knowledge. They may co-occur and reinforce each other, but both need not be present in every evaluation error.
I made money by breaking my own rule. What should I do with that?
Record the breach and the profit separately. The profit is an accounting fact; the breach remains a fact about execution even when the outcome is favourable. Check it against prior criteria using the plan and order history. The financial result alone does not reveal it. If the frequency of breaches rises after a series of such events, review the procedure; this does not automatically establish that the earlier profits caused the change.
I issue the process verdict on myself. Isn't that useless?
Your assessment may use self-report and order history; these sources have different limitations. Define criteria that can be checked in the data: whether levels were placed before entry, whether and when they were changed, when the decision occurred and whether an earlier entry exists. They do not require a scale of feelings. Completeness can be a weak point: a missing breach entry does not establish that no breach occurred. Compare the number of entries with the number of positions and retain the status of events that cannot be resolved.
Does this mean the result is irrelevant?
The result is information, but cannot by itself establish the quality of an individual decision. A series of results helps assess rules under stated assumptions. Execution data answer another question: the gap between a planned and realised level can be measured and checked for a consistent direction across orders. That measurement still requires attention to uncertainty and execution conditions. Neither discard the result nor treat it as the sole criterion.
I trade fast, I have no time to write anything before entry.
Adapt the record to the pace of work while retaining information from before the decision. Three fields — entry condition, stated confidence from 1 to 10 and planned exit level — illustrate a shorter form, rather than guaranteeing a complete assessment of every rule. Completion time depends on the tool and method. You can prepare the condition catalogue earlier or automate recording. If the form delays a decision, examine its design and when it is completed; difficulty alone does not establish impulsivity. Article 10.7 discusses how to design these arrangements.

Sources and references

  1. Baron J., Hershey J.C., "Outcome bias in decision evaluation", Journal of Personality and Social Psychology, 54(4), 1988, pp. 569–579. The evaluation of the same decision shifts with its outcome; medical and gambling scenarios, hypothetical stakes.
  2. Fischhoff B., "Hindsight ≠ foresight: The effect of outcome knowledge on judgment under uncertainty", Journal of Experimental Psychology: Human Perception and Performance, 1(3), 1975, pp. 288–299. Knowing the ending raises the retrospective estimate of its probability. Experiment 1 used four student samples (100, 80, 87 and 100 participants); some assessed multiple events. Original full text, pp. 289–290.
  3. Guilbault R.L., Bryant F.B., Brockway J.H., Posavac E.J., "A meta-analysis of research on hindsight bias", Basic and Applied Social Psychology, 26(2–3), 2004, pp. 103–117. A meta-analysis of more than ninety studies; the effect confirmed, the average size small.
  4. Tversky A., Kahneman D., "Belief in the law of small numbers", Psychological Bulletin, 76(2), 1971, pp. 105–110. Systematic overestimation of what can be inferred from a small sample.
  5. Mezulis A.H., Abramson L.Y., Hyde J.S., Hankin B.L., "Is there a universal positivity bias in attributions?", Psychological Bulletin, 130(5), 2004, pp. 711–747. A meta-analysis of 266 studies of the asymmetry in attributing causes to successes and failures.
  6. Miller D.T., Ross M., "Self-serving biases in the attribution of causality: Fact or fiction?", Psychological Bulletin, 82(2), 1975, pp. 213–225. A critique of the motivational explanation of attribution asymmetry.
  7. Duke A., Thinking in Bets, Portfolio/Penguin, 2018. The source of the term "resulting" — practitioner literature, not research.

Your learning progress

Finished this lesson? Mark it yourself. Opening or scrolling a page never marks it complete.

Progress requires JavaScript and browser storage.

Saved only in this browser. No account or cross-device sync. Clearing site data can erase your progress.

Jarosław Wasiński

Editor-in-chief, ForexMechanics.com • Macro & FX analyst

Independent analyst and practitioner with over 20 years of experience in financial markets. Actively involved in Forex since 2007, with a focus on fundamental analysis, OTC market structure, and disciplined capital risk management.

  • Creator and editor-in-chief of MyBank.pl, providing reliable financial education since 2004.
  • Author of hundreds of in-depth market commentaries, structural analyses, and educational materials for traders and investors.
  • Advocate for market transparency, promoting education grounded in hard data and institutional reports (BIS, ESMA, CFTC).

All content is educational and informational only – it does not constitute investment advice or a recommendation. Remember: leveraged trading (Forex/CFD) carries a high risk of rapid capital loss.