The Loss Aversion Phenomenon
Loss aversion plays a key role in the resistance buyers have to accepting a new product or feature. This phenomenon requires businesses to not only provide a qualitative edge over the status quo, but to demonstrate such a substantial increase in quality that it overcomes any perceived “loss” on the customer’s end. As Kahneman and Tversky define it, the consequence of loss aversion is that “losses have a far greater impact on people than similarly sized gains.”
If a business cannot show the financial and behavioral costs of switching are substantially smaller than the quality it delivers, the business faces a near-impossible task of overcoming buyer resistance.
Can a PM Come to the Rescue?
A product manager can leverage this understanding of loss aversion and buyer behavior to better facilitate the adoption of new features. A core tenet of product management is to focus on the customer, not the feature, a perspective that differentiates a PM from developers and designers. Starting with user experience and pain points, a PM is in a unique position to understand how much value a product feature must deliver to outweigh the loss aversion of switching from the status quo.
It is also their responsibility to communicate this priority across the organization—from design and development through sales and marketing. Developers need to understand what quality customers seek, and marketing must highlight not just the product’s strengths but how these qualitative gains offset buyers’ “losses.” Without this, the business risks its new feature falling victim to the “endowment effect,” which causes “people to value products that they already possess… more than those they don’t have.” By facilitating communication across teams, a PM can minimize this risk and allow the feature to overcome the endowment effect.
Expectation vs. Reality
While PMs seem to have a clear directive for overcoming loss aversion, the reality of feature development and launch is more nuanced. The development team may be unable to deliver the level of quality needed to show value under technical constraints. Or even if a new feature does manage to deliver gains, it may demand substantial behavioral change, making buyers doubt the promised benefits.
However, product management doesn’t necessarily end if it becomes impossible to truly counter loss aversion if it proves difficult to counter loss aversion; instead, it’s the PM’s job to guide strategy and leadership in adapting the business model to buyer psychology. Rather than pursuing the “smash hit” (a feature that can produce significant gains with little change) or the “easy sell” (an easy feature to implement that poses little loss to the buyer), a PM may need to help the business commit to the “long haul” or abandon a “sure failure” feature.
In the end, a PM’s knowledge of loss aversion is vital to delivering successful features, guiding development and strategy in ways that server both business and customer needs, and ensuring the organization doesn’t fall victim to the “eager seller” trope.
