A trade makes money, so it feels good. Another loses, so it feels bad. Both feelings are almost irrelevant to whether you are trading well, because outcomes are noisy: the same decision can win or lose depending on what the market happened to do.
The review skill is looking past the outcome at the process. Was the entry rule followed? Was the stop where the plan said? Was the size solved from the risk budget? Those are the questions a review can actually answer.
Review the process, not the profit. A profitable trade can be a bad decision if it broke the rules, and a losing trade can be a good one if it followed them. Outcomes are noisy; process is what you control and what you can fix. A review that judges trades by P&L cannot tell process problems from ordinary variance.
Why the Outcome Is a Noisy Signal
A single trade's result depends on the market, not just on your decision. The same rule can produce a winner this time and a loser next time, because the price path was different.
That is why a review that judges each trade by profit or loss cannot separate skill from luck, and cannot tell a process problem from a rough stretch.
| Process | Outcome | Review verdict |
|---|---|---|
| Followed the plan | Profit | Good process, good result — nothing to fix |
| Followed the plan | Loss | Good process, expected loss — the plan worked |
| Broke the rules | Profit | Bad process, lucky result — still a violation |
| Broke the rules | Loss | Bad process, expected loss — fix the deviation |
What 'Process' Actually Means in Review
Process is the set of decisions that were supposed to happen: the entry rule that fired, the invalidation that set the stop, the size solved from the risk budget, and the exit rule that closed the trade.
Reviewing process means asking whether each of those matched the written plan, not whether the trade made money. A deviation that repeats across trades is fixable; a rough stretch where everything matched is usually variance.
The Good Loss: Why Following the Plan Is the Win
A loss taken at the planned stop, with the size the plan called for, is a successful execution. It did what the rule required, and it cost exactly what the risk budget approved.
The point of the review is to confirm that. If a losing stretch shows every trade matched the plan, the finding is that the process held — which tells you where a fix would not help.
| Trade | Process | Stop distance × size = actual risk | Actual outcome | Review verdict |
|---|---|---|---|---|
| Trade A (planned) | Entered at $50.00, stop set at $49.00 as planned, size solved from the risk budget: $1,000 ÷ $1.00 = 1,000 shares | $1.00 × 1,000 shares = $1,000 (1.0% of account, matches budget) | Stopped out for a $1,000 loss (-1.0%) | A correctly executed loss — the plan was followed |
| Trade B (unplanned) | Entered at $50.00, stop moved on impulse to $47.00, size doubled to 2,000 shares without re-solving from the risk budget | $3.00 × 2,000 shares = $6,000 (6.0% of account, 6x over budget) | Price bounced; closed at $51.00 for a $2,000 profit (+2.0%) | A rule violation that paid off — exposure far exceeded budget |
Trade A lost $1,000, but it did exactly what the plan required — the stop distance and size matched the risk budget precisely. That is a successful execution with nothing to fix. Trade B made $2,000, but the stop was widened on impulse and the size was doubled, pushing actual exposure to $6,000 — six times the budget. If price had continued down to $47.00 instead of bouncing, that trade would have lost $6,000, not made $2,000. What decides whether it was a good trade is the process at the moment the order was placed, not which way price happened to move afterward.
A review should ask what the decision looked like before the outcome was known. That is the only question the trader controlled and the only one a review can meaningfully answer.
How to Run a Process Review
For each trade, score the process, not the P&L: was the entry rule followed, was the stop where the plan said, was the size from the risk budget, did the exit match the rule?
Then look for patterns across the trades. One deviation is an event; the same deviation repeated is a process problem. Only the pattern justifies a change.
Frequently Asked Questions
Should I ignore profit entirely in review?
No. Profit is part of the record, but the review question is whether the process was followed. Outcome alone cannot answer that.
Can a profitable trade still be a violation?
Yes. If it broke a rule and happened to win, the process still failed and the violation should be logged.
How many trades before I judge the process?
Enough to see a pattern. A single trade never proves a process problem or a process success.
