A weekly review that ends with one change

It is possible to spend an hour reviewing trades and finish with nothing more specific than “be more patient.” A useful review ends with a decision about your process: something small enough to try and clear enough to evaluate later.

Set aside a repeatable review window. Bring your trade records, your original notes, and the plan you were working from. The goal is to compare what you intended with what you actually did.

Check the record before the story

Start by looking for missing notes, duplicate entries, or inconsistent tags. An incomplete record can make an explanation feel more convincing than it deserves.

Separate facts from interpretation. “Three entries mention an interruption” is a fact about your notes. “Interruptions caused every mistake this week” is a claim those notes may not support.

Write down uncertainty where it exists. If you changed the meaning of a setup tag halfway through the week, do not treat the two groups as interchangeable. Make a note to repair the definition before relying on that comparison.

Compare like with like

Choose one question rather than opening every possible breakdown. You might ask whether your notes are complete after a certain session, or whether a recurring departure from the plan appears in more than one setup.

Read the underlying entries alongside any summary. A total can tell you where to look, but it cannot explain what happened in a particular trade.

• Include examples that fit your first impression.
• Include examples that challenge it.
• Note changes in context that make a comparison less useful.
• Leave a question open when there is not enough evidence.

A small set of trades is a starting point for investigation, not proof that you have discovered a durable edge or a reliable cause.

Choose one process experiment

Translate your observation into something you control. Instead of “stop making rushed decisions,” you might test “write one sentence describing the planned setup before the session begins.”

Define the experiment before the next review:

1. Action: what you will do differently.
2. Record: what you will capture to see whether you did it.
3. Review point: when you will look back and decide whether the change was useful.

This is an experiment in your workflow, not a promise about trading results. Keep its evaluation connected to the behavior you are trying to change.

A review should leave you with a smaller next step, not a longer list of things to feel bad about.

Close the loop next week

Begin the next review with the experiment you chose. Did you do it? Was it practical? Did it make the record clearer? If not, identify whether the action was too vague, too burdensome, or aimed at the wrong problem.

Do not silently replace last week’s experiment with a new one. Keep a short log of what you tried and what you learned. An abandoned idea is still useful when you know why it was abandoned.

If the review keeps stalling on vague notes, simplify your capture process with a trade journal you’ll actually use. Better reviews begin with a record you can trust, including its limitations.