Experiments

Data Science

What does "statistical significance" mean for AI experiments?

Jun 6, 2026

min read

A graphic of a bar chart with an arrow pointing upward.

Running statistical significance on an AI experiment the same way you'd run it on a button color test is one of the most common ways teams end up drawing confident conclusions from noise.

The core problem is structural: traditional A/B testing assumes a fixed treatment, but AI models are probabilistic by design. Every LLM call is a sample from a distribution, not a deterministic output. That adds a second layer of variance on top of normal user behavior — and the statistical frameworks most teams use were never built to handle two noise sources at once.

This article is for engineers, PMs, and data teams who are running or planning AI experiments and want to understand why standard testing instincts break down. Whether you're testing a new prompt configuration, a different model version, or an LLM-powered feature, the same core issues apply. Here's what you'll learn:

Why AI outputs are noisier than traditional feature tests — and what that means for sample sizes
How to choose metrics that actually reflect user outcomes, not just model quality
The validity traps that silently corrupt results: p-hacking, peeking, and multiple metrics
Why statistical significance alone isn't enough, and how to define practical significance before your experiment runs

The article moves in order from the statistical foundations to the practical decisions you make when designing and interpreting AI experiments. Each section builds on the last, so if you're new to significance testing in this context, reading straight through will give you the clearest picture.

What statistical significance actually means (and why AI experiments make it harder)

If you've run A/B tests before, you've encountered the phrase "statistically significant" — probably as the threshold between "we can ship this" and "we need more data." But the concept is frequently misapplied even in traditional testing environments, and AI experiments introduce a structural complication that makes misapplication far more costly.

Before getting into what makes AI experiments different, it's worth being precise about what statistical significance actually means.

The core definition: p-values, null hypotheses, and the 0.05 threshold

Statistical significance is a measure used in hypothesis testing to determine whether observed results are unlikely to have occurred due to chance alone. The mechanism is the p-value: a number that answers a specific question — if there were truly no difference between your control and treatment, how likely would it be to see results this large just by chance? A p-value of 0.05 means there's only a 5% chance you'd see this result if nothing real were happening.

When the p-value falls below a predetermined threshold — conventionally 0.05 — you reject the null hypothesis, which is simply the assumption that there is no real effect between your control and treatment groups. That threshold acts as the gatekeeper between "this might be noise" and "this is probably real."

Two things are worth internalizing here. First, the 0.05 threshold is a convention, not a law of nature. It's a reasonable default that the field has coalesced around, but it carries no special mathematical authority.

Second — and this matters enormously for AI experiments — statistical significance only tells you whether an effect is real. It says nothing about whether that effect matters. As one practitioner put it on Hacker News: "Significance testing only tells you the probability that the measured difference is a 'good measurement'... Whether the measured difference is significant in the sense of 'meaningful' is a value judgement." A result can be statistically significant and practically irrelevant. Keeping those two questions separate is essential.

What traditional A/B tests assume about determinism

Standard A/B testing was designed around a specific noise structure. Once a user is assigned to a variation, their experience is fixed. A button is blue or it isn't. A headline reads one string or another. The treatment is deterministic — it doesn't change between exposures, across users, or over time.

This means the only meaningful source of variance in a traditional experiment is user behavior. People click or they don't. They convert or they don't. That behavioral variance is real and substantial, but it's bounded and well-understood.

The statistical framework — power analysis, minimum detectable effects, sample size calculations — was built to handle exactly this structure: one noise source, controlled through randomization and sufficient sample size.

How AI outputs break the determinism assumption

AI models, particularly large language models, are probabilistic by design. Temperature settings, sampling parameters, and model versioning mean that the same prompt from the same user in the same context can produce meaningfully different outputs across calls. The treatment is not fixed. It varies.

This introduces a second, independent source of variance that traditional A/B testing frameworks were never designed to accommodate. In a standard experiment, variance comes from users. In an AI experiment, variance comes from users and from the model's outputs. These two sources compound.

When you're measuring whether a new LLM configuration improves task completion rates, you're trying to detect a signal through two layers of noise simultaneously — the natural variation in how different users behave, and the natural variation in what the model produces for any given user.

This isn't a minor technical footnote. It's a structural difference that changes the statistical bar before you've written a single line of experiment configuration.

What compounded variance means for sample sizes

Variance and sample size are directly linked in hypothesis testing. When variance increases, you need more data to detect the same effect at the same confidence level. Another way to say the same thing: if your sample size is fixed, higher variance means only larger effects will show up as significant — smaller real improvements become invisible to the test.

That's what minimum detectable effect (MDE) means in practice: the smallest true difference between control and treatment that your experiment can reliably surface given your significance threshold and statistical power.

Teams that size AI experiments using the same calculators they use for button color tests will systematically underpower their studies. The calculator assumes one noise source. The experiment has two. The result is experiments that run to completion, show no significant effect, and get interpreted as "the AI feature doesn't work" — when the real problem is that the study was never adequately powered to detect the effect in the first place.

CUPED and post-stratification exist precisely to address this: by controlling for pre-experiment variance, they effectively shrink the noise floor and let experiments reach significance faster without requiring proportionally larger sample sizes.

The practical implication is straightforward: AI experiments require either larger samples, longer runtimes, tighter metric definitions, or variance reduction techniques — and ideally some combination of all four. Teams that don't account for this upfront will spend cycles on underpowered experiments and draw conclusions from noise.

Why AI outputs are noisier than traditional feature tests

When you run an A/B test on a button color, every user in the treatment group sees the same button. The only variance in your results comes from differences in how users respond. That's one source of noise, and it's the source that classical statistical frameworks were built to handle.

AI experiments introduce a second source of noise that sits upstream of the user entirely — the model output itself — and when these two sources compound, the sample sizes and run times that feel adequate for traditional tests become systematically insufficient.

Output stochasticity: the noise layer that doesn't exist in button tests

In a deterministic feature test, "treatment" means something precise: every user in the treatment group received the same intervention. In an LLM-powered feature, treatment group members don't share a common experience — they share a distribution of experiences. The model produces different outputs for different users, and often different outputs for the same user on repeated queries.

This means you're not measuring the effect of a feature; you're measuring the average effect of a range of outputs, some of which may be helpful, some neutral, some actively counterproductive. That output-level variance sits on top of normal user-level behavioral variance, and the two sources multiply rather than average out.

Delayed user outcomes and the learning curve problem

The METR study on AI-assisted developer productivity illustrates this failure mode with unusual clarity. In a controlled within-subject design — where the same 16 experienced open-source developers alternated between AI-assisted and non-AI-assisted tasks — developers perceived a 20–24% speedup from using Cursor. Controlled measurements showed actual slowdowns. Three-quarters of participants saw reduced performance; only one quarter improved.

Notably, the one developer with more than 50 hours of prior Cursor experience was among the top performers, suggesting that AI tool benefits, if they exist, accrue over time as users climb a steep learning curve. This creates a specific measurement problem: the costs of an AI feature (slower task completion during the adaptation phase) are immediate and show up cleanly in your experiment window, while the benefits may only materialize weeks later as users internalize new workflows.

As Simon Willison noted in discussing the study, "getting a significant productivity boost from LLM assistance and AI tools has a much steeper learning curve than most people expect." A short experiment window captures the noisiest, least representative phase of user behavior — which is exactly when most teams are measuring.

Metric attribution lag: when the outcome you care about happens later

Even setting aside the learning curve, there's a separate problem with causal chain length. A coding assistant might improve output quality in ways that only surface in code review rates or production bug counts weeks after the experiment closes. A customer support AI might reduce churn in ways that take a full billing cycle to register.

This isn't the same as the learning curve problem — it's about the distance between the AI's output and the business outcome you actually care about. The longer that causal chain, the more opportunity there is for confounding variables to enter the measurement, and the less your experiment window reflects the true steady-state effect.

How these three sources interact to inflate required sample sizes

Each of these noise sources — output stochasticity, user adaptation lag, and metric attribution lag — independently increases within-group variance. When they operate simultaneously, the effect on required sample sizes is compounding. Higher variance raises the MDE threshold, which means you need proportionally larger samples to achieve the same statistical power at the same confidence level.

A sample size calculation done using traditional A/B test variance assumptions will underpower an AI experiment, often by a significant margin.

The practical corrective is to treat variance reduction as a first-class concern in AI experiment design. Techniques like CUPED — which controls for pre-experiment covariates like prior tool experience, exactly the confound the METR study identified — and post-stratification can meaningfully reduce the sample sizes required to reach significance. That's not a complete solution to AI-specific noise, but it's a concrete lever that teams can pull while they work on the harder problems of metric selection and experiment duration.

Eval scores measure the model; these metrics measure whether users are better off

Accounting for AI-specific variance gets you to a valid experiment. Choosing metrics that actually reflect user outcomes means you're measuring the wrong thing with statistical rigor — which is its own kind of failure. Metric selection is the single highest-leverage decision you make in an AI experiment.

Get it wrong and you'll either miss a genuinely effective feature or declare a win on something that doesn't move the needle for users. This problem is more acute in AI experiments than in traditional A/B tests precisely because the outputs are probabilistic and the outcomes you care about are often delayed — which means the gap between what you can easily measure and what you should measure is unusually wide.

The hierarchy: downstream behavioral outcomes over model scores

The temptation in AI experiments is to reach for metrics that are close to the model: eval scores, BLEU scores, accuracy benchmarks, response quality ratings. These are measurable, fast to compute, and feel rigorous. The problem is they answer the wrong question. Evals tell you whether the model is better. A/B tests should tell you whether users are better off — and those two things frequently diverge.

The right hierarchy puts downstream behavioral metrics at the top: retention rate, task completion rate, session depth, revenue per user. These are the outcomes that reflect whether the AI feature is actually delivering value. Intermediate model-quality scores can serve as guardrails — useful for catching regressions — but they shouldn't be your primary success metric.

Landon Smith, Head of Post-Training at Character.AI, put it directly: the goal is to compare modeling techniques "from the perspective of our users," guiding research in the direction that best serves the product, not the benchmark.

The North Star Metric framework is a useful anchor here. A well-chosen NSM reflects the core value delivered to users, predicts long-term revenue, and is actionable by the team. Spotify's "time spent listening" is the canonical example — it captures engagement in a way that model-quality scores never could.

Where AI metric design goes wrong

Three failure modes show up repeatedly in AI experiments. The first is measuring model outputs instead of user outcomes — the "vibe check" problem. A model that scores higher on internal evals may not improve task completion at all, and treating eval improvement as a proxy for user value is where many teams go wrong.

The second failure mode is choosing metrics with very low base rates. A metric that converts at 0.5% requires an enormous sample to detect a meaningful effect. The Minimum Detectable Effect (MDE) framework makes this concrete: if the expected effect size is smaller than the MDE given your sample size and significance threshold, the test cannot surface a real difference even if one exists. Low-baseline proxies don't just require more data — they often make experiments practically infeasible.

The third failure mode is metric proliferation. Adding model-quality metrics alongside behavioral metrics feels thorough, but it inflates your false positive rate in ways that compound quickly. With five unrelated metrics evaluated at a 0.05 significance threshold, the probability of at least one false positive reaches 41%. With two metrics, it's still 19%.

The practitioner community has flagged this as one of the most common misuses of significance testing in industry — and AI experiments, with their natural temptation to track both model and user metrics simultaneously, are especially vulnerable.

Variance reduction as a practical lever

Even with the right metrics, AI experiments tend to have high within-group variance — which means longer runtimes and larger required sample sizes. Variance reduction techniques are the practical response to this problem. They don't fix bad metric selection, but they make good metric selection more efficient.

CUPED works by using data you already have about users before the experiment starts — things like their prior usage frequency, historical purchase rate, or tenure — to filter out variance that has nothing to do with the treatment. If heavy users always convert at higher rates regardless of what you test, CUPED controls for that, leaving a cleaner signal. Post-stratification achieves a related reduction through stratified analysis after the fact.

GrowthBook's experimentation platform includes both natively, and post-stratification has been shown to run experiments approximately 20% faster — a meaningful gain when you're waiting on downstream behavioral metrics that take days or weeks to accumulate.

Sequential testing is the third tool worth understanding here. When downstream behavioral metrics take time to mature, teams face pressure to peek at results early. Sequential testing methods allow continuous monitoring without inflating false positive rates — which is particularly relevant when your primary metric is something like 30-day retention rather than an immediate click.

The underlying principle across all three techniques is the same: reduce the noise in your measurement so the signal from a real effect can emerge faster. None of them substitute for choosing a metric that reflects actual user outcomes in the first place.

P-hacking, peeking, and multiple metrics: the validity traps that undermine AI experiment results

Even when you've chosen the right metrics and accounted for AI-specific noise, your experiment results can still be meaningless — not because of bad data, but because of how you ran the test. The validity threats in this section aren't exotic edge cases.

They're the default behavior of fast-moving product teams under pressure to ship, and they're especially dangerous in AI experiments where iteration cycles are fast and the temptation to keep tweaking until something works is structurally baked into the workflow.

Every metric you add compounds your false positive rate

Every time you add a metric to an experiment and evaluate it at a 0.05 significance threshold, you're not just measuring one more thing — you're compounding your family-wise error rate. GrowthBook's documentation puts this plainly: if you test the same hypothesis across 20 different metrics at the 5% significance level, the probability of finding at least one statistically significant result by chance alone climbs to around 64%. That's not a failure of execution. That's arithmetic.

The five-metric version of this problem is less dramatic but more common. Testing five independent metrics at α = 0.05 yields a false positive probability of roughly 22.6%. The math: each metric has a 95% chance of not producing a false positive (that's what 0.05 significance means). For five independent metrics, the chance that all five avoid a false positive is 0.95 × 0.95 × 0.95 × 0.95 × 0.95, or about 77%. Which means the chance that at least one produces a false positive is the remaining 23%.

And that calculation assumes the metrics are independent, which they almost never are. Page views correlate with funnel starts. Session length correlates with engagement scores. When metrics move together, the theoretical false positive rate becomes an approximation rather than a ceiling.

The practical implication: teams that track ten guardrail metrics plus three primary metrics without applying any correction aren't running a rigorous experiment. They're running a lottery.

P-hacking in AI prompt and model iteration

AI experiments create a specific p-hacking loop that traditional A/B testing rarely encounters. When you're testing a button color, there's one button. When you're testing a prompt configuration, there are hundreds of plausible variants — different phrasings, different context windows, different temperature settings — and the natural workflow is to iterate until something looks good, then declare a winner.

GrowthBook's documentation names the underlying fallacy directly: the Texas Sharpshooter Fallacy, where a marksman shoots at a barn and then paints the target around the bullet holes. Testing many prompt variants and retroactively identifying the "significant" one is structurally identical. The target was drawn after the shooting.

What makes this insidious is that it doesn't require bad intent. GrowthBook's documentation notes that p-hacking occurs "either consciously or unconsciously" — analysts exploring different subgroups or time windows until something surfaces. In AI development, where prompt iteration is a legitimate engineering practice, the line between exploration and data dredging is easy to cross without noticing.

The fix is procedural: specify the exact prompt or model configuration being tested before running the experiment, not after reviewing preliminary results.

The peeking problem and sequential testing

Peeking — checking results before the pre-specified sample size is reached and stopping early when significance appears — is one of the most common ways experiments get invalidated. It inflates Type I error rates because the probability of crossing the significance threshold at least once during an experiment is higher than the probability of crossing it at the planned endpoint. Stop early enough times on enough experiments, and your 5% false positive rate quietly becomes something much larger.

AI experiments are particularly vulnerable here because delayed outcome metrics create pressure to look early. If your primary metric is 30-day retention, waiting for full data collection feels costly. The temptation to check at day 10 and ship if things look promising is real.

Sequential testing is the technical solution. It allows valid inference at any interim look by adjusting the significance threshold dynamically — so you can check results mid-experiment without inflating your error rate. Within GrowthBook, sequential testing is available as part of the core experiment workflow, which means teams don't need to implement the math themselves.

Correction methods and the A/A baseline

For teams running multiple metrics, two correction approaches are worth knowing. Bonferroni correction divides the significance threshold by the number of tests (α/n), making it the most conservative option — appropriate when any false positive is costly.

Benjamini-Hochberg takes a different approach: instead of asking "what's the chance of any false positive at all?" (which Bonferroni answers), it asks "among the results I'm calling significant, what fraction are probably false positives?" That's a more useful question when you're tracking many metrics — it's less likely to dismiss real effects as noise, at the cost of accepting that some small fraction of your "significant" results may not be real. GrowthBook's experimentation platform includes both correction methods natively.

Before running any high-stakes AI experiment, an A/A test — where both variants receive identical treatment — serves as a calibration check on your measurement infrastructure. A healthy A/A test will occasionally surface a single metric as significant due to the inherent 5% false positive rate; that's expected.

What signals a broken setup is three or four metrics simultaneously showing 99%+ or sub-1% probability to win. That pattern indicates a tracking problem, a randomization failure, or a data pipeline issue — and it's far better to discover this before your experiment than after.

The broader context here matters: industry estimates suggest roughly one in three experiments produces a genuine improvement — though the exact figure varies by domain and team maturity. When your baseline success rate is that low, inflating false positive rates through multiple testing, peeking, or prompt-iteration p-hacking doesn't just distort individual results — it systematically corrupts your team's ability to learn what actually works.

Statistical significance is not enough: why practical significance matters more in AI tests

There are two questions at the heart of every experiment, and they are not the same question. The first: Is this result real? The second: Does this result matter? Statistical significance answers the first. It tells you whether the effect you observed is likely to be genuine rather than a product of random variation. It says nothing — nothing at all — about whether that effect is large enough, valuable enough, or meaningful enough to act on.

"Statistical significance helps establish whether a result is reliable, while practical significance helps determine whether it is worth acting on." These are sequential questions, not interchangeable ones. Passing the first does not mean passing the second.

This distinction is widely misunderstood. A Hacker News commenter who works in industry described it as "one of the most common fallacies I observe in industry and a lot of science" — the tendency to read "statistically significant" as synonymous with "notable" or "meaningful." It isn't.

And for AI experiments specifically, where shipping a new model version or prompt configuration carries real costs in inference, latency, maintenance burden, and regression risk, conflating the two questions is an expensive mistake.

The scale problem: when statistical significance becomes automatic

The mathematical relationship between sample size and p-values creates a trap that's easy to miss. As your user base grows, even vanishingly small effects produce very low p-values. At the volumes typical of AI product deployments — millions of sessions — almost any difference between variants will clear the p < 0.05 threshold.

One Hacker News commenter illustrated this directly: "This intervention causes an uplift in [metric] with p<0.001. High statistical significance! The uplift: 0.000001%. Meaningful? Probably not."

This isn't a hypothetical edge case. It's the operating reality for teams running AI experiments at scale. The probabilistic output layer of AI systems means there are always some measurable differences between variants. The question is never whether a difference exists — at sufficient scale, you will always find one. The question is whether the difference is large enough to justify the cost and risk of shipping.

Consider the NN/g example: Design A has an 85.0% checkout completion rate; Design B has 85.2%. A test returns p < 0.05 — statistically significant. But a 0.2 percentage point difference is almost certainly not worth acting on. The result is real. It is not worth shipping for.

Define your MDE before the experiment runs, not after

The practical solution is to define your minimum detectable effect — the smallest improvement that would actually change a business decision — before the experiment launches. Not after you see the results. After you see the results, you're rationalizing.

GrowthBook's documentation defines MDE as the minimum difference between control and treatment that can be detected given a specific significance threshold, statistical power, and sample size. The critical discipline is ensuring that the effect size you expect to see exceeds the MDE you've defined as meaningful. If a 0.2% improvement in task completion wouldn't change whether you ship the feature, don't declare victory when you detect it.

Define the threshold that would change the decision, and treat anything below it as a null result regardless of p-value.

For AI features specifically, this bar needs to reflect the full cost of shipping. A new model version isn't free — it carries inference cost, latency implications, and the ongoing maintenance burden of supporting a more complex system. The practical significance threshold should be calibrated against those costs, not just the upside metric.

If a 1% improvement in retention doesn't cover the cost of running a heavier model, then 1% is not a meaningful win. Define that threshold upfront, write it into your experiment plan, and hold to it when results come in.

Experiment platforms that build MDE into experiment design and track cumulative impact across experiments do so precisely because individual p-values don't tell the full story. A single experiment might show a statistically significant but tiny effect; the question of whether that effect compounds into meaningful business outcomes requires a different lens entirely.

The mindset shift is this: statistical significance is a filter for noise, not a mandate to ship. It tells you the signal is real. You still have to decide if the signal is worth acting on — and that decision should be made before you ever look at the data.

Where AI experiments break down: setup, execution, and interpretation

The through-line of this article is simple, even if the mechanics aren't: AI experiments fail not because teams are careless, but because they apply frameworks built for one noise source to problems with two. Output stochasticity, user adaptation lag, and metric attribution lag compound in ways that make traditional sample size intuitions unreliable, traditional metric choices misleading, and traditional result interpretation actively dangerous.

The fix isn't exotic — it's disciplined setup before the experiment runs and honest interpretation after it closes.

Lock in your metric and MDE before a single user is bucketed

The most consequential decisions in an AI experiment happen before a single user is bucketed. Lock in your primary metric — a downstream behavioral outcome, not an eval score — and define the minimum effect size that would actually change your shipping decision, factoring in the real costs of the new model or configuration.

If you can't articulate what "meaningful" looks like before you see data, you're not running an experiment; you're running a search for confirmation.

Mid-experiment discipline: peeking, metric proliferation, and variance control

Resist the pull to check results early, especially when your primary metric takes weeks to mature. If you need to monitor mid-experiment, use sequential testing — it's built for this. Keep your metric count tight, apply Bonferroni or Benjamini-Hochberg correction if you're tracking multiple outcomes, and treat guardrail metrics as guardrails, not additional success criteria.

GrowthBook ships sequential testing and both correction methods natively, so the infrastructure isn't the barrier — discipline is.

A significant result is not a mandate to ship

A p-value below 0.05 tells you the effect is probably real. It does not tell you the effect is worth acting on. Ask both questions in sequence: Is this result real? And is it large enough to justify the cost of shipping? If the detected effect sits below the MDE threshold you defined before the experiment, treat it as a null result regardless of what the p-value says. That threshold exists precisely so you don't rationalize small wins into shipping decisions.

The honest truth is that most AI experiments — like most experiments generally — won't produce a clear win. That's not failure. That's how you build a reliable signal over time instead of a catalog of confident mistakes. This article was written to give you a clear picture of where AI experimentation actually breaks down, and what to do about it. If even one section changes how you design your next experiment, it's done its job.

The highest-leverage move depends on where you are in the process

Where are you in the process?

About to launch an AI experiment: Write down your primary metric and your MDE threshold before you configure anything else. If you cannot articulate what "meaningful" looks like before seeing data, stop and define it now. Those two decisions will determine whether your results are interpretable.

Already ran an experiment and unsure whether to trust results: Check two things: (1) Did you define your success criteria before or after you saw the data? (2) Did you apply any correction for multiple metrics? If the answer to either is "after" or "no," your result may not be trustworthy regardless of the p-value.

Earlier in the process, not yet running experiments: Run an A/A test on your measurement infrastructure before anything else. A broken tracking setup invalidates every experiment downstream — and it's far cheaper to find that out now than after you've drawn conclusions from corrupted data.

Related insights

Sign up for free

Take Growthbook for a spin, no credit card required.

Create my account

Example H2

See All Articles

Experiments

Feature Flags

CLI vs MCP: TLDR, it doesn’t matter as much as you think

Oct 21, 2026

min read

Your agent should know how to do the job whichever interface it uses.

Your coding agent can already run terminal commands. Your product manager's assistant can connect to remote tools. Both need to inspect the same experiment, understand the same metric, and prepare changes to the same feature flag.

That creates a familiar question: should you give them a CLI or an MCP server?

The usual answers mix several concerns. A CLI is easy to compose with scripts. MCP gives compatible clients a standard way to discover and invoke tools. Skills can supply the instructions that make either route useful. None of those statements tells you whether the agent knows your release process or can distinguish a draft from a live change.

For GrowthBook, the choice has become smaller. We've built the agent layer around a REST API and reusable workflow skills, then made those available through different interfaces. Your choice of CLI or MCP no longer needs to determine which product workflow your agent can understand.

It still determines how the agent connects, executes requests, and handles credentials. This article explains that distinction, shows the same disabled-flag operation through both routes, and gives you a way to evaluate the integration you actually intend to use.

The debate combines three different questions

Start with a specific job: prepare a release control for a new checkout flow. The agent needs to know which project owns checkout, which environments exist, what the default behavior should be, and whether the proposed flag key already exists.

Choosing an interface answers only part of that job.

How can the agent reach the product?

A command-line interface lets an agent invoke a program in an environment where it has shell access. That program can make authenticated API requests and return data. You can also run the same commands yourself, put them in scripts, and preserve output for inspection.

The Model Context Protocol architecture connects a host application to servers through clients. An MCP server exposes capabilities that a compatible host can discover and call. The host might be a coding environment, a desktop assistant, or another agent application.

These categories overlap. A terminal-based agent can also be an MCP client. A local MCP server can be a process launched by that client. A remote MCP connection can work without the host giving the model a general-purpose shell.

So “terminal agent” doesn't automatically mean “use the CLI,” and “MCP” doesn't automatically mean “remote service.” Ask what access the runtime provides before choosing the adapter.

What procedure should the agent follow?

An API can expose a create operation without teaching an agent when to use it. A syntactically valid feature flag might still have the wrong project, an ambiguous key, or a default value that doesn't match the application.

That's the job of a skill: reusable instructions for a recognizable task. The Agent Skills format gives those instructions a portable structure, including a skill entry point and supporting references. A workflow can describe the context to inspect, the sequence to follow, and the evidence to return.

For the checkout example, useful guidance says to resolve environments, check the permanent key, choose a value type, and create the flag disabled. Merely exposing a create command leaves those decisions to the agent's general knowledge.

Skills are also useful when the right answer is to take no action yet. “Create a flag” and “design an experiment” are related requests, but they can require different objects and sequencing. An agent needs enough product guidance to make that distinction.

What context makes the procedure relevant?

Even a good playbook needs the current product state. The agent should inspect the objects in your GrowthBook organization and, when it is changing application code, the repository's SDK initialization and tests.

Those are different sources of context. GrowthBook supplies flags, experiments, metric definitions, and other authorized product resources. Your coding runtime supplies the application files it can access. An MCP connection doesn't by itself grant repository access, and a CLI doesn't by itself explain your metric definitions.

Evaluate the combination: access to the product, a maintained procedure, and enough context to apply that procedure. A comparison that changes all three at once cannot isolate the effect of CLI versus MCP.

GrowthBook puts the durable parts below the interface

We separated the agent layer into responsibilities that can be reused. The product API exposes operations. Skills explain workflows. The interface connects the agent to those two layers.

This is the architectural shift behind GrowthBook's agent experience. Instead of making every client integration carry its own interpretation of experimentation, we can share the interpretation and change how it is delivered.

The API provides the operations

GrowthBook's REST API makes product objects addressable. An agent can inspect a project, retrieve a flag, or perform an authorized operation against those objects.

The rebuilt API described in GrowthBook 4.4 uses shared schemas to support types, validation, and API documentation. The CLI is generated from the API definition. That reduces the amount of separately maintained command logic needed to expose product operations.

The OpenAPI specification explains the underlying principle: a machine-readable description can represent an HTTP API's paths, operations, inputs, and responses. Generation is useful because it derives another interface from that contract.

Generation doesn't mean any installed binary knows every future endpoint. The generated client still has a version, and your GrowthBook server still has a version. A self-hosted instance can lag behind the public documentation. Treat API compatibility as a deployment fact you verify.

Skills provide the workflow guidance

GrowthBook's feature-flags skill routes requests to more specific workflows. Creating a flag, inspecting dependencies, changing targeting, requesting review, and publishing a revision are separate procedures.

That structure lets the agent load the guidance relevant to the current job. The skill authoring guidance on progressive disclosure supports this approach: keep the entry point focused and place detail in references that are loaded as needed.

The benefit is maintainability as well as context management. A correction to a flag workflow can be made in the maintained skill rather than repeated across a series of tool descriptions and client-specific prompts.

There are two shell concepts to keep distinct. The generated growthbook CLI is a terminal interface to the product API. The skills repository also includes a small gb-call helper for making REST requests. Installing a skill doesn't make that helper a globally available command; its location depends on the installation. Both can reach the API, but their configuration and invocation are different.

MCP provides a thin bridge

The current GrowthBook MCP implementation exposes four tools: growthbook_list_skills, growthbook_read_skill, growthbook_api_read, and growthbook_api_write.

An agent discovers a domain, reads the relevant workflow, then makes API calls. It doesn't need a dedicated MCP tool for every product endpoint. Calls described as gb-call GET in a skill map to the read tool; mutating methods map to the write tool with the same path and body.

The bridge does not run the shell helper. It forwards authenticated requests. Product-side permissions and validation remain important because a small tool surface can still reach many operations.

Shared guidance also has a delivery boundary: the MCP server bundles skills when it is built, using a pinned source revision. A newly edited skill in the repository needs to be included in a subsequent server build before that server supplies it. “Shared source” is a maintainability claim, not a promise of instant synchronization.

Explore the shared flag workflows

Open the feature-flags skill to see the procedures that guide creation, targeting, reviews, and publishing. Bring the same workflow knowledge to the agent interface your team uses.

View the Flag Skill

The same disabled flag can use either route

The practical question is whether the interface changes the job. Let's create a Boolean flag called checkout-redesign, with a false default and every environment disabled.

This is an API example for a sandbox project, not an application integration tutorial. It creates a control object; your application still needs a correctly configured GrowthBook SDK to evaluate it. The feature flag documentation covers the product concepts behind that integration.

Connect and verify before preparing the write

For the terminal route, install the current GrowthBook CLI, configure a Personal Access Token through its interactive setup, and inspect the available command syntax:

npm install -g growthbook
growthbook configure
growthbook whoami
growthbook features create --help
growthbook features get --help

Check that the active server and identity are the ones you intend to use. Prefer a tested, pinned CLI version in repeatable automation. Don't include a live token in a command you plan to share.

For an MCP route, the GrowthBook Cloud setup uses the hosted endpoint and browser OAuth. In a client using the documented mcpServers configuration shape, such as Cursor, add:

{
  "mcpServers": {
    "growthbook": {
      "url": "https://mcp.growthbook.io/mcp"
    }
  }
}

Complete the browser authorization and confirm tool discovery. Other clients can use a different configuration shape. Self-hosted GrowthBook users should follow the local stdio or self-hosted HTTP instructions rather than point a private instance at the Cloud service.

Next, let the connected agent discover the flag-creation workflow. These are tool-call parameters, shown separately in the order to invoke them:

{"name":"growthbook_list_skills","arguments":{}}

{"name":"growthbook_read_skill","arguments":{"name":"feature-flags"}}

{"name":"growthbook_read_skill","arguments":{"name":"feature-flags/references/flag-create"}}

The returned guidance should describe the prerequisites for creating the flag. If the workflow isn't present, resolve the server's bundled skill version before substituting instructions from an older integration.

Resolve real IDs and construct one payload

The flag-creation workflow checks existing keys, lists projects, and resolves environments. In the MCP client, invoke the read tool with each of these argument objects:

For the CLI route, perform that discovery with the corresponding command groups documented in the CLI command catalog:

growthbook features list-keys --output-format json
growthbook projects list --output-format json
growthbook environments list --output-format json

Inspect each command's help if your installed version differs. The returned keys, project IDs, and environment IDs are the inputs to the payload below. In MCP, the equivalent read-tool arguments are:

{"path":"/api/v2/feature-keys"}

{"path":"/api/v1/projects"}

{"path":"/api/v1/environments"}

Verify that checkout-redesign isn't taken, identify the sandbox project's ID, and enumerate every actual environment. These read responses determine the payload; don't treat example environment names as a complete inventory of your organization.

Save the following as flag.json, replacing <PROJECT_ID> and the environment keys with the discovered values. This example assumes the only environments are staging and production:

{
  "id": "checkout-redesign",
  "valueType": "boolean",
  "defaultValue": "false",
  "description": "Control exposure to the redesigned checkout",
  "project": "<PROJECT_ID>",
  "environments": {
    "staging": { "enabled": false },
    "production": { "enabled": false }
  }
}

The API represents defaultValue as a string, even for a Boolean flag. Explicitly disabling each environment avoids relying on the organization's default state for newly created flags. Use a PAT for this example so the caller has a user identity for attribution.

Review the permanent key, project, value, and disabled states before submitting. If the intended job is an experiment, route to experiment design first instead of creating an unrelated flag and hoping to connect it later.

Submit once, then read the object back

With the CLI, the create command accepts a JSON body. In a Bash-compatible shell, inspect the request with dry run before submitting:

growthbook features create --body "$(cat flag.json)" --dry-run
growthbook features create --body "$(cat flag.json)" --output-format json

The first command previews a request; it doesn't prove the server will accept it. Run the second only after checking the preview and approving this creation. In PowerShell, use that shell's file-reading syntax rather than paste the Bash substitution unchanged.

The PowerShell equivalent, using the same reviewed file, is:

$flagPayload = Get-Content -LiteralPath .\flag.json -Raw
growthbook features create --body $flagPayload --dry-run
growthbook features create --body $flagPayload --output-format json

The same distinction applies: preview first, approve the specific creation, then submit. Neither command changes the application's deployed code.

Through MCP, call growthbook_api_write with the same payload serialized into its body string. Substitute the same resolved project and environment names:

{
  "method": "POST",
  "path": "/api/v2/features",
  "body": "{\"id\":\"checkout-redesign\",\"valueType\":\"boolean\",\"defaultValue\":\"false\",\"description\":\"Control exposure to the redesigned checkout\",\"project\":\"<PROJECT_ID>\",\"environments\":{\"staging\":{\"enabled\":false},\"production\":{\"enabled\":false}}}"
}

Choose one creation route. Don't run both against the same key; they target the same product object, and the second creation should encounter an existing key.

Verify through the CLI get command:

growthbook features get --id checkout-redesign --output-format json

Or invoke growthbook_api_read with:

{"path":"/api/v2/features/checkout-redesign"}

Check the returned key, project, value type, default value, disabled state of every environment, and absence of unintended rules. Report those facts rather than “success.” No targeting or exposure change is included in this example.

Choose the route that fits the runtime

Once the procedure and API operation are shared, the remaining choice is operational. Where does the agent run? What can it execute? How does it authenticate? What does your team need to inspect afterward?

Shell access favors terminal composition

A shell-capable agent can run the CLI alongside repository tools, save structured output, and combine product inspection with local checks. That is useful when the job includes code changes, generated files, or a reproducible script.

For example, a flag audit can produce an inventory file while an engineer separately checks code references. The agent should preserve the association between the GrowthBook key and each repository reference. The final artifact can include both the product state and the proposed code diff.

The shell makes composition available; it doesn't make a workflow safe by default. A script can select the wrong profile or swallow an error. Decide which failures stop the workflow, where outputs are stored, and which steps need a reviewable artifact.

Remote tool access favors MCP clients

MCP is useful when the host already provides a tool connection but doesn't expose a terminal. A PM can inspect an experiment through a compatible assistant without installing a product CLI inside that assistant's runtime.

The MCP authorization specification defines an authorization framework for HTTP transports. GrowthBook Cloud uses browser OAuth, while local stdio configurations use credentials supplied to the process. Those are distinct deployment paths.

MCP also gives hosts a structured description of tools. The tool specification includes annotations such as read-only and destructive hints. Hosts can use those signals in their interaction design, but the signals are not an access-control boundary. The product must still enforce the caller's actual permissions.

Use a small decision table

Your immediate requirement	Route to consider	What to verify
Combine product operations with local files and scripts	CLI plus maintained skills	Shell access, profile, installed version, structured output
Connect a compatible assistant without a shell	Hosted MCP	HTTP/OAuth support, identity, tools, bundled workflow
Keep requests inside a self-hosted deployment	CLI or self-hosted MCP	Network reachability, server version, credentials, trusted app origin
Reuse a procedure across different team clients	Shared skills through either route	Workflow revision, API compatibility, expected review artifact

You can support more than one row. An engineer's CLI and a PM's MCP connection can operate on the same objects with different identities and permissions. Standardizing the workflow is often more useful than standardizing everyone's client.

Compare actual outcomes, not tool counts

Four MCP tools can address a large API. A large CLI command catalog can expose the same operations. Counting entries tells you little about whether an agent completed the intended job correctly.

Likewise, there is no universal token or speed result implied by the architecture. The client, model, instructions, response size, pagination, and number of requests all affect a real run. Measure the work you need instead of importing a result from an unrelated integration.

Keep the evaluation task constant

Use one sandbox project and one bounded task. For a read test, ask each route to find a named flag and identify its enabled environments, current revision, and relevant dependencies. For a write test, use separate temporary keys with the same reviewed disabled-flag requirements.

Give both runs the same expected output. Record whether each identified the correct objects, loaded the relevant workflow, handled missing data, and preserved the boundary between creation and exposure. Measure elapsed time and context consumption only alongside those correctness checks.

If one run gets rich workflow guidance and the other gets only a command name, you're testing the guidance as well as the interface. That can still be a useful product evaluation, but describe what changed.

Test failure behavior deliberately

Try a nonexistent object, an existing key, and a credential without the required permission. The agent should identify the failure and stop the dependent action. It should not invent an ID, silently pick another environment, or reinterpret a permission error as permission to retry with a broader credential.

The revision workflow adds another important test: multiple open drafts. When a chain of changes belongs in one revision, the agent must preserve its version rather than repeatedly ask for whichever draft is latest.

A creation receipt and a publication receipt are different artifacts. If your evaluation only checks that a request returned without error, it can miss the point where a proposed change became live or where a draft failed to include the intended edits.

Record the versions behind the result

Capture the CLI version, server version when available, client configuration, and the skill text or revision used. With MCP, inspect the guidance actually returned by the connected server. With installed skills, inspect the local instructions actually loaded.

That record makes a later regression diagnosable. A changed result may come from new guidance, a client update, a changed API, or different product state. “MCP became worse” is too broad to help you fix it.

Build workflows that survive the next client

The most useful consequence of GrowthBook's design is organizational. Engineers, PMs, and analysts can choose the agent surface that fits their work while referring to the same flags, experiments, and metrics.

An engineer can prepare a disabled flag from a terminal. A reviewer can inspect its draft in the app. An assistant connected through MCP can retrieve the same object and explain its state. The handoff should carry an ID, a revision where applicable, the proposed behavior, and the decision still required.

This is where the CLI-versus-MCP question loses much of its importance. Your release procedure doesn't need to be rewritten around each client. The product holds state; the API exposes operations; skills explain the work; the chosen interface delivers access.

Start with one inspection or sandbox creation. Require the agent to return a concrete object and its verified state. Then add the next workflow only when the current one is reliable enough for your team to review.

GrowthBook's feature flag platform gives that work a common place to live. The durable choice is how you connect release control and measurement to your team's process. CLI and MCP are ways to carry that process into the tools people already use.

Start with a common foundation

Set up GrowthBook for the flags, experiments, and metrics your agents will share. Then choose the CLI or MCP connection that fits each team member's work.

Get Started With GrowthBook

Experiments

Analytics

Standard deviation vs variance: Key differences for A/B testers

Oct 21, 2026

min read

A metric can have wide user-to-user variation and still yield a precise experiment estimate.

That is why confusing standard deviation with standard error creates bad A/B testing decisions. A dashboard may show that users differ substantially while the average effect is estimated closely enough to guide a release. Those statements can both be true.

Variance and standard deviation describe spread. Variance works on a squared scale; standard deviation takes its square root to return to the metric's original units. Neither is automatically the uncertainty around an experiment result.

For A/B testers, the useful distinction is practical: use standard deviation to communicate outcome variability, use variance in the calculations that combine uncertainty, and inspect the standard error or interval for the treatment effect. Start by making sure all three describe the correct unit of analysis.

Understand the difference in units

Variance uses squared distances

Outcomes above and below a mean have deviations with opposite signs. Simply averaging those signed deviations gives zero. Variance avoids that cancellation by squaring each deviation before combining them.

The sample variance formula is s² = Σ(xᵢ − x̄)² / (n − 1), where x̄ is the sample mean and n is the number of observations. The symbol Σ means to add the terms across observations.

If the outcome is measured in seconds, variance is measured in seconds squared. That is mathematically useful but less intuitive for explaining a product experience. “Variance is 4 seconds squared” does not mean users differ by 4 seconds.

Standard deviation returns to the original scale

Standard deviation is s = √s². A variance of 4 seconds squared corresponds to a standard deviation of 2 seconds. Both describe the same dispersion, expressed on different scales.

Do not define standard deviation as the average absolute distance from the mean. That is a different measure. Squaring deviations gives large deviations more influence, and taking the square root afterward does not undo that weighting.

Quantity	What it describes	Units for task time
Variance	Squared dispersion in outcomes	Seconds squared
Standard deviation	Outcome dispersion on the original scale	Seconds
Standard error of the mean	Sampling variability of an estimated mean	Seconds

Neither variance nor standard deviation requires a normally distributed population merely to be calculated. Normality matters for particular interpretations and inferential procedures, not for the existence of these summaries when the required moments are finite.

Calculate both from the same observations

Work through a small dataset

Use four synthetic task times: 2, 4, 4, and 6 seconds. This tiny dataset is for arithmetic, not evidence about a real product or a basis for confident inference.

The mean is (2 + 4 + 4 + 6) / 4 = 4 seconds. Deviations from the mean are −2, 0, 0, and 2 seconds. Their squares are 4, 0, 0, and 4 seconds squared, totaling 8.

Treating these observations as a sample, the usual sample variance is 8 / (4 − 1) = 8/3, or about 2.667 seconds squared. The sample standard deviation is √(8/3), or about 1.633 seconds.

This is a useful check on a report. If someone describes the same sample's variance as 1.633, they have probably substituted the standard deviation. If the units are missing, the mistake is much harder to spot.

Choose sample or population formulas deliberately

If those four observations constitute the entire finite population you want to describe, population variance divides by 4: 8/4 = 2 seconds squared. Population standard deviation is √2, or about 1.414 seconds.

The population and sample distinction depends on what you are estimating. Having every recorded event from an experiment does not necessarily make those events the full population of future users or future conditions you care about.

The n − 1 denominator makes the usual sample variance an unbiased estimator of population variance under independent, identically distributed sampling with finite variance. It does not make the square root exactly unbiased for population standard deviation. Nor does it correct biased sampling or dependence between observations.

Verify the calculation with explicit function names

Python's statistics functions distinguish sample calculations from population calculations. With Python 3 installed, this standalone example requires no external packages or data:

from statistics import variance, stdev, pvariance, pstdev

times = [2, 4, 4, 6]
print(round(variance(times), 3), round(stdev(times), 3))
print(round(pvariance(times), 3), round(pstdev(times), 3))

The first line of output is 2.667 1.633; the second is 2 1.414. The different denominators explain the difference. Before comparing statistics from two tools, check their sample/population defaults and handling of missing values.

Find the noise you can reduce

Explore practical variance reduction methods, including metric design and CUPED, and the conditions that make each approach useful.

Read the Variance Reduction Guide

Use standard errors for experiment uncertainty

Distinguish users from estimated means

Standard deviation describes how users' outcomes vary. Standard error describes how an estimator would vary across repeated samples. For an independent sample, the estimated standard error of its mean is s / √n.

Suppose a user-level task-time metric has a sample standard deviation of 20 seconds among 10,000 independent users. The estimated standard error of the mean is 20/√10,000 = 0.2 seconds. Large differences between users coexist with a much smaller uncertainty around their average.

Collecting four times as many independent users would halve this standard error if the outcome variance stayed similar. It would not mechanically halve user-level standard deviation. The individual experience remains variable even as the estimated mean becomes more precise.

Combine arm variances before taking the square root

For independent treatment and control groups, a simple unadjusted difference in means has estimated variance s²ₜ/nₜ + s²꜀/n꜀. Its standard error is the square root of that sum. You do not add the two arm standard deviations and call the result the experiment's uncertainty.

Take a separate synthetic summary with 10,000 independent users in each arm and a 20-second standard deviation in both. The variance of the estimated difference is 400/10,000 + 400/10,000 = 0.08 seconds squared. Its standard error is √0.08, about 0.283 seconds.

If the observed treatment-minus-control difference is −1 second, an illustrative large-sample, unadjusted 95% normal interval is −1 ± 1.96 × 0.283, approximately −1.554 to −0.446 seconds. Negative values mean faster completion under this metric definition.

This example assumes independent groups and an appropriate large-sample approximation. It is not the exact output of GrowthBook's relative-lift, sequential, covariate-adjusted, or ratio-metric methods. GrowthBook's statistical details describe how the platform estimates effects and their uncertainty.

Avoid interpreting intervals as outcome ranges

That interval concerns the mean treatment effect. It does not say that 95% of individual users improved by between 0.446 and 1.554 seconds. An individual user's causal effect is a different quantity, and the experiment does not observe both potential outcomes for the same person.

Likewise, mean ± one standard deviation is not a universal statement about where 68% of users fall. That familiar interpretation depends on an approximately normal distribution. Skewed task times or revenue can look very different.

The frequentist confidence level describes the repeated-sampling coverage of the interval procedure under its assumptions. It is not a posterior probability assigned to a fixed realized interval.

Check what your metric actually measures

Match the variance to the randomization unit

If users are randomized and each contributes many requests, request rows are not automatically independent experimental units. Treating 100 requests from one person as 100 unrelated users can make uncertainty look smaller than it should.

Define the outcome at the intended unit or use a method that accounts for clustering. GrowthBook's aggregate data requirements are relevant when supplying precomputed summaries: the sample size, sum, and dispersion must correspond to the statistic and analysis method.

Two teams can report different standard deviations without either making an arithmetic mistake. One may summarize per-request latency while the other summarizes each user's average latency. They are describing different outcome distributions. Clarify the grain before comparing their numbers.

Paired measurements need another distinction. If the same users provide before-and-after outcomes, the measurements within each pair can be correlated. Analyze each user's difference or use an appropriate paired method; do not apply the independent-arm formula automatically. The paired-means framework treats those differences as the observations of interest. Pairing also does not remove time trends or establish causality by itself; the design still determines which comparison is defensible.

Inspect tails instead of deleting them casually

Large observations influence both variance and standard deviation. A few unusually long tasks can dominate a time metric; a few large purchasers can dominate revenue. Determine whether those values reflect valid behavior, instrumentation defects, retries, or unit errors.

A valid expensive user is not automatically an outlier to discard. Removing high values after seeing an experiment result can change the estimand and introduce selective analysis. Decide justified exclusions or transformations before interpreting the test.

Report complementary summaries when they answer useful questions: a histogram, median, or a relevant tail percentile can show what a single spread measure hides. Those summaries do not replace the mean effect if the mean remains the decision metric.

Keep units consistent across pipelines

Converting seconds to milliseconds multiplies every value by 1,000. Standard deviation also multiplies by 1,000, but variance multiplies by 1,000,000. A dramatic numerical variance increase can therefore be a unit conversion rather than a product regression.

For the four-value example, sample standard deviation becomes approximately 1,633 milliseconds and variance becomes approximately 2,666,667 milliseconds squared. The underlying task times have not changed. Store units with metric definitions and inspect them when comparing dashboards.

A lower variance caused solely by rescaling a metric does not create more statistical information. The effect size rescales too. Separate a numerical change in units from an actual improvement in the precision of your estimate.

Also avoid averaging standard deviations from daily reports and labeling the result a weekly standard deviation. The complete-period spread depends on both variation within days and differences between daily means. Keep the underlying observations or sufficient summaries that support the intended calculation. A simple average of displayed daily values generally loses information needed to reconstruct the full distribution.

Turn spread into a better testing plan

Define the outcome before planning the sample

Start with the metric definition: population, identity, aggregation, window, units, exclusions, and desired effect. Estimate variability from representative historical data at that same grain.

Historical variance is an input, not a guarantee. New traffic, a different user mix, or a changed measurement window can alter it. Explore plausible variance and effect-size assumptions rather than treating one historical number as exact.

Keep the two arm variances separate when appropriate. A treatment can change variability as well as its mean. The simple equal-standard-deviation illustration above is a teaching assumption, not a requirement that production groups have identical spread.

Reduce estimation noise without hiding behavior

CUPED and post-stratification use suitable pre-experiment information and covariates to improve effect estimation. CUPED stands for Controlled-experiment Using Pre-Experiment Data. Its value depends on useful predictive information and a valid implementation.

Adjustment can reduce uncertainty in the treatment effect without making real users' outcomes less variable. That distinction prevents a reporting error: a narrower adjusted interval is not evidence that customers now experience a more consistent product.

Also separate missing data from genuine zeros. A user with no purchase may correctly contribute zero revenue; a missing instrumentation event might represent an unknown outcome. Treating both identically can distort the mean and its variance before any statistical engine sees the data.

Report the right quantity for the decision

Reader's question	Useful quantity
How much do individual outcomes differ?	Standard deviation, with distribution context
What enters this uncertainty calculation?	Variance at the correct analysis unit
How precisely is the effect estimated?	Standard error and an appropriate interval
Is the measured difference worth acting on?	Effect size, uncertainty, guardrails, and decision context

For a clear experiment readout, show the metric's unit and analysis grain, the estimated effect, and its appropriate uncertainty interval. Add outcome spread when it helps readers understand the population or diagnose a noisy metric.

GrowthBook's experimentation platform brings defined metrics and statistical analysis together. A trustworthy interpretation still starts with your measurement choices: describe spread with standard deviation, calculate with variance where required, and judge precision using the estimator's uncertainty.

Build a clearer experiment readout

Connect your metrics to GrowthBook and evaluate effects with the analysis method and measurement definitions your team has chosen.

Get Started With Experimentation

Experiments

Analytics

How to calculate true positive rate (TPR)

Oct 21, 2026

min read

Catching 80 defects means little until you know how many defects existed.

Suppose a detector flags 125 suspicious software changes. Engineers inspect them and confirm 80 real defects. That tells you something about alert quality, but it does not tell you how many defects the detector missed. To calculate true positive rate, you need the actual positives outside the alert queue too.

True positive rate, or TPR, measures the share of actual positive cases that a system correctly identifies. It is also called recall or sensitivity. The formula is TP / (TP + FN), where TP means true positives and FN means false negatives.

The arithmetic is simple. Choosing the right population, labels, threshold, and denominator is the difficult part. This guide works through an engineering example, distinguishes neighboring metrics, and explains what changes when the “test” is an A/B experiment rather than an item classifier.

Start with actual positives, not alerts

Define the positive class

“Positive” means the condition you want to detect. It does not necessarily mean a good outcome. In a defect detector, positive means a real defect. In a spam filter, it means spam. Write that definition before calculating anything.

A true positive is an item that is actually positive and predicted positive. A false negative is actually positive but predicted negative. Those two groups together form the denominator: all actual positives in the evaluation sample.

The recall definition is therefore conditional on actual class membership. TPR asks, “Among the real defects, what proportion did we catch?” It does not ask, “Among the alerts, what proportion were real?”

Fix the unit and observation window

Choose a consistent evaluation unit. A code change, an individual finding, and a repository are different units. If one change generates 12 duplicate alerts, counting alerts in the numerator and changes in the denominator produces a meaningless rate.

For the example, each unit is one code change, evaluated once by one fixed detector version at one fixed threshold. An independent review process eventually labels each change as defective or not defective. The observation window is long enough for those labels to mature.

This resembles the discipline needed when defining experiment metrics: the event, identity, time window, and denominator must describe the same question. A correct formula applied to incompatible counts still gives the wrong answer.

Calculate TPR from the confusion matrix

Put every evaluated item in one cell

Consider an original synthetic evaluation of 1,000 code changes. Reviewers establish that 100 contain a defect and 900 do not. The detector catches 80 defects, misses 20, and incorrectly flags 45 nondefective changes.

Actual label	Predicted positive	Predicted negative	Total
Defective	80 true positives	20 false negatives	100
Not defective	45 false positives	855 true negatives	900
Total	125	875	1,000

Read the labels rather than relying on cell position. Libraries and reports can arrange axes differently. The scikit-learn confusion matrix convention uses actual classes on rows and predicted classes on columns, with class order also affecting where each value appears.

Check the totals before calculating rates. The four cells sum to 1,000. True positives plus false negatives sum to 100 actual defects. Predicted positives total 125, which is a different denominator.

Divide detected positives by all actual positives

The calculation is:

TPR = TP / (TP + FN) = 80 / (80 + 20) = 80 / 100 = 0.80 = 80%.

Interpret it in words: the detector caught 80% of the actual defects in this evaluation sample. It missed 20%, so the false negative rate is 20%. For a binary task with complete labels, TPR and false negative rate sum to 100%.

Do not divide 80 by 1,000. That would measure true positives as a share of all evaluated changes, not recall. Do not divide 80 by 125 either. That is precision, which answers the alert-quality question.

The result describes this sample and threshold. It does not establish that every future workload will have the same recall, or that all defect categories are equally detectable. Keep the counts beside the percentage so readers can see the support behind it.

Handle zero positive support explicitly

If the sample contains no actual defects, TP + FN equals zero. Sample TPR is undefined. Returning 0% would imply the detector missed known defects; returning 100% would imply it successfully found them. Neither interpretation is supported.

Software libraries need a practical zero-division convention. That convention can return a placeholder or warning, but it does not create evidence. Report “TPR unavailable: zero actual positives” and preserve the support count. A pipeline can then distinguish an unevaluable slice from measured poor performance.

Check the experiment error risks

See how power, repeated checks, and multiple comparisons affect the reliability of experimental decisions beyond a single classifier score.

Read the False Positives Guide

Compare TPR with precision and false positives

Keep the denominators visible

For the same 1,000 changes, the other common metrics tell different stories:

Metric	Calculation	Result
True positive rate / recall	80 / 100 actual positives	80%
Precision	80 / 125 predicted positives	64%
False positive rate	45 / 900 actual negatives	5%
Specificity	855 / 900 actual negatives	95%
Accuracy	(80 + 855) / 1,000 changes	93.5%

The classification metric definitions differ because they condition on different populations. Here, 36% of alerts are false, but the false positive rate is 5%. Calling both numbers “the false positive rate” hides the operational distinction.

Accuracy can also look reassuring in an imbalanced population. A detector that labels all 1,000 changes nondefective would be 90% accurate while detecting none of the 100 defects. TPR exposes that failure, though it still needs the false-positive side of the picture.

Choose a threshold for the decision

Suppose a stricter threshold, evaluated on the same labeled changes, catches 60 defects and incorrectly flags 10 nondefective changes. Its TPR is 60%, its precision is about 85.7%, and its false positive rate is about 1.11%.

This threshold reduces the review queue from 125 changes to 70. It also misses 40 defects instead of 20. Whether that tradeoff is acceptable depends on the consequences of a missed defect, the review team's capacity, and what action follows an alert.

A ROC curve plots TPR against false positive rate across thresholds. It helps compare operating points. It does not pick the operational threshold for you, and an area-under-curve summary does not specify the queue size at the threshold you intend to deploy.

If you tune thresholds using the same labels you later report as a final evaluation, the score can be optimistic. Use separate validation and held-out evaluation data, or another defensible evaluation design, and freeze the decision rule before the final assessment.

Specify the action at each threshold too. A low-confidence finding might create a suggestion, while a high-confidence finding might block a merge. Those are different interventions with different error costs. One aggregate recall figure should not imply that every detected item received the same treatment.

Make sure the labels can support the claim

Audit predicted negatives too

If engineers review only alerts, you can estimate precision within the reviewed alert population. You cannot directly count missed defects among unreviewed negatives. Assuming those changes are clean makes FN artificially small and TPR artificially high.

An evaluation may need independent review of a representative sample of predicted negatives, delayed incident labels, or a curated benchmark with known defects. Each approach has limits. Incident labels miss undetected failures; curated examples can differ from ordinary production work.

If the evaluation oversamples suspicious changes or certain repositories, report that design. Use appropriate weighting when estimating performance for the real workload. A simple unweighted confusion matrix describes the sampled dataset, which may not represent the deployed population.

Preserve uncertainty and segment support

An 80% estimate based on 4 detected defects out of 5 is much less precise than one based on 800 out of 1,000. The important sample size for recall is the count of actual positives, not just the total number of changes evaluated.

Report positive support by important slices, such as language, defect category, or repository type. A high pooled TPR can hide weak performance on a rare but expensive failure mode. At the same time, avoid declaring tiny slices definitively better or worse from a few examples.

Counts alone do not make observations independent. Many similar changes from one repository can share a common pattern. Use uncertainty methods that fit the evaluation design rather than assuming every row is an unrelated trial.

Separate label delay from label absence

A recently deployed change might appear nondefective because nobody has had time to find the bug. Treating it as a confirmed negative gives the newest cohort a different labeling standard from older cohorts.

Define when an item becomes eligible for evaluation and track unresolved labels separately. Keep model version, threshold, label version, and observation dates with the result. That makes a later score change interpretable: you can tell whether the detector changed, the workload changed, or the labels matured.

For a warehouse-native measurement workflow, these definitions belong in the underlying data model. Joining model decisions to review outcomes still requires identity and time alignment; a queryable warehouse does not automatically resolve ambiguous ground truth.

Keep comparable populations together

When comparing detector versions, evaluate them on the same held-out cases where possible. Otherwise, an apparent recall improvement could come from an easier mix of defects. Preserve a breakdown of new, removed, and unchanged cases so reviewers can see what changed between evaluations.

When combining reports, add the underlying TP and FN counts for nonoverlapping, consistently defined populations, then calculate the pooled rate. An unweighted average of repository percentages answers a different question because it gives a tiny repository the same influence as a large one. Either summary can be useful, but label the weighting explicitly.

If the same change appears in several reports, deduplicate or model that repeated observation before pooling. Repeated scans do not create additional independent defects. Keep an audit trail from the final counts back to the evaluated item identifiers so a suspicious rate can be investigated.

Connect detection quality to product decisions

Distinguish classifier recall from statistical power

In hypothesis testing, statistical power is the probability that a testing procedure rejects the null when a specified alternative is true. It is a repeated-test detection probability, depending on assumptions such as effect size, variance, sample size, and decision rule.

That is related to the idea of detecting a real signal, but it is not the same dataset as a labeled-item confusion matrix. In an ordinary A/B program, you do not observe the true causal effect of every experiment with certainty. Dividing declared winners by all experiments does not reveal a ground-truth TPR.

Power planning asks how often your procedure would detect a particular real effect under its assumptions. A classifier evaluation asks how many labeled positives were detected in the evaluated sample. Keep those questions separate when discussing GrowthBook's statistical methods.

Evaluate the intervention as well as the detector

An improved offline detector can still create a worse product workflow. More alerts might overwhelm engineers, delay releases, or catch defects too late to matter. Conversely, a modest recall change might be valuable if it catches the failures with the highest operational cost.

When appropriate, use randomized experiments to evaluate the downstream intervention: which review experience helps teams resolve defects, with what delay and cost? Keep detector recall, review workload, and product outcomes as separate measures.

GrowthBook's experimentation platform can analyze defined outcomes from such tests. Your team supplies reliable assignment, exposure, labels, and metric definitions. Neither a high TPR nor a significant product result eliminates the need to inspect the other evidence.

Use a repeatable reporting checklist

Before sharing a TPR number, state the positive class, evaluation unit, detector version, threshold, and label process. Show TP and FN beside the rate. Include precision or false positive rate so readers can assess the workload created by detection.

Then ask whether predicted negatives were evaluated, whether labels had time to mature, and whether the sample reflects the population where you will act. Mark zero-support slices unavailable and explain material gaps in coverage.

The useful result is a statement someone can audit: “At this threshold, the detector found 80 of 100 labeled defects in these 1,000 evaluated changes, while producing 45 false alerts.” That is a clearer basis for a decision than “our model is 80% accurate.”

Measure what the change delivers

Connect your data and defined metrics to GrowthBook to evaluate how a product or workflow change affects the outcomes your team cares about.

Start Measuring With GrowthBook

Ready to ship faster?

No credit card required. Start with feature flags, experimentation, and product analytics—free.

Get Started

Book a Demo

Simplified white illustration of a right angle ruler or carpenter's square tool.

White checkmark symbol with a scattered pixelated effect around its edges on a transparent background.

Running statistical significance on an AI experiment the same way you'd run it on a button color test is one of the most common ways teams end up drawing confident conclusions from noise.

What statistical significance actually means (and why AI experiments make it harder)

The core definition: p-values, null hypotheses, and the 0.05 threshold

What traditional A/B tests assume about determinism

How AI outputs break the determinism assumption

What compounded variance means for sample sizes

Why AI outputs are noisier than traditional feature tests

Output stochasticity: the noise layer that doesn't exist in button tests

Delayed user outcomes and the learning curve problem

Metric attribution lag: when the outcome you care about happens later

How these three sources interact to inflate required sample sizes

Eval scores measure the model; these metrics measure whether users are better off

The hierarchy: downstream behavioral outcomes over model scores

Where AI metric design goes wrong

Variance reduction as a practical lever

P-hacking, peeking, and multiple metrics: the validity traps that undermine AI experiment results

Every metric you add compounds your false positive rate

P-hacking in AI prompt and model iteration

The peeking problem and sequential testing

Correction methods and the A/A baseline

Statistical significance is not enough: why practical significance matters more in AI tests

The scale problem: when statistical significance becomes automatic

Define your MDE before the experiment runs, not after

Where AI experiments break down: setup, execution, and interpretation

Lock in your metric and MDE before a single user is bucketed

Mid-experiment discipline: peeking, metric proliferation, and variance control

A significant result is not a mandate to ship

The highest-leverage move depends on where you are in the process

Related insights

Sign up for free

Table of Contents

Related Articles

CLI vs MCP: TLDR, it doesn’t matter as much as you think

Your agent should know how to do the job whichever interface it uses.

The debate combines three different questions

How can the agent reach the product?

What procedure should the agent follow?

What context makes the procedure relevant?

GrowthBook puts the durable parts below the interface

The API provides the operations

Skills provide the workflow guidance

MCP provides a thin bridge

Explore the shared flag workflows

The same disabled flag can use either route

Connect and verify before preparing the write

Resolve real IDs and construct one payload

Submit once, then read the object back

Choose the route that fits the runtime

Shell access favors terminal composition

Remote tool access favors MCP clients

Use a small decision table

Compare actual outcomes, not tool counts

Keep the evaluation task constant

Test failure behavior deliberately

Record the versions behind the result

Build workflows that survive the next client

Start with a common foundation

Standard deviation vs variance: Key differences for A/B testers

A metric can have wide user-to-user variation and still yield a precise experiment estimate.

Understand the difference in units

Variance uses squared distances

Standard deviation returns to the original scale

Calculate both from the same observations

Work through a small dataset

Choose sample or population formulas deliberately

Verify the calculation with explicit function names

Find the noise you can reduce

Use standard errors for experiment uncertainty

Distinguish users from estimated means

Combine arm variances before taking the square root

Avoid interpreting intervals as outcome ranges

Check what your metric actually measures

Match the variance to the randomization unit

Inspect tails instead of deleting them casually

Keep units consistent across pipelines

Turn spread into a better testing plan

Define the outcome before planning the sample

Reduce estimation noise without hiding behavior

Report the right quantity for the decision

Build a clearer experiment readout