Skip to content
Confidence
  • Documentation
  • Blog
  • Bootcamp
  • Status
  • Confidence Bootcamp
    • My learning
    • Intro to experimentation
      • Introduction
      • Lesson 1: Why you should experiment
      • Lesson 2: Experiment hypothesis
      • Lesson 3: Success and guardrail metrics
      • Lesson 4: Success metrics
      • Lesson 5: Set up your experiment
      • Lesson 6: Calculation frequency
      • Lesson 7: Target audience
      • Lesson 8: Sample size
      • Lesson 9: Quality assurance
      • Lesson 10: Run your experiment
      • Lesson 11: Evaluate your experiment and make a decision
      • Lesson 12: A/B tests and rollouts
      • Course wrap up
    • Intro to metrics
      • Introduction
      • Lesson 1: What is a metric?
      • Lesson 2: Metric roles
      • Lesson 3: Time considerations
      • Lesson 4: Capturing behavior
      • Lesson 5: Strategic metrics
      • Lesson 6: Interpretability
      • Lesson 7: Feasibility and sensitivity
      • Lesson 8: Variance reduction and metric selection
      • Lesson 9: Select metrics
      • Lesson 10: Segment-level analysis
      • Course wrap up
    • Scientific product development
      • Introduction
      • Lesson 1: Why you should experiment
      • Lesson 2: The scientific method
      • Lesson 3: Randomized controlled trials
      • Lesson 4: Experiment hypothesis
      • Lesson 5: Case study
        • Case study
        • Answers to case study
      • Lesson 6: Why do we need statistics?
      • Lesson 7: Success metrics
      • Lesson 8: Detectable effects and sample size
      • Lesson 9: Make a decision
      • Course wrap up
    • A primer on hypothesis testing
      • Introduction
      • Lesson 1: Introduction to hypothesis testing
      • Lesson 2: True vs estimated effects
      • Lesson 3: Sampling distribution of the difference-in-means estimator
      • Lesson 4: Z-tests and how to reject the null hypothesis
      • Lesson 5: False postive rate and alpha
      • Lesson 6: True positive rate, MDE, and power
      • Course wrap up
    • Intro to Feature Flags
      • Introduction
      • Lesson 1: What is a feature flag?
      • Lesson 2: Lifecycle of a feature flag
      • Lesson 3: Clients
      • Lesson 4: Evaluation context and targeting
    • Sample size calculation - I
      • Introduction
      • Lesson 1: What is the required sample size?
      • Lesson 2: Alpha and power
      • Lesson 3: Baseline mean and variance
      • Lesson 4: Sample size playground - I
    • Sample size calculation - II
      • Introduction
      • Lesson 1: Multi-metric decision making
      • Lesson 2: Number of success metrics
      • Lesson 3: Number of guardrail metrics
      • Lesson 4: Number of comparisons
      • Lesson 5: Sample size playground - II
    • Sample size calculation - III
      • Introduction
      • Lesson 1: Binary metrics
      • Lesson 2: Treatment group proportions
      • Lesson 3: Variance reduction
      • Lesson 4: Sequential testing and sample size
      • Lesson 5: Sample size playground - III
    • Advance your experimentation
      • Introduction
      • Lesson 1: Guardrail metrics with non-inferiority margins
      • Lesson 2: Choose evaluation frequency
      • Lesson 3: Metrics' roles in experiments
      • Lesson 4: Cumulative holdback evaluations
    • Experimentation culture
      • Introduction
      • Lesson 1: Onboarding into experimentation
      • Lesson 2: Empowering experimentation champions
      • Lesson 3: Sustaining the experimentation culture
    • Videos

Lesson 6: Guardrail metrics and NIMs

Summary

In this lesson, you learn what guardrail metrics are and how to read their status labels. You see how adding a non-inferiority margin (NIM) changes what the labels mean, and why a NIM gives you stronger evidence of safety than no NIM.

Guardrail metrics are not the ones you are trying to improve. They are the ones you want to make sure you do not damage. Examples: session length, error rate, revenue per user. The question for a guardrail is not "did this go up?" but "did this go in the wrong direction?"

Because the question is different from a success metric, the status labels are different.

Without a NIM

The CI for a guardrail metric sits on the same axis as for a success metric. The zero line is still the reference. But the question is now about the harmful direction, not the positive direction.

For a metric where increases are harmful (such as time in checkout, error rate, or support contacts):

  • Has deteriorated: the CI is entirely on the wrong side of zero, in relation to the improvement-direction of the metric. There is statistical evidence the metric moved in the harmful direction. This is a serious signal.
  • Has not deteriorated: the CI crosses zero. No statistical evidence of movement in the wrong direction. The guardrail is holding.

Use the interactive below with the "No NIM" checkbox checked to explore these labels.

CI and status for guardrail metrics

Adjust the point estimate to see how the status changes. Use the direction toggle and NIM to explore different configurations.

Metric improves when it:
-20%-10%0%+10%+20%
+4.2%
Has not deteriorated
-15%+15%
10010,000
10 (low noise)100 (high noise)
1%15%
Has not deteriorated: With high confidence, the true effect is between -1.5% and +9.9%. Since zero is in the interval, there is no statistical evidence of harm to this metric.
The result for this metric is in line with recommending to ship!

Try the following with "No NIM" checked:

  • With the direction set to "Decreases" (harmful = increase), drag the point estimate from +15% to -15% and watch both states: "Has deteriorated" when the CI sits entirely above zero, and "Has not deteriorated" when the CI crosses zero.
  • Move it to +3% and reduce the sample size to 200. The wide CI crosses zero: "Has not deteriorated."
  • Move the point estimate above +5% with a small sample size. The CI may sit entirely above zero: "Has deteriorated."

What a NIM is

A non-inferiority margin (NIM) defines how much deterioration is acceptable. Rather than asking "did this metric move at all?", a NIM lets you say "we accept up to X% increase: anything within that tolerance is acceptable."

Adding a NIM changes the question from "did this harm?" to "did this stay within bounds?"

In Confidence

In Confidence, the NIM appears as a solid vertical line on the results page, with an arrow pointing toward the safe zone. Whether a metric is non-inferior or possibly inferior is determined by the CI's position relative to the NIM line. Has deteriorated still uses the zero line as its threshold.

With a NIM

  • Non-inferior: the CI is entirely within the NIM boundary. This is positive evidence of safety: even the worst-case bound is within the acceptable tolerance.
  • Possibly inferior: the CI crosses the NIM boundary. Not enough evidence to confirm the metric stayed within the tolerance.
  • Has deteriorated: the CI is entirely on the wrong side of zero, in relation to the improvement-direction of the metric. Statistical evidence that the metric moved in the harmful direction, same threshold as without a NIM.

If a metric is possibly inferior, you can still interpret the CI the usual way: with high confidence, the true effect is somewhere between the lower and upper bound. That means you can use the CI to assess the worst case. Look at the bound in the harmful direction—the upper bound for a metric where increases are harmful, or the lower bound for a metric where decreases are harmful. That bound tells you how bad the effect could plausibly be, even if you cannot yet rule out that the metric stayed within the NIM.

To explore the with-NIM states, clear "No NIM" in the interactive above and try the following:

  • With the direction set to "Decreases" (harmful = increase), drag the point estimate from +15% to -15% and watch all three states appear in sequence: "Has deteriorated" when the CI is entirely above zero, "Possibly inferior" as the CI crosses the NIM boundary, and "Non-inferior" when the entire CI is within the acceptable range.
  • Set the point estimate near 0%. The CI sits well below the NIM: "Non-inferior."
  • Move the point estimate toward the NIM value. The CI starts to cross the NIM line: "Possibly inferior."
  • Move the point estimate well above the NIM. The whole CI is above zero: "Has deteriorated."

The key difference

Note

Without a NIM, "Has not deteriorated" tells you only that you could not detect harm: absence of evidence, not evidence of absence. With a NIM, "Non-inferior" is positive evidence of safety. The CI is entirely within the acceptable range, so even the most pessimistic estimate is acceptable. The second approach is more rigorous when safety matters.

Reader exercise

A guardrail metric where increases are harmful has a NIM of 5%. The CI shows [+0.8%, +3.4%]. What is the status?

Reader exercise

A guardrail metric where increases are harmful has no NIM. The CI shows [+0.9%, +11.2%]. What is the status?

Reader exercise

Why is 'Non-inferior' a stronger result than 'Has not deteriorated' for a guardrail metric?

Notes for nerds

The distinction between "Has not deteriorated" and "Non-inferior" maps onto a broader framework for thinking about what level of evidence an experiment actually needs to provide. Rather than treating every experiment as requiring the same strength of evidence, you can think of experimentation as a ladder of risk mitigation: each rung offers progressively stronger statistical guarantees, but also requires more data to reach. Using guardrail metrics without NIMs sits at a lower rung: you are ruling out obvious harm, but not positively bounding how bad things could be. Adding a NIM moves you up the ladder: you are now producing positive evidence of safety within an acceptable tolerance.

This framing has practical implications for how you design experiments when sample sizes are limited. The Confidence blog post on experimenting with smaller samples develops this idea in full.

Was this page helpful?

PreviousLesson 5: Significance for success metrics
NextLesson 7: Health checks and the SRM

© Copyright 2026. All rights reserved.

Follow us on XFollow us on GitHub

On this page

  1. Without a NIM

  2. What a NIM is

  3. With a NIM

  4. The key difference

  5. Notes for nerds