Module 4E
Aggregated journal review: finding your behavioural pattern
Leads into 4F, the psychology drills, which work on whatever this review finds.
This curriculum's own.
You cannot run this yet, and that is expected
This module needs twenty to thirty logged sessions before it produces anything. At one trade a day that is somewhere around six to ten weeks of work, and there is no way to shorten it.
It is taught here and used later, which is unusual and deliberate. You need to know what the review will ask for, because that determines what you record between now and then. A reader who meets these four questions after eight weeks of journalling will discover they logged the wrong things.
2H already gave you the cadence, weekly and monthly. This module is the method.
Why this exists
The journal produces raw data. This is what turns it into something.
A trader who journals every session for two months has a serious dataset about their own behaviour, and most never look at it systematically. They review individual trades in isolation, feel good or bad about specific sessions, and move on.
The behavioural pattern, which is the thing that actually determines long-term outcomes, is invisible at the session level. It only appears in aggregate. This module is the structured process for stepping back from the individual trade and finding the pattern across twenty, fifty or a hundred decisions.
It is where journalling stops being documentation and becomes intelligence.
The four questions, always in this order
One: when do I execute cleanly, and when do I not?
A behavioural audit, not a performance one. Pull your last twenty to thirty sessions and mark each one clean or compromised, using 2H's binary. Clean means the full process was followed. Compromised means any deviation at any point, regardless of whether the trade made money.
Then look for pattern in the compromised ones:
- What day of the week?
- What time did the deviation occur, before the window, at entry, or during the trade?
- Was there a news event, a prior win, or a prior loss immediately before?
- Was the write-up skipped?
The goal is to find the conditions that produce breakdown, not the trades where it happened.
That distinction is the entire question. A list of bad trades is a list of regrets. A list of conditions is a list of things you can change, and the conditions are almost always more boring and more actionable than the trades.
Two: what is the win rate on clean executions only?
Separate the two groups and calculate each independently.
Almost universally, clean executions outperform compromised ones by a meaningful margin. That is the most useful single fact this review can produce, and it says something specific: your edge is real when you execute it. The execution is the problem, not the model.
Which matters because the instinct when results disappoint is to change the model. Go looking for a better setup, a new filter, another course. This calculation tells you whether that instinct is correct, and usually it is not.
If clean executions are also losing at a high rate, that is different and more important. Either the model does not suit the current regime, or the setup criteria need tightening. Both are real findings. Neither is a discipline problem, and treating it as one will make it worse.
Three: what pattern appears in the losses specifically?
Take only the losing trades. For each, find the earliest point of deviation, not the moment it went wrong.
Was the setup fully confirmed before entry or was entry anticipatory? Was the stop predefined and honoured? The target? Was a second trade taken? Was the write-up complete?
Most people find their losses cluster around one or two failure points. The common findings are consistent enough to be worth naming in advance:
- Losses cluster after winning sessions, which is overconfidence lowering the standard
- Losses cluster on days the write-up was skipped or abbreviated
- Losses cluster in sessions where a second trade was taken
- Losses cluster on particular days of the week, which usually reflects something outside trading entirely
That last one is worth taking seriously rather than dismissing. If your worst sessions are always Mondays, the problem is probably not the market on Mondays.
Four: what does my own language tell me?
The most overlooked layer, and the one that works best alone, because it needs no mentor and no outcome data.
Read the last few weeks of pre-market halves without looking at the outcomes. Cover them if you have to. Then pay attention to how you wrote:
- Hedging language, I think maybe, it could, not totally sure but, tends to precede compromised execution
- Absolute language, this is definitely going to, the setup is perfect, tends to precede overconfidence errors
- Clean conditional language, if price sweeps this level and the flow confirms I enter, if not I sit out, tends to precede clean execution
The write-up is a direct window into the state you entered the session in. Read in aggregate, it tells you whether that state is being managed or ignored, and it tells you before the outcomes do.
This is the closest thing in the curriculum to an objective look at yourself. You are reading your own words back with the results hidden, which removes the one thing that most distorts self-assessment: knowing how it turned out.
The behavioural pattern log
A separate running document, updated monthly. Not a list of trades. A list of your own tendencies.
| Pattern | When it appears | What it produces | Status |
|---|---|---|---|
| Skipping the write-up | High-confidence mornings, rushed schedule | Unconfirmed entries, larger losses | Active, monitoring |
| Early exit | After a few points of open profit | Reduced reward-to-risk, the arithmetic broken | Improving, three clean holds last month |
| Second trade after a loss | Immediately after a stop | Revenge trade, second loss | Resolved, none in six weeks |
This is what makes improvement cumulative rather than repetitive. Without it, every month's review rediscovers the same pattern from scratch and you spend a year learning the same thing four times.
It also gives you something almost nobody has: a status column. Being able to write "resolved, none in six weeks" against a pattern that used to cost you money is a different kind of evidence from a good month, and it survives a bad one.
What this review is not
Not a P&L review. Profitability is an outcome of process adherence over a sufficient sample, so reviewing it in isolation tells you nothing about what to change. A profitable week from compromised execution teaches worse lessons than an unprofitable week from clean execution, because it teaches them more persuasively.
Not a trade critique. The individual trade is not the unit of analysis here. The pattern across trades is. Obsessing over one losing trade is how people avoid looking at the pattern connecting them, and it feels like rigour the entire time.
Self-check
Grade yourself honestly
1. Why does the review sort by clean and compromised rather than by winners and losers?
A correct answer says the outcome is not the thing you control and it is heavily influenced by variance, so sorting by it groups unrelated sessions together. Sorting by process groups sessions by the one variable you can change, which is why the comparison in question two is possible at all.
2. Your clean executions and your compromised ones show roughly the same results. What does that mean?
A correct answer notices this is not the usual finding and treats it as a signal about the model rather than the discipline. Either the setup criteria need tightening or the regime has changed. The wrong response is to try harder at execution, because the data just told you execution is not the variable.
3. What is the value of reading your write-ups with the outcomes hidden?
A correct answer names hindsight. Knowing how it turned out changes how you read what you wrote, every time, and you cannot switch that off by intending to. Covering the outcomes is the only reliable way to read your own state rather than your own results.
4. Your losses cluster on one particular day of the week. What is the likely explanation?
A correct answer says the cause is probably not the market. Something in your week is landing on that day: schedule, sleep, a recurring commitment, whatever precedes the session. This is the finding people dismiss most often and it is one of the easiest to actually fix.
If question 2 was the one you had to think about
That is the right question to find hard, because it is the one that decides whether you keep going or change direction. Almost every trader assumes their problem is discipline, because that framing is flattering in a strange way: it implies the edge is fine and only effort is missing. This review is the only thing in the curriculum that can tell you otherwise, and it can only tell you once there is enough data to look at.
One rep before you continue
Write the first line of your pattern log
You almost certainly do not have thirty sessions yet, so do not attempt the full review. Do the smallest version that works.
Take whatever sessions you do have, even five. Sort them into clean and compromised using 2H's binary. Then write one row of the pattern log: the pattern, when it appears, what it produces, and its status.
That single row is the document you will keep for as long as you trade. Starting it with almost no data is the point, because the alternative is starting it in three months and discovering you have not been recording the thing it needs.
What the next module does with this
4E finds the pattern. 4F and 4G are the drills that work on it.
4F is psychological: sitting through a trade untouched, confirmed no-trade days, deliberate exposure to the states that break your execution. 4G is technical: predict-then-verify reps against replay, where the market supplies the answer key.
Both are post-graduation tools taught now for the same reason this module is, which is that you need to know they exist before you need them.
Log the module
Where did you get stuck?
Not a test, and nothing is marked. This module is the one you cannot use yet, so the useful thing to know is whether it makes sense as something to work toward. About a minute.