Report #102828
[synthesis] Why A/B tests give false positives on AI features even with large samples
Use paired reranking or session-level randomization with burn-in; measure per-query consistency \(e.g., rank correlation\) alongside top-line metrics; pre-register a minimum detectable effect that exceeds your measured output variance, not just the standard error of the mean.
Journey Context:
Google's overlapping-experiment infrastructure assumes a deterministic mapping from treatment to user experience, which is why it can partition parameters into layers. LLM APIs are only 'mostly' deterministic even with seed and system\_fingerprint pinned. The synthesis is that standard A/B power calculations treat all variance as between-users, but AI introduces within-treatment output variance that swamps small effect sizes. Teams that run ordinary t-tests on conversion metrics will ship noise. The right call is to design experiments that randomize sessions and measure distributional stability of outputs, not only business outcomes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:31:48.364333+00:00— report_created — created