Inferensys

Glossary

Minimum Detectable Effect

The smallest statistically significant improvement or degradation that an experiment is designed to reliably detect, a crucial input for power analysis that determines the required sample size and duration.
Elegant overhead shot of a polished wooden communal table in a sun-drenched WeWork lounge, laptops and tablets displaying AI workflow dashboards, plants and pendant lights in background.
EXPERIMENTAL DESIGN

What is Minimum Detectable Effect?

The Minimum Detectable Effect (MDE) is the smallest statistically significant improvement or degradation that an experiment is designed to reliably detect, serving as the critical input for power analysis that determines the required sample size and test duration.

The Minimum Detectable Effect (MDE) is the smallest true effect size—whether a lift in conversion rate or a drop in latency—that an A/B test is statistically powered to identify with a specified confidence level. It represents the sensitivity threshold of the experiment; any real impact smaller than the MDE will likely go undetected, resulting in a Type II error (false negative). The MDE is inversely related to the required sample size: detecting a tiny 0.1% lift demands a massive user base, while a larger 5% MDE requires significantly fewer observations.

Setting the MDE is a business decision balancing opportunity cost against statistical rigor. A very small MDE requires prolonged experiments that delay shipping features, while a large MDE risks missing incremental but cumulatively valuable improvements. In practice, the MDE is calculated using the formula: MDE = (Z_α/2 + Z_β) * σ / √n, where Z_α/2 is the critical value for the significance level, Z_β corresponds to statistical power, σ is the metric's standard deviation, and n is the sample size. This calculation directly informs the power analysis that governs experimentation timelines.

EXPERIMENTAL DESIGN

Core Characteristics of MDE

The Minimum Detectable Effect (MDE) is the foundational parameter that bridges business impact with statistical rigor. It defines the smallest metric improvement worth detecting, directly dictating the cost and duration of an experiment.

01

The Inverse Square Law of Sample Size

The relationship between MDE and sample size is governed by an inverse square law. Halving the MDE (e.g., from 2% to 1%) does not double the required sample size—it quadruples it.

  • Practical Impact: Detecting a 0.5% lift requires 16x the traffic of a 2% lift.
  • Business Constraint: This non-linear cost forces a hard trade-off between experimental sensitivity and traffic availability.
  • Formula Context: The required sample size ( n ) is proportional to ( 1 / \text{MDE}^2 ).
4x
Sample Size Increase for 1/2 MDE
02

MDE vs. Statistical Significance

MDE is often conflated with the significance level ((\alpha)), but they control distinct error sources. Statistical significance guards against false positives (Type I error), while MDE is calibrated against false negatives (Type II error).

  • (\alpha) (Significance): Probability of detecting an effect when none exists. Typically set to 5%.
  • (\beta) (Power): Probability of correctly detecting a true effect of size MDE. Typically set to 80% or 90%.
  • Key Distinction: You can have a highly significant result (low p-value) for an effect smaller than the MDE, but the experiment was not powered to reliably detect it.
03

Variance Sensitivity

MDE is not an absolute number; it scales directly with the baseline variance of the target metric. Metrics with high natural volatility require a larger MDE for the same sample size.

  • Low Variance Metrics: Click-through rate (CTR) on a stable, high-traffic widget allows for a very small MDE (e.g., 0.1%).
  • High Variance Metrics: Average order value (AOV) or revenue per user, which have heavy-tailed distributions, demand a larger MDE (e.g., 2-5%) to avoid underpowered tests.
  • Variance Reduction: Techniques like CUPED (Controlled-experiment Using Pre-Experiment Data) reduce variance, effectively lowering the achievable MDE without increasing traffic.
04

Practical Significance Calibration

The MDE must be larger than the minimum business impact required to justify the engineering cost of shipping a model. An MDE set purely by statistical convenience risks detecting statistically significant but operationally irrelevant changes.

  • Cost-Benefit Analysis: If a new personalization model requires 6 months of engineering effort, the MDE should reflect the revenue lift needed to generate a positive ROI within a fiscal year.
  • Baseline Stability: The MDE must exceed the natural week-over-week fluctuation of the metric to avoid chasing noise.
  • Guardrail Alignment: The MDE for a North Star Metric (e.g., revenue) should be considered alongside guardrail metrics (e.g., latency) to ensure the detected improvement doesn't mask a degradation elsewhere.
05

Duration and Time-to-Detect

MDE directly determines the minimum runtime of an experiment. A smaller MDE requires capturing more user-week cycles to account for day-of-week effects and novelty effects.

  • Novelty Effect: Users may initially engage with a new recommendation module regardless of its true quality. The experiment must run long enough for this effect to decay, which requires a sample size sufficient to detect the post-novelty MDE.
  • Holdout Validation: Long-term holdout groups are essential for validating that the MDE observed in a 2-week experiment holds over a 6-month period without degrading due to user learning or ecosystem changes.
06

MDE in Sequential Testing

Traditional fixed-horizon MDE calculations assume a single evaluation at the end of the test. Sequential analysis and always-valid p-values allow for continuous monitoring, but they alter the effective MDE.

  • Alpha Spending: Continuous monitoring requires adjusting significance thresholds to control the false positive rate, which slightly inflates the required sample size for a given MDE.
  • Stopping Rules: If an experiment is stopped the moment the MDE is crossed, the effect size estimate is likely upwardly biased due to random variation. A post-selection inference correction is required.
EXPERIMENTAL DESIGN PARAMETERS

MDE vs. Related Statistical Concepts

How Minimum Detectable Effect compares to other core statistical concepts used in power analysis and experimental design

ConceptDefinitionPrimary UseRelationship to MDE

Effect Size

Standardized measure of the magnitude of a difference between groups

Interpreting practical significance of results

MDE is the minimum effect size an experiment is designed to detect

Statistical Power

Probability of correctly rejecting a false null hypothesis

Determining experiment sensitivity

MDE is derived from desired power level; higher power enables smaller MDE

Significance Level (α)

Probability of Type I error; threshold for rejecting null hypothesis

Controlling false positive rate

MDE increases as α becomes more stringent (e.g., 0.01 vs 0.05)

Sample Size

Number of experimental units required per variant

Planning experiment duration and traffic allocation

MDE and sample size are inversely related; smaller MDE requires larger sample

Confidence Interval

Range likely containing the true population parameter

Reporting uncertainty around observed lift

If CI excludes MDE threshold, the result is practically significant

P-Value

Probability of observing data at least as extreme given null is true

Statistical significance testing

P-value alone does not indicate effect magnitude; MDE ensures practical relevance

Type II Error (β)

Probability of failing to detect a true effect

Assessing false negative risk

MDE is the smallest effect detectable given acceptable β (typically 0.2)

MINIMUM DETECTABLE EFFECT

Frequently Asked Questions

Understanding the Minimum Detectable Effect (MDE) is critical for designing efficient online controlled experiments. These answers address the most common statistical and practical questions regarding the calculation and application of the MDE in A/B testing infrastructure.

The Minimum Detectable Effect (MDE) is the smallest statistically significant improvement or degradation that an experiment is designed to reliably detect, serving as a crucial input for power analysis. It is not a property of the data but a design parameter chosen by the experimenter based on business impact. The MDE is calculated inversely from the sample size formula: it is a function of the desired statistical power (typically 80%), the significance level (alpha, typically 0.05), and the baseline variance of the metric. A smaller MDE requires a larger sample size, as the test needs more data to distinguish a tiny signal from random noise. For continuous metrics like average order value, the formula is MDE = (Z_alpha/2 + Z_beta) * sigma * sqrt(2/n), where sigma is the standard deviation and n is the sample size per variant.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.