The paradox of progress

Every time a major platform rolls out a redesign, the internet erupts. YouTube changes its video player, and users call it "the worst UI ever." Snapchat rearranges its interface, and 1.3 million people sign a petition to revert it. Apple introduces Liquid Glass, and forums fill with people refusing to update their phones. This pattern plays out over and over, at every scale. From consumer apps to enterprise software, people push back against change, even when the change is objectively better. Understanding why this happens, and how to work with it, is one of the most important things you can learn as a designer, builder, or entrepreneur.

The psychology behind the pushback

Resistance to change is not irrational. It is deeply wired into how we think. Psychologists have a name for it: status quo bias. It describes our tendency to prefer the current state of affairs, even when alternatives might be better. The Decision Lab defines it simply as "our preference for the current state of affairs, resulting in resistance to change." Status quo bias is powered by a few related cognitive mechanisms. Loss aversion means we feel losses roughly twice as strongly as equivalent gains. When a platform removes a feature you relied on, that loss stings more than any new feature excites you. The endowment effect compounds this further: we overvalue things simply because we already have them, including the way we currently do our work. So when YouTube moves the tabs button behind an ellipsis menu, or when Cloudflare rearranges its dashboard navigation, users are not just evaluating the new design on its merits. They are mourning the loss of something familiar. The old design feels like theirs.

The graveyard of redesigns

History is full of cautionary tales. Snapchat (2017) made one of the most dramatic missteps. The app jammed Stories in between private messages and fundamentally rearranged its navigation. 83% of App Store reviews for the update were negative. The backlash was not just noise, it showed up in Snapchat's quarterly earnings through declining user growth and advertising revenue. The company eventually rolled back many of the changes. YouTube has faced repeated waves of user fury over UI updates. In 2025, a redesigned video player with new controls and icons was branded "disgraceful" and "the worst change yet" by vocal users. Reddit threads filled with comparisons to "a scam website" and calls for those responsible to be fired. YouTube even appeared to partially reverse the changes after the backlash. Digg, once the dominant social news site, pushed a controversial redesign in 2010 that so alienated its community that users fled to Reddit in what became known as "the Digg Exodus." The site never recovered. Even enterprise software is not immune. Cloudflare users regularly complain when their dashboard gets rearranged. Community forum posts surface with titles like "Undesirable Changes to Dashboard Interface" and "Dashboard suddenly changed and I can't see WAF custom rules anymore." When your users depend on muscle memory to manage their infrastructure, even small navigations changes feel like the rug has been pulled out.

Liquid Glass and the cycle of innovation

Apple's Liquid Glass, introduced with iOS 26, is a fascinating case study because it sits right in the middle of an ongoing cycle. The design uses translucent, refracting UI elements that overlay content rather than sitting in fixed toolbars. The backlash was immediate: users criticized readability issues, battery drain, and described the animations as "from 2005." Nielsen Norman Group, one of the most respected UX research firms, published an analysis titled "Liquid Glass Is Cracked, and Usability Suffers." Some users reported actively avoiding the iOS update because of the design. But here is the interesting part. This is not actually new. Microsoft introduced transparent, glass-like UI elements with Windows Aero in Vista back in 2006. At the time, it was criticized for being resource-hungry and was widely seen as style over substance. Most machines could not run it smoothly, and users disabled it to reclaim performance. Fast forward nearly two decades, and the same aesthetic concept is back, executed with modern hardware that can actually handle it. Windows Vista's Aero Glass was called a misstep. Apple's Liquid Glass is called innovation. As one retrospective put it, "What launched to howls of derision has grown into a defining style... a rare case where risky experimentation paid dividends long after the fact." Some users have already come around. One writer described their experience: "I hated it... until I fell in love with it." The pattern repeats: shock, rejection, gradual adaptation, and eventually, acceptance.

It is not just UX

The resistance to change extends far beyond visual design. In enterprise software, ERP implementations routinely fail because of user resistance, not technical issues. Panorama Consulting describes how this resistance is "often quiet and slow-moving," showing up as workarounds, shadow processes, and passive non-adoption rather than outright refusal. Changing workflows is arguably harder than changing interfaces. A new dashboard layout might take a week to get used to. A new way of managing projects, filing reports, or communicating with your team can take months, and the productivity dip during that transition is real. Companies resist change structurally too. Legacy systems persist not because they are good, but because the cost of switching, in time, training, and disruption, feels greater than the cost of staying. Grand Studio describes how organizations "accumulate layers of technology, processes, and teams that, over time, create a tangled web of complexity" that becomes its own barrier to change.

Why this matters if you are building things

If you are designing products, building software, or leading any kind of change, understanding resistance is not optional. It is core to your job. Here are the practical lessons from decades of redesign backlash: Gradual beats radical. Facebook, for all the complaints it has received over the years, has been remarkably successful at evolving its interface incrementally. Each individual change provokes grumbling, but the platform never faced a Snapchat-level exodus. Incremental change lets users adapt without feeling like the product was taken away from them. Involve people early. Research on ERP resistance consistently shows that employees resist harder when they feel a new system is being "forced onto them." Involving users in the process, even symbolically, creates buy-in. When a manufacturing plant asked supervisors what would make an implementation successful instead of defending the technology choice, those same supervisors became advocates. Acknowledge what is lost. Every change removes something. Pretending otherwise breeds resentment. When YouTube redesigns its player, users lose muscle memory and spatial familiarity. Acknowledging that cost, rather than only marketing the benefits, builds trust. Design transition paths, not just end states. The best changes include escape hatches, gradual rollouts, and ways for users to ease in. Apple's Reduce Transparency accessibility setting, for instance, gives Liquid Glass skeptics a way to soften the effect while they adjust. Give it time, but listen. Not all backlash is just status quo bias. Snapchat's redesign had genuine usability problems that hurt their business. The skill is distinguishing between temporary discomfort with the new and legitimate signals that something is broken. If your metrics decline and do not recover, the users might be right.

The paradox of progress

There is a fundamental tension in building things for people. Users want products to improve, but they do not want products to change. These are contradictory desires, and navigating that contradiction is the real design challenge. The best products thread this needle by making the new feel like a natural extension of the old. When Apple moved from skeuomorphic design to flat design with iOS 7, the outcry was enormous. Today, nobody wants to go back to the faux-leather calendars and felt-textured game tables. The same will likely be true of Liquid Glass in a few years. Change is inevitable. Resistance to it is equally inevitable. The question is not how to eliminate resistance, because you cannot. The question is how to design change that respects what people value about the present while moving them toward something better. As the history of tech design shows us, today's outrage often becomes tomorrow's nostalgia. The transparent glass that Vista users disabled to save their CPU cycles is the same aesthetic that Apple now presents as the future. The only thing that changed was the hardware caught up, and we had enough time to forget we ever hated it.

References