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.
Glossary
Minimum Detectable Effect

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.
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.
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.
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 ).
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.
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.
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.
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.
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.
MDE vs. Related Statistical Concepts
How Minimum Detectable Effect compares to other core statistical concepts used in power analysis and experimental design
| Concept | Definition | Primary Use | Relationship 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) |
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.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the statistical and methodological concepts that interact directly with the Minimum Detectable Effect to design robust, efficient A/B tests.
Statistical Power
The probability that an experiment will correctly reject a false null hypothesis. It is the complement of the Type II Error rate (β), calculated as 1 - β. An industry standard is 80% power, meaning there is a 20% chance of missing a true effect. Power is a direct function of the Minimum Detectable Effect, sample size, and variance. Increasing the MDE for a fixed sample size increases power, but risks missing smaller, practically significant improvements.
Power Analysis
A pre-experiment calculation that determines the required sample size to detect a specified Minimum Detectable Effect with a given statistical power and significance level (α). Key inputs include:
- Desired Power (1-β): Typically 80%.
- Significance Level (α): Typically 5%.
- Baseline Conversion Rate: The current metric's average.
- MDE: The smallest lift you care about. Without this analysis, experiments often end prematurely, leading to underpowered, inconclusive results.
Effect Size
A standardized, scale-free measure of the magnitude of a phenomenon. Unlike the raw Minimum Detectable Effect, which is often expressed in absolute percentage points (e.g., a 2% lift), Cohen's d or Glass's Δ provide a universal measure of practical significance. This allows for comparison across different metrics. A small MDE in raw terms might correspond to a trivial effect size, questioning the business value of detecting it.
Type II Error (β)
A false negative error where the experiment fails to detect a true effect, retaining the null hypothesis incorrectly. The probability of this error is denoted by β. The Minimum Detectable Effect is intrinsically linked to β; setting a very small MDE without a proportional increase in sample size will inflate β, making it highly likely you will miss the very effect you are trying to detect. Balancing MDE and β is the core trade-off in experimental design.
Sample Ratio Mismatch (SRM)
A critical validity check, not a statistical parameter, but a failure that invalidates MDE calculations. SRM occurs when the observed traffic split deviates significantly from the intended randomization ratio (e.g., 50/50). If the sample size is corrupted by a bug in the randomization pipeline, the pre-calculated Minimum Detectable Effect is no longer valid, and the test's power is compromised. It is the first guardrail metric checked before analyzing results.
Bonferroni Correction
A conservative adjustment to the significance level (α) when testing multiple metrics or variants. If you test 20 metrics, the probability of a false positive increases. The Bonferroni correction divides α by the number of tests (e.g., 0.05 / 20 = 0.0025). This directly impacts the Minimum Detectable Effect, as a stricter α requires a much larger sample size to maintain the same power, effectively increasing the MDE for a fixed traffic volume.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us