Statistics, experimentation, causal reasoning · insight-1009
Keep a long-term holdback to measure what a year of shipped wins really added
- Evidence type
- practitioner heuristic
- Difficulty
- medium
- Roles
- Data scientist, Data analyst
- Industries
- e-commerce, saas, aviation
Summary: situation, action, reason, boundary
Situation
A quarterly deck sums the lifts of 14 individually significant experiments and claims +9%, while the dashboard moved +2%.
Action
Hold a small random slice of users (a few percent) on the old experience for the whole period and compare it with everyone else at the end. Report that delta as the cumulative effect and the sum of launch estimates only as an ex-ante figure.
Reason
Significant estimates from noisy tests tend to exaggerate effects, and stacked changes interact; only a concurrent randomised comparison of old versus new product is unbiased.
Boundary
Mature products with a steady stream of incremental experiments.
Symptom or risk
Launch-time estimates are inflated by selection, overlap the same improvement, fade after novelty and interact, so the sum does not reproduce.
Exceptions
Changes that cannot coexist with the old version for engineering or legal reasons.
Trade-offs
Holdback users get an older product, and maintaining the old paths costs engineering time.
Pitfalls
Letting shared services or personalisation leak new behaviour into the holdback.
Lessons and concepts
Claims and their sources
In low-power designs, statistically significant estimates tend to overstate the true effect (Type M error).