Experiments

Data Science

Why your AI model performs great offline but fails in production

Jun 3, 2026

min read

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

Your model scored well on every benchmark.

Then you shipped it, and users started complaining within days. The instinct is to blame the model — retrain it, tune it, collect more data. But the model usually isn't the problem. The evaluation was. Offline benchmarks measure how well a model learned a frozen slice of historical data. They say almost nothing about how that model will behave when real users, real infrastructure, and a constantly shifting input distribution enter the picture.

This article is for engineers, PMs, and data teams who are shipping AI features and want to understand why offline model evaluation production failure is so common — and what to do about it. Whether you're building a recommender system, a chatbot, or an agentic pipeline, the same structural gaps apply. Here's what you'll learn:

Why offline benchmarks are a poor proxy for real-world performance, and where the false confidence comes from
How data drift and distribution shift silently break models that passed every pre-deployment check
Why standard metrics like accuracy, F1, and BLEU often don't map to what users actually experience
How hidden product constraints — latency, integration failures, and unexpected user behavior — cause failures that benchmarks will never catch
How to sequence offline and online evaluation into a staged pipeline that catches each class of failure at the right cost and risk level

The article moves from diagnosis to architecture. The first sections explain why the gap between benchmark performance and real user behavior exists. The final section gives you a concrete model for closing it — using golden query sets, canary rollouts, production monitoring, and feedback loops that keep your evaluation sets from going stale.

Why offline benchmarks are a poor proxy for real-world performance

If your model's evaluation metrics look solid but users are still complaining, the instinct is to blame the model. Retrain it, tune it, collect more data. But before you do any of that, it's worth asking a harder question: are your benchmarks actually measuring what matters in production?

In most cases, the problem isn't that the model is bad — it's that the evaluation was never designed to predict how the model would behave with real users in a live environment. That's a fundamentally different problem, and it requires a different fix.

Offline evaluation answers a useful question — just not the right one

Offline evaluation scores a model against a fixed, labeled dataset using a defined scoring method. It answers a specific question: how well did this model learn this historical data? That's a useful question for catching regressions, comparing model versions, and validating that a training run didn't degrade known capabilities. It's repeatable, fast, and easy to operationalize — which is exactly why it became the default starting point for most ML projects.

But repeatability isn't the same as validity. A benchmark can score a model perfectly on historical inputs while being completely silent about whether those inputs still represent what users send today. The score is frozen at the moment the dataset was collected. Production isn't.

The structural limitations of static datasets

Fixed datasets are historical artifacts. They capture the distribution of inputs and interactions that existed when the data was collected, which means they structurally cannot represent behaviors that have since evolved, inputs that didn't exist at collection time, or the full long tail of real production traffic.

This problem compounds when teams skip chronological splitting of their hold-out sets. Evaluating a model on randomly sampled historical data — rather than data that comes after the training window — introduces time-based leakage that makes offline metrics look more predictive than they are. As Shaped.ai puts it directly: "predicting a hold-out set of interactions is not the same as predicting what your users will actually interact with." The dataset is an approximation of production, and approximations have expiration dates.

How edge cases get systematically excluded

Offline datasets are built from observed, logged interactions. That means rare inputs, novel query patterns, and adversarial edge cases are structurally underrepresented — not because anyone made a bad decision, but because low-frequency events don't accumulate enough signal to make it into training or evaluation data in meaningful quantities.

The consequence is a model that achieves strong precision and recall on a benchmark while being completely unprepared for the long tail of real user behavior. The failures that matter most in production — the ones that generate support tickets, erode trust, or cause users to abandon a feature — are often exactly the inputs that never appeared in the evaluation set.

Strong benchmark scores can mask new failure modes in production

This is where the structural limitations of offline evaluation become genuinely dangerous. A model that scores better on a benchmark may still introduce new failure modes in production, particularly when the deployment environment is noisy, user inputs have shifted, or the evaluation is measuring proxy metrics that don't map to actual user outcomes. Label Studio states this plainly: "A model can look improved offline and still cause new issues in real usage."

The problem is especially acute for tasks involving subjective qualities — tone, helpfulness, policy adherence, response appropriateness. Offline evaluation struggles with these unless a purpose-built rubric has been designed with labels that reliably capture those qualities. Most teams haven't built that rubric. They're relying on accuracy or F1 scores that were never designed to answer whether users find the model's output useful or trustworthy.

The result is a false confidence loop: metrics look good, the team ships, and the first real signal that something is wrong comes from user behavior — not from the evaluation suite. That's not a model quality problem. It's an evaluation design problem, and recognizing the distinction is the first step toward building a system that can actually catch what benchmarks miss.

A concrete version of this plays out in content moderation systems. A classifier trained on historical violation examples may achieve 94% accuracy on a held-out test set — and still miss an entire emerging category of policy violations that didn't exist when the training data was collected. The benchmark score is real. The safety gap is also real. Neither fact cancels the other.

Data drift and distribution shift: how production inputs break offline assumptions

Every offline evaluation set is a snapshot. It captures a slice of the input distribution that existed at a particular point in time, reflects the user behaviors and edge cases that were observable when the data was collected, and encodes assumptions about what "normal" inputs look like. The moment production traffic diverges from that snapshot — and it will — the evaluation set stops measuring what you think it's measuring.

Models that cleared every pre-deployment check begin failing on inputs they were never tested against, and nothing in your monitoring stack throws an error. Predictions simply become progressively less reliable. This isn't a quality lapse. It's a structural property of deploying ML systems into a non-stationary world.

Covariate shift vs. concept drift: two distinct failure modes

The first failure mode — often called data drift or covariate shift — is the simpler one to grasp: the inputs your model sees in production start to look different from the inputs it was trained on. The model's internal logic hasn't changed. But the data flowing through it has.

Concept drift is different and more dangerous. Here, the input distribution may look stable, but what "correct" means has changed. A fraud detection model trained on 2023 transaction patterns may encounter structurally familiar inputs in 2025 — but the ground truth of what constitutes fraud has shifted as attack patterns evolved. The model's predictions are confident and wrong. The inputs looked normal. The labels didn't.

The operational consequence of this distinction is significant. Covariate shift can often be detected without ground truth labels — by monitoring input statistics, running statistical hypothesis tests, or measuring distance metrics between training and production distributions. Concept drift frequently cannot be detected until ground truth labels arrive, which in many systems means waiting days, weeks, or longer. That lag is where silent degradation lives.

The long tail of unexpected production inputs

Offline evaluation sets, however carefully constructed, represent a finite sample of a non-stationary distribution. Production traffic doesn't respect that boundary. It includes new device types, new geographies, edge-case phrasing, emerging behavioral patterns, and user populations the evaluation set never anticipated.

Consider a credit risk model trained primarily on salaried employees that gets applied to a growing segment of gig workers, whose income volatility and spending patterns differ structurally. Or a recommendation model trained on pre-pandemic behavior that suddenly encounters shifted inventory and interaction patterns. In both cases, the model receives inputs that fall outside its training distribution and returns predictions that are technically confident but structurally unreliable. As Chalk.ai describes it: "The result is silent degradation — a widening gap between what the model expects and what it actually receives."

It's worth noting a practitioner nuance here: detecting input distribution shift doesn't guarantee that model performance has degraded. A model may experience measurable covariate shift and still generalize adequately if the new inputs fall within its learned range. Drift detection is a necessary early warning signal, not a definitive performance verdict. The Evidently AI framing is precise on this point: when ground truth labels aren't accessible, drift monitoring serves as a proxy signal to assess whether the model is operating under familiar conditions — not a direct measure of accuracy.

How quickly evaluation sets go stale

The practical implication is that evaluation sets should be treated as perishable artifacts, not permanent benchmarks. The inputs your model sees today are not the same as they were six months ago. External events — a shift in user demographics, a change in upstream data pipelines, a macroeconomic disruption — can invalidate an evaluation set almost overnight.

Teams that evaluate once at deployment and never refresh are measuring their model against a world that no longer exists. The evaluation isn't wrong; it's expired.

Why production monitoring must close the feedback loop

Without active monitoring, drift-induced failures surface through lagging indicators: user complaints, support tickets, and business metric drops. One social platform with 150 million monthly active users, cited in an UpTrain product launch discussion, described exactly this pattern — discovering model issues through customer complaints and increased churn rather than through proactive observability. By the time the signal reached the team, the degradation had already affected users at scale.

Closing this loop requires connecting production inputs to downstream outcomes in near real-time. Gradual rollouts — exposing new model versions to a small user segment before full deployment — give teams an early window to observe whether production inputs match offline assumptions before the blast radius widens. Warehouse-native experiment analysis, which links model behavior directly to user outcomes without duplicating data pipelines, is the infrastructure layer that makes this feedback loop actionable rather than theoretical.

The core insight is this: offline evaluation tells you how a model performs on a past distribution. Production monitoring tells you how it performs on the present one. Neither is optional.

Measuring the wrong things: when offline metrics don't map to user outcomes

A model can pass every benchmark you throw at it and still ship a product that users find frustrating, unhelpful, or just wrong. The problem isn't always the model. Often, it's the measurement framework — and metric selection turns out to be just as consequential as model selection.

This is Goodhart's Law applied to AI evaluation: when a metric becomes a target, it stops being a good measure of the underlying goal. Teams optimize relentlessly for accuracy, F1, BLEU, NDCG, and precision — and end up with systems that score well on paper while failing the people who actually use them.

Precision and recall don't tell you whether users completed their task

Standard offline metrics measure prediction accuracy against historical data. That's a useful signal, but it's a fundamentally different question than whether users will find the output valuable.

Precision and recall tell you how well a model recovered relevant items from a fixed dataset. NDCG tells you how well it ranked them. None of these metrics tell you whether a user completed their task, returned the next day, or found the response trustworthy. Even qualitative offline evaluation — examining the distribution and diversity of recommendations — is still bounded by what's in the historical record. It can't surface what users needed that the dataset never captured.

The gap widens the further a system's outputs are from simple classification. For recommender systems, the mismatch is significant. For generative systems, it becomes structural.

Why standard NLP metrics break down for generative and agentic systems

BLEU scores were designed to evaluate machine translation by comparing candidate outputs against reference translations. That framing assumes there's a correct answer — a fixed target to measure against. For a chatbot, a coding agent, or a summarization system, that assumption collapses. There's no single correct response, and counting how many word sequences the output shares with a reference answer tells you almost nothing about whether the output was actually useful.

This isn't a niche concern. The Hacker News community discussion around AI evaluation tooling (a thread on hamel.dev with nearly 200 points) reflects a practitioner consensus that evaluating non-binary outputs remains an active, unsolved problem. Teams are actively debating tools like Opik, Braintrust, Promptfoo, and Laminar not because they've solved the problem but because standard frameworks don't handle it. The specific tools matter less than the pattern they reveal: practitioners are actively investing in evaluation infrastructure precisely because no standard framework has solved it.

One commenter noted that even purpose-built eval tools broke down once evaluation complexity increased beyond a certain threshold; another flagged that instrumenting the right signals — even something as foundational as capturing structured request traces for automated evaluation — requires real engineering investment. The tooling is maturing, but the underlying measurement problem hasn't been resolved by any of it.

Helpfulness and tone resist measurement without a purpose-built rubric

The failure mode gets worse for the qualities users actually care about most. Helpfulness, tone, policy adherence, factual grounding — these are the dimensions that determine whether a user trusts a system or abandons it. They're also the hardest to capture in a static labeled dataset.

Label Studio frames this clearly: "Offline evaluation also struggles with metrics that require subjective judgment (tone, helpfulness, policy adherence) unless you've designed a rubric and labels that capture those qualities reliably." The operative phrase is "unless you've designed a rubric." Most teams skip this step — not because they don't recognize its importance, but because it's genuinely difficult and there's no off-the-shelf answer. The absence of a rubric is itself a metric design failure, and it tends to be invisible until users start complaining.

Reorienting evaluation around what users actually experience

The prescriptive answer is to reorient evaluation around what users actually experience — and to measure multiple outcomes simultaneously rather than optimizing a single proxy.

GrowthBook's Metric Correlations feature illustrates why single-metric optimization fails in practice. The documented example is instructive: an experiment increases total user revenue while simultaneously decreasing user retention. Optimizing for revenue alone would flag the experiment as a success. Tracking both metrics together surfaces a potential dark pattern — "where your experiments are driving purchasing behavior but somehow also making the product worse." The same dynamic applies to model evaluation: a change that improves BLEU score might degrade user satisfaction; a change that increases click-through might reduce task completion.

The teams that get this right tend to reframe evaluation from model-centric to user-perspective-centric. Landon Smith, Head of Post-Training at Character.AI, describes the shift this way: "We can compare different modeling techniques from the perspective of our users — guiding our research in the direction that best serves our product." That framing — techniques evaluated from the user's perspective, not the model's — is the practical answer to the wrong-metrics problem. It doesn't eliminate offline evaluation; it changes what offline evaluation is trying to confirm.

Hidden product constraints: how UX context and integration failures cause silent production failures

A model can pass every benchmark you've designed, clear your evaluation suite, and still fail your users within hours of deployment. Not because the model is wrong, but because the product context surrounding it was never part of the evaluation. This is one of the most frustrating categories of offline model evaluation production failure precisely because it doesn't look like a model problem — it looks like a bug, a slowness, a weird edge case — until you realize the model was never tested as part of a system.

Integration failures that only appear under real traffic

When you evaluate a model offline, you're evaluating it in isolation. You feed it inputs, collect outputs, score them. What you're not testing is what happens when those outputs flow into a downstream API that has its own timeout behavior, or get passed to an orchestration layer that expects a specific response format, or hit a rendering pipeline that breaks when the response exceeds a certain length.

Markus Kuehnle, writing about production AI failures, puts it plainly: "When an agent breaks in production, debugging through deep layers of framework abstraction is a nightmare." The failure isn't in the model — it's in the integration. And because offline benchmarks evaluate the model in isolation, these failure modes are completely invisible until real traffic exposes them.

Consider a concrete example: a model returns a technically correct response, but that response is 1,400 characters and the UI component rendering it was built to handle 800. The component breaks. From the user's perspective, the feature is broken. From the benchmark's perspective, the model scored perfectly.

Latency and infrastructure constraints as hidden performance factors

Accuracy metrics say nothing about time. A model that answers correctly in four seconds may be functionally useless in a product where users expect a sub-second response — and the users who experience that delay won't file a bug report. As Product School's analysis notes, "a model that's '95% accurate' can still fail your users if it's too slow." They'll just stop using the feature.

This matters because latency is not a model property in isolation — it's a system property. It depends on infrastructure load, concurrent users, network conditions, and token generation costs under real traffic patterns. Kuehnle specifically identifies the absence of visibility into "real-time latency, token cost, and exact output traces" as a core infrastructure blind spot, not a model evaluation problem. No static dataset can simulate what happens to your p95 latency when your user base doubles on a Tuesday afternoon.

User interaction patterns that static datasets cannot simulate

Real users don't interact with AI features the way evaluation datasets assume. They interrupt mid-response, rephrase the same question three times in a row, chain queries in unexpected sequences, and behave differently on mobile than on desktop. Label Studio's analysis of offline evaluation limitations notes that static datasets "omit new user behaviors" and that models can cause "new issues in real usage, especially if the deployment environment is noisy or user inputs change over time."

The compounding problem is that these failures are underreported. Most users won't submit feedback when a feature behaves strangely — they'll simply abandon it. That abandonment signal only surfaces in engagement metrics, not in model evaluation scores, which means integration-pattern failures can persist invisibly for weeks before anyone connects the drop in retention to the model deployment that preceded it.

Trace monitoring as the fix for integration-layer blind spots

Since these failures don't appear in benchmarks, better benchmarks aren't the answer. Observability is. Kuehnle's recommended architecture is specific: implement comprehensive trace monitoring using tools like Opik or MLflow to log exactly what is happening for every request — inputs, outputs, latency, token costs, and the full execution path through any orchestration layer. "You cannot fix what you cannot see" is his framing, and it applies precisely here.

One practical technique that bridges monitoring to deployment control: placing a feature flag with attribute-based targeting in front of model outputs to activate detailed logging selectively for a specific user segment, without instrumenting every request in production at full cost. This pattern — using feature flags for targeted observability — is what feature flag rollout infrastructure enables, and it's what practitioners like Steven Eberling recommend as a first-line telemetry strategy. When a latency spike or rendering failure appears in a specific segment, you can trace it, isolate it, and roll back without a full production incident.

The systems-thinking shift here is straightforward but consequential: stop treating model evaluation and product evaluation as the same thing. They measure different failure modes, and only one of them tells you what your users are actually experiencing.

Staging offline and online evaluation so each layer catches what the previous one cannot

The previous sections of this article have made a case for why offline evaluation is structurally incomplete — it can't anticipate distribution shift, it optimizes for proxy metrics that don't track user outcomes, and it has no visibility into the integration failures that only appear under real traffic. But the answer isn't to abandon offline evaluation. It's to stop treating it as the final word and instead embed it within a staged architecture where each layer catches a different class of failure at the appropriate cost and risk level.

The CMU Software Engineering Institute has framed this plainly: providing performance guarantees for AI systems in real-world settings "remains a challenge" due to the complexity of deployed environments and the tasks systems are designed to complete. No single evaluation stage resolves that complexity. What a staged pipeline does is distribute the risk — catching cheap-to-find regressions early and reserving real-user exposure for the failures that only live traffic can surface.

Moving from controlled to real in deliberate, risk-reducing steps

The logic of a multi-stage pipeline follows a simple principle: move from controlled to real, and from cheap to expensive, in deliberate steps. Offline testing catches regressions against known inputs before any code ships. Staging validates that the model behaves correctly when integrated with real infrastructure — APIs, rendering layers, latency budgets — under simulated conditions. Canary rollouts expose a small slice of real users to the new model version, generating live signal without full production blast radius. Full rollout follows only after guardrails at each prior stage have passed.

Each stage is catching something the previous stage cannot. Offline tests won't tell you that your model's output breaks the UI renderer at a certain token length. Staging won't tell you that your model degrades for users in a specific geography with different query patterns. Canary will. The pipeline is a risk-reduction architecture, not a deployment checklist.

Golden query sets and CI/CD guardrails

At the offline layer, the most durable investment a team can make is a curated set of representative inputs — often called golden query sets — that function as regression tests for every model update. These aren't random samples; they're deliberately selected to cover the failure modes you've already discovered, the edge cases your users actually encounter, and the high-stakes interactions where degradation is unacceptable. When a model change degrades performance on these inputs, deployment is blocked automatically through CI/CD integration. This turns offline evaluation from a manual review step into an automated gate that runs on every commit.

The value compounds over time. As production monitoring surfaces new failure modes, those inputs get added to the golden set, making the offline layer progressively more representative of real conditions.

Canary rollouts and segment targeting

When a model passes offline guardrails, the next question is which users see it first. Canary deployments work best when the initial cohort is chosen deliberately — power users who generate high query volume, internal users who can provide structured feedback, or segments whose behavioral patterns are well-understood. This is where gradual rollout infrastructure becomes operationally relevant: incremental exposure using engagement data, combined with precise segment selection before broad release. If a canary reveals unexpected failures, instant deactivation rolls back the feature without disrupting the broader user base.

Landon Smith, Head of Post-Training at Character.AI, describes this approach directly: "GrowthBook has been an invaluable tool for Character.AI, helping us develop our models into a great consumer experience. We can compare different modeling techniques from the perspective of our users — guiding our research in the direction that best serves our product."

Production behavior must feed back into offline evaluation or the pipeline stalls

The staged pipeline only works if production behavior feeds back into offline evaluation. Traces, user interaction signals, and outcome metrics collected in production are the raw material for keeping evaluation sets current — without this feedback loop, golden query sets go stale and the offline layer drifts out of sync with reality, recreating the original problem.

Warehouse-native experiment analysis — where outcome measurement runs directly against the data warehouse the business already trusts, without a separate instrumentation layer — makes this feedback loop practical. It means the same outcome data that informs business decisions is also informing model evaluation, and teams aren't maintaining two parallel measurement systems. The result is an evaluation pipeline where offline and online stages reinforce each other rather than operating in isolation, and where each production deployment makes the next offline evaluation slightly more representative of the world the model will actually face.

From offline model evaluation to production confidence: where to start

The through-line of this article is simple: offline evaluation isn't broken — it's just incomplete. It was never designed to catch distribution shift, integration failures, or the gap between proxy metrics and what users actually experience. The teams that get burned aren't doing evaluation wrong. They're treating one layer of a multi-stage problem as if it were the whole thing.

The fix isn't a better benchmark. It's a pipeline where each stage catches what the previous one structurally cannot — and where production behavior feeds back into offline evaluation so your golden query sets don't quietly expire.

Audit your current evaluation stack for the failures it structurally cannot see

Before adding anything new, it's worth being honest about what your current evaluation actually measures. If your hold-out set isn't chronologically split, your offline metrics are optimistic by design. If your evaluation metrics are accuracy or F1 and your system produces generative or ranked outputs, you're measuring the wrong thing entirely. The most useful audit question isn't "are our scores good?" — it's "what class of failure would our current evaluation completely miss?"

The minimum viable production evaluation pipeline for AI teams

You don't need to build everything at once. The highest-leverage starting point is a small, curated golden query set wired into CI/CD, combined with a canary rollout that exposes a deliberate first cohort — internal users, power users, or a well-understood segment — before broader release. That combination catches regressions before deployment and surfaces real-traffic failures before they reach everyone.

As a concrete starting point: a search relevance team might build a golden set of 50 queries representing their highest-traffic intent categories, wire it into CI/CD to block any model update that drops NDCG below a threshold on those inputs, and configure a canary to expose the first 5% of traffic to internal users before broader rollout. That's not a complete evaluation system — but it's a working one, and it catches the two most common failure modes (regressions on known inputs, integration failures under real traffic) before they reach the full user base.

The feedback loop comes next: when production monitoring surfaces a new failure mode, that input belongs in your golden set. The pipeline improves itself over time if you build it that way from the start.

Observability and deployment control are distinct layers that must work together

Trace monitoring — logging inputs, outputs, latency, and token costs for every request — is the observability layer that makes integration failures visible. Feature flag rollout infrastructure gives you the deployment layer: the ability to target a canary cohort precisely using percentage-based rollouts with deterministic hashing, measure outcomes against the same warehouse data your business already trusts, and roll back instantly if something goes wrong. Platforms that unify these two capabilities — deployment control and outcome measurement — eliminate the instrumentation overhead of maintaining separate systems for each.

These aren't separate concerns. Observability tells you what's happening; deployment control determines who it happens to and when. This article is meant to be genuinely useful — not just as a diagnosis of why production failures happen, but as a practical starting point for building evaluation infrastructure that actually keeps pace with a live product.

What to do next: Start with the audit. Pull up your current evaluation setup and ask one specific question: is your hold-out set chronologically split, or randomly sampled? If it's randomly sampled, your offline metrics are likely more optimistic than they should be — fix that first, before adding any new tooling. If your evaluation is already chronologically sound, the next question is whether your metrics map to user outcomes or just model accuracy. Pick the gap that's closest to your current deployment risk, and close that one first.

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.

Your model scored well on every benchmark.

Why offline benchmarks are a poor proxy for real-world performance

Offline evaluation answers a useful question — just not the right one

The structural limitations of static datasets

How edge cases get systematically excluded

Strong benchmark scores can mask new failure modes in production

Data drift and distribution shift: how production inputs break offline assumptions

Covariate shift vs. concept drift: two distinct failure modes

The long tail of unexpected production inputs

How quickly evaluation sets go stale

Why production monitoring must close the feedback loop

Measuring the wrong things: when offline metrics don't map to user outcomes

Precision and recall don't tell you whether users completed their task

Why standard NLP metrics break down for generative and agentic systems

Helpfulness and tone resist measurement without a purpose-built rubric

Reorienting evaluation around what users actually experience

Hidden product constraints: how UX context and integration failures cause silent production failures

Integration failures that only appear under real traffic

Latency and infrastructure constraints as hidden performance factors

User interaction patterns that static datasets cannot simulate

Trace monitoring as the fix for integration-layer blind spots

Staging offline and online evaluation so each layer catches what the previous one cannot

Moving from controlled to real in deliberate, risk-reducing steps

Golden query sets and CI/CD guardrails

Canary rollouts and segment targeting

Production behavior must feed back into offline evaluation or the pipeline stalls

From offline model evaluation to production confidence: where to start

Audit your current evaluation stack for the failures it structurally cannot see

The minimum viable production evaluation pipeline for AI teams

Observability and deployment control are distinct layers that must work together

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