Software Engineering Glossary

Minimum Detectable Effect

Also known as: MDE Minimum detectable lift

The minimum detectable effect is the smallest lift an A/B test is designed to find. You pick it before the test, along with a confidence level (often 95%) and statistical power (often 80%). A smaller effect needs many more users. If your traffic cannot reach that sample in a reasonable time, the test cannot see the lift you care about, and a ‘no difference’ result is mostly the sample being too small.

Key Takeaways

  • It is the smallest change worth detecting, chosen up front, not the lift you hope to see.
  • A 10% relative lift on a 10% conversion rate is a move from 10% to 11%, and it needs on the order of 15,000 users per variant.
  • The same relative lift on a rarer event, such as a 2% baseline, can need well over 80,000 users per variant.
  • Effects smaller than the minimum detectable effect mostly stay invisible. That is part of the design.

How It Works

  1. Estimate the baseline rate of the primary metric from recent traffic.
  2. Choose the smallest relative or absolute lift that would change what you ship.
  3. Plug the baseline, that lift, 95% confidence, and 80% power into a sample size calculation.
  4. If you cannot collect that many users in a week or two, test a bigger change or a more frequent metric.

Where It Is Used

  • Sample size calculators such as Evan Miller’s take a baseline rate and a minimum detectable effect and return users per variant.
  • Checkout and signup tests on low-traffic products often cannot detect small conversion lifts, so teams test bolder changes.
  • Experiment platforms use it to estimate how long a test must run before it can give a trustworthy answer.

Related glossary terms