Skip to content
The Product Guys
All lessons
User Psychology6 min read

Loss Aversion, Honestly

The finding is real but smaller than the folklore, and the ethics get sharp fast.


Saltbox, a bookkeeping tool for small studios, is rewriting its cancellation flow. The current version is one button and a confirmation. Growth proposes a new version: a screen showing everything the account will lose, then an offer of two months at half price. The projected save rate is 18 percent. Someone asks whether this is a good idea or a trap, and the room splits. This lesson is about how to argue that question well.

The asymmetry, without the folklore multiple

Gaining tenpounds10Losing the tenyou had16
Losing something weighs more than gaining the same thing. That direction holds up. The size does not: the often-quoted ratio comes from particular lab gambles, and later field work finds it smaller and heavily dependent on context. Treat the tilt as real and the number as unknown for your product.

What prospect theory says

Kahneman and Tversky's 1979 paper on prospect theory made two claims that matter here. People evaluate outcomes as gains and losses relative to a reference point rather than as final states of wealth. And the value function is steeper for losses than for gains. In their 1992 follow-up they estimated a loss aversion: Losing something feels worse than gaining the same thing feels good. coefficient around 2, which is where the popular claim that losses hurt twice as much comes from.

Treat that 2 as a rough lab estimate for gambles over money, not a constant of nature. It came from a specific task with a specific population. Gal and Rucker's 2018 paper in the Journal of Consumer Psychology argues the whole principle has been overgeneralised, and that a lot of what looks like loss aversion is better explained by inertia and by the ambiguity of what counts as a loss. You do not have to agree with them, but you should know the debate exists before you cite loss aversion as settled science in a pricing review.

What is robust enough to build on: the reference point does real work. Whether a change reads as gaining something or losing something depends on what the user thinks they currently have, and you influence that.

Framing that fights the user

  • You will lose 4 years of invoices, 312 client records, and 2 connected bank feeds.
  • Are you sure? Your reports will be permanently deleted.
  • Wait! Don't throw away everything you've built.

Framing that respects the reference point

  • Your data stays available to export for 30 days after you cancel.
  • Cancel now and keep read-only access until 14 March.
  • Download everything (CSV, 2 files) before you go.

Both columns reference the same facts. The left column manufactures a loss and stands in the doorway with it. The right column removes the loss, which removes the grip. Notice that the right column probably saves fewer accounts this quarter. It also generates fewer chargebacks, fewer support tickets, and fewer public complaints, and the people who leave cleanly are the ones who come back.

Where the reference point is set legitimately

Pricing is the honest use. An annual plan shown next to the monthly price sets a reference point, and Save 2 months is a true statement about a real comparison. A plan comparison table sets a reference point too. The test is whether the reference point is one the user would recognise as fair if you explained the mechanism to them.

Worked example

Saltbox picks a middle path

They keep the retention offer but move it. On the cancel screen they show one line, Cancel my plan, and a link, See what happens to my data. After the cancellation is confirmed, they send one email: your plan ends 14 March, here is an export link, and if the price was the problem, here is a smaller plan at 9 pounds. Save rate lands at 11 percent instead of 18. Refund requests fall by a third. The team ships it and reports both numbers.

Two operational rules follow. First, if your save offer is genuinely good, it survives being shown after the cancel completes. If it only works while the user's finger is over the button, it is working on panic rather than value. Second, never report a retention win without the refund rate, the support volume, and the reactivation rate beside it. A cancellation flow that converts by friction moves cost into a column nobody on the growth team owns.

One more caution for reviews. Loss aversion is the most cited idea in product psychology and the most loosely applied. If you catch yourself using it to justify a design you already wanted, name the specific reference point you are relying on and say how you would know if you were wrong.

Quick check

Saltbox moves its discount offer to after cancellation completes. What does this test?

The takeaway

Loss aversion is real but contested and smaller than folklore claims, and using it to block an exit converts trust into short-term retention.

Try this tomorrow

Move your best retention offer to after the cancellation is confirmed and run it for one cycle. Report save rate together with refund rate and support volume.

Answer the check above, then bank the day.

Where this comes from

  • Prospect Theory: An Analysis of Decision under Risk (1979), Daniel Kahneman and Amos Tversky
  • Thinking, Fast and Slow, Daniel Kahneman
  • The Loss of Loss Aversion: Will It Loom Larger Than Its Gain? (2018), David Gal and Derek Rucker

User Psychology is one of six tracks. These lessons summarise and build on the work above, they do not reproduce it. Buy the books, they are better.