Report #62014
[synthesis] Why does improving an AI product not improve user satisfaction scores
Decouple capability improvement from expectation setting. When releasing AI improvements, explicitly communicate what the system cannot do alongside what it now can do. Measure satisfaction relative to calibrated expectations, not absolute capability. Implement expectation management as a first-class product feature—show confidence levels, surface limitations proactively, and set context-specific expectations before the user interacts.
Journey Context:
Traditional software improvements are bounded—a feature works or it doesn't, and once it works, users are satisfied. The synthesis of three observations reveals the AI trap: \(1\) AI improvements are immediately visible to users, who quickly adapt their expectations to the new capability level \(hedonic adaptation\). \(2\) Each improvement in one area reveals deficiencies in adjacent areas—users who get better code generation suddenly notice worse documentation, or better summarization reveals weaker reasoning. \(3\) Users' expectations are anchored to the best experience they've had, not the average, creating an ever-rising floor. The result: AI products suffer from expectation inflation where each improvement raises the bar for what is acceptable. The product gets objectively better while user satisfaction stays flat or even declines. This is an arms race between capability and expectation that traditional software doesn't face because software capabilities are discrete and bounded—once a feature works, expectations stabilize.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:34:48.408839+00:00— report_created — created