Minimum Detectable Effect
The smallest true effect a test is capable of reliably catching, given how much data you have and how much noise sits in that data — the honest answer to 'how good does my edge need to be before I'd even notice it?'
Prerequisites: Statistical Power and Sample Size, Effect Size and Cohen's d
Before running a test, it is worth asking the question backward: given the amount of data you're about to collect and the noise you already know is in it, what is the smallest true effect your test would even be capable of noticing? Run a test with too little data against a genuinely small edge, and the honest answer might be "you had no realistic chance of detecting this, even if it were completely real." The minimum detectable effect (MDE) is that threshold, computed in advance, and it turns "we found nothing" into a question with a real answer: was there nothing there, or was the test simply too weak to see it?
An analogy: the smallest object a telescope can resolve
Every telescope has a resolving power — the smallest angular separation between two stars it can actually distinguish, set by its aperture size and the wavelength of light. Point a small telescope at two stars closer together than its resolving power, and it will show you one blurred dot, not two, no matter how long you stare or how real the gap between them is. Asking "how much data do I need to detect an effect of size X?" and asking "given my data, what is the smallest effect X I could detect?" are the same telescope-resolving-power question asked in opposite directions.
The formula, one symbol at a time
For a two-sample comparison (say, comparing average returns under a treatment and a control), the minimum detectable effect at a chosen significance level and desired power is approximately:
In plain English: the smallest gap your test can reliably catch grows with how much noise is in the data () and shrinks as your sample size () grows, at a rate governed by the square root of . The terms are fixed constants for standard choices — at two-sided and power , and , so their sum, , is a number worth memorizing as the standard "detectability multiplier."
Watch the running average above settle inside its shrinking envelope as more draws accumulate — that envelope is a band, the exact same shape that shrinks the MDE. It narrows fast at first, then flattens, so doubling your sample size does not halve the smallest effect you can detect; it only shrinks it by a factor of .
Worked example 1: MDE for a strategy A/B comparison
You plan to compare 200 trading days under Strategy A against 200 days under Strategy B ( per group), with daily return noise in each group, at the standard , power .
With 200 days per group, the test can reliably detect a true average daily-return gap of about 0.42 percentage points or larger. If the real edge between the two strategies is smaller than that — say, a genuine but modest 0.2-point difference — this test is very unlikely to find it, regardless of how carefully it's run.
Worked example 2: what more data buys you
Quadruple the sample to per group, same noise:
Quadrupling the data halved the MDE, from 0.42% to 0.21% — exactly the relationship predicted: to detect an effect half as large, you need four times as much data, not twice. This is the concrete arithmetic behind why chasing genuinely small edges with more history has fast-diminishing returns.
The minimum detectable effect turns a vague sense of "is my sample big enough?" into a specific number, computed before you run the test: the smallest true effect your setup has a good chance of catching. A null result from a test with a large MDE relative to the effect you actually hoped to find is not evidence of "no effect" — it may simply be evidence of an underpowered test.
What this means in practice
Before backtesting a strategy or running a live A/B trading experiment, computing the MDE tells you whether the test is even worth running for the size of edge you're hoping to find. A signal expected to add a genuine but modest 0.1% of extra return, tested against a setup whose MDE is 0.4%, is being tested by an instrument that cannot resolve it — a "no significant result" outcome would be almost guaranteed regardless of whether the signal is real, and running the test at all would waste time and risk a false conclusion of "the strategy doesn't work."
A common mistake is treating a failed test (no significant result) as proof an effect doesn't exist, without ever checking what the test's MDE actually was. If the true effect is smaller than the MDE, "not significant" and "no effect" are not the same statement — the test may simply have lacked the resolving power to see an effect that is real but modest. Always report the MDE alongside a null result, the same way a telescope's resolving power is quoted alongside "no companion star detected."
Related concepts
Practice in interviews
Further reading
- Cohen, Statistical Power Analysis for the Behavioral Sciences, ch. 2
- Lehmann & Romano, Testing Statistical Hypotheses, ch. 3