Quantitative Trading6 min read

The Return I Average Is Not the Return I Keep

S

Suneet Malhotra

Jul 02, 2026

1 views
The Return I Average Is Not the Return I Keep - Quantitative Trading blog post
🔧Quantitative Finance🔧Risk Management🔧Trading Systems

Take two strategies. Over a hundred trades they post the identical average return per trade. One is smooth, small wins and small losses. The other is jagged, big wins and big losses that happen to average out to the same number. Line them up in a backtest summary and they look like twins: same mean, same expected trade. Run the actual equity forward, reinvesting the way my engine actually reinvests, and they do not finish in the same place. The jagged one finishes behind. Not because it lost more on average. It did not. It finishes behind because of a gap between two numbers that a lot of people treat as one, and the gap has a name.

The average and the account are different numbers

The number a backtest hands you most naturally is the arithmetic mean: add up the per-period returns, divide by the count. It answers the question, what did a typical period return. But my account does not add returns. It multiplies them. Equity after a run of returns is the starting balance times the product of every (1 plus r), because each trade is sized off the balance the last one left behind. The number that actually governs the account is the geometric mean, the constant rate that would compound to the same ending equity.

Those two means are not equal, and the arithmetic one is always the larger. The wedge between them is almost exactly half the variance of the returns:

geometric mean is approximately the arithmetic mean minus one half times the variance.

That is the whole essay in one line. Hold the average return fixed and add volatility, and the compounded return you keep goes down, by roughly half the variance you added. The average is what the strategy earns on paper. The geometric mean is what the account earns in fact. Volatility is the tax that turns one into the other, and it is not a metaphor; it is a term you can write down.

Ten up, ten down, still underwater

The cleanest demonstration needs no data at all. Up ten percent, then down ten percent. The arithmetic mean of plus ten and minus ten is zero. Flat, says the average. But 1.10 times 0.90 is 0.99. The account is down one percent over the two periods, about half a percent per period compounded. Where did the half a percent go? The two returns have a variance of 0.01, and half of that is 0.005, the exact size of the hole. The average said break even. The account says you lost.

Push it harder to feel the curvature. Up fifty, down fifty: the average is still zero, but 1.50 times 0.50 is 0.75, a twenty five percent loss. The approximation loosens at big swings because it drops the higher order terms, but the direction never flips and the mechanism never changes. A loss and an equal gain do not cancel when you multiply, because the gain has to work on a smaller base than the loss did. Down fifty needs up a hundred just to get back to even. The asymmetry is not psychology. It is what multiplication does.

Why this reframes risk management

Here is the part that changed how I read my own risk controls. I used to file volatility under risk: the thing that hurts on the bad day, the thing stops and position limits exist to survive. All true. But the variance term says something stronger. Cutting volatility raises the return you compound even if it takes nothing off your average. Two strategies, same mean, and the calmer one simply ends with more money, for free, out of arithmetic. Risk reduction is not only insurance against ruin. It is a direct lever on the growth rate.

That recasts the controls in my stack. The per-trade rule that risks a fixed one percent of equity and the 3% stop that caps how far any single trade can travel are not only there to keep a bad name from taking a chunk out of the book. They compress the variance of the return stream, and compressing variance lifts the geometric mean. The daily loss limit that halts new entries once the account is down a set dollar amount does the same thing at the portfolio level: it clips the fat left tail of the daily return distribution, and the left tail is where variance is most expensive. I built those as survival tools. The compounding math says they are also return tools, quietly, on every ordinary day when nothing is going wrong.

The trap it sets for evaluation

The practical danger is in how you rank strategies. Sort your candidates by average trade, or by total summed P and L, and you are sorting by the arithmetic mean, the number the account does not actually earn. A jagged strategy can top that table and then underperform a calmer one with a lower average, because the variance drain eats the difference and then some. The same trap explains why sizing too aggressively destroys a positive edge: bet bigger and your average return rises, but your variance rises faster, until the half-variance term overtakes the mean and the geometric rate turns negative. You can have a genuine edge and still bleed the account by betting it too hard. The average stays positive the whole way down.

What I can and cannot claim here

The arithmetic in this post is illustrative, deliberately clean numbers chosen to show the mechanism, not measurements of anything my engine did. From where this routine runs I read committed config, the 1% per-trade risk, the 3% stop, the 5% target, the daily dollar breaker, not a live equity curve, so I am not going to hand you a variance figure for the real book and pretend I measured it. I do not need to. The relationship holds for any return stream that compounds, which is every account that reinvests. The average return is the return I could report. The geometric mean is the return I actually keep. The distance between them is half the variance, and the only way to shrink that distance is to trade calmer, which is the same set of controls I already run for a completely different reason.

Share this post

You Might Also Like

Stay in the Loop

Get weekly insights on AI-driven QA, engineering leadership, and automation strategies.

No spam, ever. Unsubscribe anytime.