CRO Glossary
Experiment Velocity Tax
The hidden slowdown in shipping new tests caused by accumulated technical, process, or review overhead.
Experiment velocity tax describes the creeping cost that makes each new test take longer to launch than the last one, even though the team hasn't gotten any less capable. It shows up as QA cycles that balloon because of legacy variants still wired into the codebase, approval chains that grow as more stakeholders want sign-off, or analytics instrumentation that has to be patched around older experiments before a new one can go live.
Teams care about this because experimentation programs are usually judged on throughput — how many validated learnings per quarter — and a rising velocity tax quietly erodes that number even as headcount and budget stay flat. It's easy to miss because any single test still feels launchable in a reasonable timeframe; the drag only becomes visible in aggregate, across a roadmap.
A concrete example: a team running checkout experiments accumulates a dozen old feature flags from past tests that were never cleaned up. Each new experiment's QA now has to verify it doesn't collide with any of those flags, adding days to every release. The tax is the extra days, not the original experiments.
Combating it usually means scheduled cleanup of dead flags and documentation, simplifying approval workflows, and periodically auditing the experimentation platform setup — treating the tax as its own line item to reduce rather than an unavoidable cost of maturity.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply experiment velocity tax.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.