Report #101399
[synthesis] A/B test results for AI features flip or fade after launch
Use user-level \(not request-level\) randomization, pre-register capability-boundary strata, and pair the experiment with a prompt-drift monitor; treat metric inversion as a first-class signal, not noise.
Journey Context:
Pure engineering A/B tests assume stable treatment effects and independent observations. AI features violate both: the same user adapts prompts based on model outputs, and a model's value is concentrated at a 'jagged frontier' of tasks. A request-level A/B can show a lift in week one and a negative effect in week three because control-group users borrow prompt patterns from treatment-group users, or because the test population averages away strong gains and strong losses. The synthesis is that the experiment design itself must model the capability boundary, not just the user population.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:29:14.866933+00:00— report_created — created