Loss Aversion

This is the most important bias nobody puts in their slide deck.

Users will fight harder to keep a feature they barely use than they'll cheer for a better one that replaces it. They'll put up with a slightly worse product to avoid going through a migration. They'll pay more to avoid a price increase than they'd save by switching to a competitor.

Loss aversion is the single biggest force acting on decisions about removing features, changing prices, redesigning flows, and migrating users — and most product teams get it wrong, because the upside is easy to see (faster loading, nicer UI, lower cost to run) while the downside is invisible until it shows up later as churn, support volume, and one-star reviews.

The defence: when you're weighing a change that removes or replaces something users currently have, assume the emotional loss is twice the size of the actual change. Plan the communication, the rollout, and the migration buffer as carefully as you'd plan the feature itself.

A team decides to replace a legacy Watchlist v1 with a redesigned v2 that's objectively better in every measurable way — faster, more customisable, better sorting. The migration is forced with 30 days' notice. The product team expects a week of complaints and then acceptance.

Instead: support volume 6× for three weeks, 4% of affected users stop placing trades entirely for a month, and the top App Store review ('you ruined the app') gets 900 upvotes.

The v2 is, in fact, better. But users evaluated the change as 'lost the thing I'd set up the way I wanted' first and 'gained a better tool' second — and the first feeling was roughly twice the size of the second.

A staged rollout, an opt-in period, and a one-tap 'go back to v1' button would have cost three weeks of engineering and saved a quarter of reputation damage.