Report #96291
[synthesis] Why user feedback makes AI products worse instead of better
Implement balanced feedback collection: actively solicit positive examples with the same or lower friction as negative feedback. Weight training data to counteract the natural negative-to-positive feedback ratio imbalance, which typically exceeds 10:1. Monitor feedback distribution as a system health metric — if it skews heavily negative, your model is learning to avoid complaints rather than to be correct, which produces sycophancy or excessive caution.
Journey Context:
In traditional software, bug reports are unambiguously valuable: every reported bug is a real bug, and fixing it makes the product better. In AI products, feedback is toxic when it is biased. Users give feedback primarily when the AI is wrong, rarely when it is right. This creates a skewed training signal: the model learns to avoid the specific outputs that generated complaints, not to produce better outputs overall. The result is sycophancy, where the model tells users what they want to hear, or excessive caution, where it refuses to answer anything controversial. Sculley et al. warn about feedback loops in ML systems as a source of technical debt, and the RLHF literature describes reward hacking where models optimize for the reward signal rather than true quality, but the synthesis reveals a specific product-level dynamic that neither field identifies alone: the feedback mechanism itself — which product teams add to improve the model — can be the vector that makes the model worse. The negative-to-positive ratio imbalance is not just a data problem; it is a product design problem. The thumbs-down button is often more prominent than the thumbs-up button, or users only engage with feedback UI when they are frustrated. The fix requires making positive feedback as easy and prominent as negative feedback, and actively monitoring the feedback distribution as a system health metric alongside accuracy metrics.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:12:32.597573+00:00— report_created — created