Social media celebrates win rate. Screenshots of “90% accuracy” hide average loss size. Professional review centers on expectancy — the expected R per trade — because that is what compounds over hundreds of trades. This guide explains win rate vs expectancy, when each metric matters, and how to log both without manual math.
Win rate alone misleads
Win rate = winning trades ÷ total trades (often counting anything above 0R as a win). It ignores how much you make when right vs lose when wrong. A scalper with 80% wins and −1R average loss on the 20% losers can have negative expectancy if winners are only +0.2R.
Another example: 40% win rate with +2.5R average win and −1R average loss → (0.4 × 2.5) + (0.6 × −1) = +1.0 − 0.6 = +0.4R expectancy. Lower win rate, stronger edge. The market pays payoff structure, not comfort.
Expectancy connects win rate and payoff
Expectancy in R combines both dimensions. High win rate with small wins needs tight loss control — any slippage on stops or occasional oversizing destroys the edge. Low win rate systems (trend following, breakouts) need larger average wins — often +2R to +4R — to stay positive with 35–45% wins.
Think of win rate as “how often am I right?” and average win/loss R as “how much does being right or wrong matter?” Expectancy is the product of those stories told honestly across your full sample.
Which metric to watch when
- Win rate → entry quality: are you taking valid setups or forcing trades?
- Average win R vs average loss R → exit discipline and target management
- Expectancy → overall system health and sizing decisions
- Profit factor → gross win R ÷ gross loss R (secondary sanity check)
- Max consecutive losses → psychological and capital tolerance for your style
Style profiles: scalper vs swing
Scalpers often run 55–70% win rate with smaller average wins — sometimes +0.3R to +0.8R — and must keep losses near −1R. Swing trend traders may sit at 35–45% wins but need occasional +3R to +5R runners. Neither profile is “better”; each has a different emotional and capital curve. Judge your style by expectancy and drawdown, not by copying someone else’s win rate.
Journal fields that capture both
Log result in R on every trade. Your journal can then compute win rate and expectancy without manual formulas. Tag setups separately — win rate on a breakout tag and win rate on a fade tag tell different stories. A fade tag with 72% wins but −0.1R expectancy should be cut even if it “feels” good.
Include breakeven trades. Treating scratches as non-trades inflates win rate and distorts expectancy. Consistency in classification matters more than the exact rule for what counts as a “win.”
Psychology trap
High win-rate strategies often feel better but may cap upside through early exits. Lower win-rate systems feel rough — long streaks of −1R — but can compound if you respect stops and let winners run. Pick the profile that matches your temperament, then judge it by expectancy over 50+ trades, not by how the last week felt.
Avoid optimizing for win rate after losses by tightening targets. That raises win rate while shrinking average win R — expectancy often gets worse even as green days increase.
Quick reference table
Memorize the relationship: higher win rate helps only if average win R stays large enough relative to average loss R. At −1R average loss, you need win rate × avg win R to exceed (1 − win rate). Log both dimensions every trade and let expectancy settle the argument.
How Traderizz helps
Traderizz calculates win rate and expectancy from your logged RR automatically on the overview dashboard. Filter by tag to compare setup profiles side by side — see which patterns have high win rate but weak expectancy, and which tolerate lower win rate with strong average R.
Use weekly review with the trader diary to connect emotional sessions to metric shifts. When win rate jumps but expectancy flatlines, you usually have an exit-size problem, not an entry breakthrough. The numbers make that visible early.
Export nothing to spreadsheets unless you need custom research — keeping win rate and expectancy in one system reduces version drift and makes weekly review a single click instead of a merge job.