Why might adding more features to Product B be discouraged?

• A. Because current customer happiness is high and new features could reduce it
• B. Because added features might require more maintenance and cost
• C. Because revenue is the only metric that matters
• D. Because user satisfaction is unfounded by features

Answer: (A)

Preserving customer happiness when deciding on backlog items is the key idea. If users are already very satisfied, adding more features can disrupt what they value and enjoy—introducing complexity, new bugs, or changes to workflows that feel unnecessary. This can reduce usability and trust, turning a positive experience into a less satisfying one. So the best choice is that new features could diminish current happiness, making the feature addition not worthwhile unless there’s a clear, proven improvement to outcomes.

Maintenance or cost are important considerations, but they don’t capture the risk to user sentiment as directly. Revenue being the only metric ignores other essential outcomes like satisfaction and value. And user satisfaction isn’t something that’s unfounded by features; features can drive satisfaction when aligned with real needs, not when added for their own sake.