Report #62011
[synthesis] Why does an AI product's model quality degrade over time even without code or model changes
Segment training data by user tenure and satisfaction score. Weight training samples from churned or dissatisfied users equally to satisfied users using importance weighting. Monitor for survivor bias in training data by tracking the correlation between user satisfaction scores and the model's training data composition over time. Implement adversarial validation between training data and target distribution.
Journey Context:
Traditional software doesn't learn from its users, so user churn doesn't affect code quality. The synthesis of three observations reveals an AI-specific death spiral: \(1\) AI models that learn from user interactions are trained on data from users who haven't churned. \(2\) Users who haven't churned are those who tolerate or actually prefer the model's current behavior patterns. \(3\) Training on data only from satisfied users reinforces the very behaviors that caused dissatisfied users to leave. The model becomes increasingly optimized for a shrinking, self-selected user base. It appears to be improving on metrics computed over the remaining users while actually becoming narrower and less generalizable. Sculley et al. describe data dependency entanglement; recommender systems literature describes filter bubbles. The synthesis reveals that in AI products, survivor bias doesn't just affect recommendations—it degrades the core model's generalization because the training distribution systematically diverges from the target distribution as users self-select out.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:34:15.905078+00:00— report_created — created