Holdback Groups: Measure Your True Cumulative Impact

A holdback group is your product's long-term control, shielding a small set of users from all new features. Use it to measure the cumulative impact of many small changes over months or years, beyond what individual A/B tests can show.
Why it exists
A/B tests are great for measuring the immediate lift of a single change. But what about the combined effect of dozens of changes over a year? Summing up individual test wins is often misleading. A holdback group exists to measure the true, cumulative impact of all your product development efforts over a long period.
The mental model
Think of a holdback group as the ultimate control group for your entire product. A small, randomly selected slice of your users, perhaps 1%, is permanently shielded from all new features, UI tweaks, and optimizations. They are frozen in time on an older version of the product, providing a stable baseline to compare against.
How it works
First, you randomly assign a small percentage of users to the holdback group. This assignment is permanent. As you launch new features and run experiments for the 99% majority, the holdback group sees none of them. Over quarters or even years, you compare high-level business metrics like retention, lifetime value, and overall engagement between the main group and the holdback group. The difference is the net value your team has delivered.
When to use it
Holdbacks are for mature products with high experimentation velocity. They are powerful for justifying a team's overall impact to leadership and for diagnosing if a series of "winning" A/B tests are actually creating a worse, more complex user experience.
When not to use it
Don't use this for early-stage products; you don't have the user volume or time. It's also a poor fit if you can't commit to the engineering discipline required to maintain the group's isolation. There can also be support and fairness issues with denying users access to valuable new functionality for long periods.
One canonical example
An e-commerce platform ships 50 "winning" A/B tests in a year, each with an average 0.5% lift in conversion. Naively, they expect a cumulative lift of over 25%. However, their 1% holdback group shows that the main user base's conversion is only 4% higher after one year. This reveals that the initial lifts were driven by novelty or that the changes had negative interaction effects, providing a much more sober view of their true impact.
Interview question
What is the primary purpose of implementing a holdback group in product development?
- a.To quickly validate the immediate performance of a newly launched feature.
- b.To identify the specific user segment most receptive to new product changes.
- c.To ensure all users consistently experience the most up-to-date version of the product.
- d.To measure the true, long-term cumulative impact of all product changes over time.Correct
Why? this is the answer
A holdback group is specifically designed to measure the true, net cumulative impact of all product changes over an extended period, which individual A/B tests cannot accurately capture. Option A describes the function of a standard A/B test, which focuses on immediate, isolated changes.
Just read this? Test yourself on what you have been reading.
Read the original → cxl.com
- #experimentation
- #a/b testing
- #product analytics
- #growth
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on experimentation — each one lists the topics its interview covers.
See open roles