How can product managers effectively balance the desire to innovate and introduce new features with the need to address buyer resistance? What strategies can they employ?
Product managers are often cast as visionaries driving transformation, but adoption is shaped by far more than a simple contest between “new” and “old.” In reality, whether innovations take hold depends on the subtle interplay between products, social contexts, and lived experiences. The hard truth is that even “objectively superior” innovations face steep odds, as “studies show that new products fail at the stunning rate of between 40% and 90%, depending on the category, and the odds haven’t changed much in the past 25 years.”
To navigate this, product managers need to develop contextual empathy — an ability to see innovation through the lens of users’ everyday lives and communities. Adoption rarely happens just because something is useful. “Consumers irrationally overvalue benefits they currently possess relative to those they don’t,” and losses “loom[ing] larger than gains” makes change feel risky. But resistance isn’t only about loss aversion or habit. Innovations are tangled in networks of culture, routine, and peer influence, where legitimacy must be earned socially as much as individually. The fact that “most people seem oblivious to the existence of the behaviors implicit in the endowment effect and the status quo bias” shows that adoption is as much about social dynamics as it is about rational decision-making.
Instead of obsessing over minimizing switching costs or chasing mythical 10x improvements, product managers might reframe their work in ecosystem terms. Real progress happens when products “reshape the environment of adoption”, and that requires coalition-building — finding allies in trusted communities or partnering with complementary services that lower collective resistance. The success of hybrid vehicles, for example, came less from radical disruption than from layering green technology onto familiar habits: “the Prius provides drivers with both the traditional internal-combustion engine and an innovative, self-charging electric engine, resulting in a driving experience that is virtually identical to that of a gasoline-only car.” In that sense, adoption unfolded as a shared journey rather than an individual leap.
Participatory design offers another valuable lever, as when users “see their fingerprints on the product,” the discomfort of change can turn into pride of ownership. Involving representative (even skeptical) users throughout development signals respect for the real-world context innovation enters. It also guards against feature creep: with thoughtful co-design, every new feature must justify itself not by “creativity” alone but by its genuine fit with the ecosystem’s needs. Seen this way, feature creep becomes “a failure of collaboration and constraint” more than a failure of imagination.
Finally, product managers should recognize the power of change agents or “network bridges” within user communities. Diffusion often happens because a trusted individual with credibility or deep contextual understanding advocates for the product (as the reading says, “the messenger is as vital as the message”). Rather than convincing every buyer directly, the goal is to empower those already woven into the social fabric to champion adoption naturally.
