Most traders measure themselves by whether the last trade made or lost money. That instinct feels reasonable — money is the point, right? The problem is that in any short sequence of decisions, random noise can overwhelm skill by a wide margin. A trader can do almost everything correctly and still lose. A trader can make a reckless, underprepared decision and walk away with a gain. If you judge the decision by the result, you reward the wrong behavior and punish the right one.

This article teaches you to separate the quality of a decision from the result it happened to produce — a discipline researchers who study probability call avoiding resulting. By the end, you will be able to assess your own decisions on the process axis, not just the outcome axis, and you will understand why that distinction is the foundation of any durable trading skill.

Why the Brain Collapses Process and Outcome

The human mind is a pattern-recognition engine optimized for cause and effect. When a result is good, the brain works backward and concludes the decision was good. When a result is bad, the decision gets condemned. This is useful in stable, low-noise environments — if you touch a hot stove and burn your hand, the burn correctly tells you not to do that again. Financial markets are not a low-noise environment. A single trade result carries almost no information about whether the decision behind it was sound.

Psychologists describe this tendency as outcome bias: evaluating a decision based on information that was unavailable at the time the decision was made. The result arrives after the decision, yet the brain treats the result as evidence about the decision's quality. A doctor who performs a difficult surgery correctly but loses the patient due to a rare complication was not a bad doctor. A driver who runs a red light and makes it through unharmed was still a reckless driver. The feedback was misleading in both cases. Markets do the same thing to traders, every day.

The Mental Model: Scoreboard vs. Skill

Here is the framing that makes this concrete: in a noisy game, the scoreboard and the skill diverge in the short run and converge in the long run.

Over a handful of decisions, a poor process can produce wins and a strong process can produce losses — simply because luck is large relative to the signal. Over hundreds or thousands of decisions, the noise averages out. The scoreboard starts to reflect who actually had edge and who was being carried by randomness. Traders who build on a strong process accumulate compounding evidence that the process works. Traders who build on a lucky streak are standing on a foundation that will eventually dissolve.

This is not a comforting abstraction. It means you cannot trust short-run results to tell you whether you are improving. You have to build a second scoreboard — one that grades the process — and trust it more than the first.

What Resulting Costs You

When a trader evaluates decisions purely by outcome, two failure modes follow. The first is false confidence: a reckless decision that happened to win gets reinforced, the trader repeats the behavior, and eventually a version of that same decision arrives in a market environment where it causes serious damage. The recklessness was always there; the early wins just hid it.

The second failure mode is false correction: a disciplined decision that happened to lose gets abandoned. The trader modifies or discards the very part of the process that was working, replacing it with something reactive and unexamined. Both failure modes erode the skill base over time, even when the short-run account balance does not immediately reveal the damage.

There is an additional cost that is harder to see: the emotional volatility. If each result feels like a referendum on your judgment, your confidence becomes a function of recent luck rather than genuine competence. You feel sharp when markets happen to move your way and incompetent when they do not. Neither feeling maps to reality.

The Method: Grade the Decision Before the Result

The discipline is straightforward to describe and requires real effort to practice. Apply it in three steps.

Define what a good decision looks like before you make it. This means writing down — before the result is known — your reasoning, the information you used, the alternatives you considered, and the conditions under which your logic would be wrong. If you cannot articulate the decision in writing before the result, you do not yet have a process; you have an impulse.
Score the process, not the result. After the decision resolves, grade yourself on the pre-decision criteria, not on whether you made or lost money. Did you follow your reasoning? Were there red flags you ignored? Did you act within your prepared rules or outside them? This is the number that matters for skill development.
Track process metrics separately from P/L. Keep a simple log: decision quality score, adherence to plan, quality of pre-decision reasoning. Review these numbers across a meaningful sample — at minimum twenty to thirty decisions — before drawing conclusions about whether your approach is working.

A Hypothetical Example: Two Traders, 500 Decisions

Imagine two traders entering the same type of scenario — a volatile session after unexpected economic data. Trader A spends ten minutes reviewing the relevant context, identifies two plausible directions and the conditions that would confirm each, sets a clear exit if the confirmation does not appear, and acts within the size appropriate for the uncertainty. The trade resolves against them. They lose.

Trader B skips preparation, acts on the first impulse, sizes up because the move "feels strong," and exits late because there was no pre-defined exit. The trade resolves in their favor. They win.

Now run those same behavioral patterns forward across 500 decisions. Trader A, applying consistent reasoning, builds a record that reflects the actual quality of available information. Their losses come from genuine uncertainty, not preventable errors. Trader B, applying no consistent framework, will eventually encounter the full distribution of outcomes that their behavior produces — including the large losses that come from oversizing into the wrong impulse at the wrong moment.

After 500 decisions, the two scoreboards will look very different. More importantly, Trader A can diagnose and improve their process because it is explicit. Trader B cannot improve what they never defined.

The question to sit with is not "who won the first trade?" It is: which decision pattern do you want compounding across your next 500?

Common Mistakes When Trying to Apply This

Rewriting the pre-decision reasoning after the result is known. The analysis must be recorded before the result — not reconstructed from memory afterward. Memory is not neutral; it bends toward what actually happened.
Grading only the losers. Process review must be applied to winning decisions too. A reckless decision that won is not evidence of a good process. It is the most dangerous outcome, because it reinforces the wrong behavior most powerfully.
Treating process scores as permanent verdicts. A low process score on one decision is diagnostic information, not a judgment of your identity as a trader. The purpose of grading is calibration, not punishment.
Reviewing too small a sample. Drawing conclusions from three or five decisions introduces more noise than signal. The process axis requires patience. Stabilizing a skill means accumulating dozens of graded decisions, not a week's worth.
Defining "good process" too loosely. If your criteria for a good decision are vague enough to be satisfied by almost anything, the grading becomes meaningless. Good process criteria are specific enough to fail.

Abu Simulator Drill: Score Before You See

Open a Speed Run in Abu Terminal. Before you advance past each decision point, pause and do the following: in a notes field or on paper, write one sentence describing why you are making the choice you are about to make, and rate your confidence in the reasoning — not in the outcome — on a scale of one to three. One means you are guessing. Two means you have a reason but it is incomplete. Three means your reasoning is specific and you can articulate what would prove it wrong.

After the Speed Run ends and the hindsight screen is visible, go back through your notes. For each decision, compare your process score to the outcome the simulator showed. Look for the mismatches: decisions that scored one or two on process but happened to produce a favorable result, and decisions that scored three on process but resolved unfavorably. Those mismatches are the data. They tell you where you are being carried by luck and where you are being penalized by noise despite making sound choices.

Run the same Speed Run scenario a second time. This time, focus only on pushing every decision to a process score of three — regardless of what the outcome turns out to be. Notice whether the second run feels different in terms of preparation and clarity, even when the results are the same.

Reflection Prompt

After your next Speed Run or replay session, write a short response to this question: Identify one decision in this session that scored high on process and still resolved unfavorably. What does that result tell you — and what does it not tell you — about the quality of your reasoning?

The answer to that question, taken seriously, is where the discipline starts to stabilize.

Quick Check: Three Questions

A trader skips their preparation routine, acts impulsively, and the trade works out. Should they treat this as evidence that preparation is unnecessary? Why or why not?
What is the difference between outcome bias and simply learning from results? At what sample size does a losing result start to carry meaningful information about process quality?
If you can only track one metric beyond raw P/L, what would a useful process metric look like, and how would you know if it was working?

Process vs Outcome: Judging Decisions, Not Results