What to measure first
Start with metrics you can interpret reliably. If you cannot act on a metric during your next review cycle, defer it.
| Category | Examples | Purpose |
|---|---|---|
| Outcome metrics | P&L, average gain/loss, win/loss count | Shows headline results by period or strategy. |
| Process metrics | Plan-followed rate, late-entry frequency, sizing errors | Identifies behavior patterns that drive results. |
| Context slices | By strategy, by tag, by ticker group | Separates strong setups from weak ones. |
Compare by strategy before comparing by day
Day-to-day results can be noisy. Strategy and tag segmentation usually reveals more useful signals for process changes. For example, review covered calls separately from spreads or long calls.
Weekly review questions that improve decision quality
- Which setup tags produced the cleanest plan execution this week?
- Where did risk sizing deviate from the stated plan?
- Which losses were process failures versus valid losses?
- What one rule change should be tested next week?
Important: Do not optimize your process around a single week. Use recurring reviews to see whether a pattern repeats across multiple weeks.
Build a full review loop
The strongest review loop is: track trades consistently -> apply tags and notes -> run a weekly checklist -> compare strategy and process metrics.
FAQ
Should I optimize for win rate?
Win rate alone can hide risk and sizing issues. Review it with average gain/loss, process adherence, and strategy context.
How often should I review performance?
Weekly is a practical cadence for process review. Monthly reviews can be useful for broader strategy changes.