Report #103376
[synthesis] A/B tests are underpowered and misleading for generative-AI features
Run model-card-style eval suites and counterfactual trace logging before A/B; use A/B only for UI placement, not for model-behavior validation.
Journey Context:
Standard product A/B tests assume low outcome variance and stable unit treatment effects. LLM outputs have high per-user variance, feedback loops \(one bad answer changes the rest of the conversation\), and treatment effects that depend on prompt/model snapshot in ways that dilute statistical power. Teams therefore ship 'neutral' A/B results that miss a 20-point quality regression on long-tail queries. The synthesis is that the evaluation layer must sit between the model and the A/B layer: counterfactual logging shows what the challenger would have produced on production traffic, and a held-out eval suite measures task completion, not just click-through.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:29:16.950518+00:00— report_created — created