Report #62420
[synthesis] Why A/B testing gives misleading results for AI features
Use interleaving experiments instead of standard A/B for AI features, or at minimum apply CUPED with pre-experiment covariates for task difficulty. Monitor for selection bias where users self-select into harder or easier tasks based on perceived variant quality.
Journey Context:
Standard A/B testing assumes independent and identically distributed observations. AI product outputs violate this in three ways: \(1\) Users adapt their inputs based on perceived model quality—if variant B seems better at code, users give it more code tasks, creating selection bias that inflates B's measured performance. \(2\) AI outputs are correlated within sessions—a good early answer increases engagement, producing more data points from satisfied users and fewer from frustrated ones who left. \(3\) Treatment effects are heterogeneous across task types, but standard A/B averages this out, masking that a variant is catastrophically worse for important minority use cases. Teams commonly run standard A/B tests and get misleading wins—a variant that's worse overall but better for the most common use case appears to win. Interleaving \(showing both variants in random order to the same user\) eliminates selection bias but is harder to implement and requires careful UX design. The synthesis: controlled experiment methodology was designed for UI changes where the treatment effect is roughly constant; for AI, the treatment effect is a function of the input distribution, which the treatment itself shifts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:15:21.646689+00:00— report_created — created