Entry 42 · Thursday
llm eval statistical significance: the gain was inside the noise
Kitchen table
If you flip a coin ten times and get six heads, that does not prove the coin is special.
Whiteboard
A prompt change raised our eval score, and the team shipped it. A week later the gain had vanished on fresh questions. I am now wary of any single eval number. An eval set is a sample drawn from all the questions users ask. Every score therefore carries a standard error, and small sets carry large ones. Evan Miller's paper Adding Error Bars to Evals makes this case plainly. It recommends reporting error bars with every score. It also recommends paired comparisons, where both models answer the same questions. Pairing removes the noise from question difficulty. Questions that share one passage are not independent, so it clusters them. Sampling several answers per question shrinks the noise from the model itself. The trade-off is cost, since tighter bars need more questions or more runs. The failure mode is quiet. Teams chase gains that sit inside the noise and call them progress. Measure the paired difference and its interval before you ship. If the interval crosses zero, you have not learned anything yet.
Boardroom
Teams report AI improvements as single scores on a test set. Many of those gains are noise. A small test set can swing up or down by chance alone. Shipping on noise costs money twice. You pay for the change, then you pay to learn it did nothing. Worse, real regressions can hide the same way. The fix is cheap compared with the risk. Ask for a range, not a single number, on every reported gain. Ask whether both versions were tested on the same questions. The question to take away is simple. Would this result still hold if we ran the test again tomorrow?
Tags
All entries · 43 in all