Skip to content
UX Atlas
LawEstablished researchIntermediate

Peak-End Rule

People judge an experience by its most intense moment and its ending, not by the average of the whole thing.

Definition

Work by Daniel Kahneman, Barbara Fredrickson and colleagues showed that retrospective evaluations of an experience are predicted largely by the peak affect and the final moments, and are remarkably insensitive to how long the experience lasted.

Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.

On this page
  1. Definition
  2. Remembered experience is not lived experience
  3. Where the peaks and ends are in a product
  4. Designing the shape of an experience
  5. In practice
  6. Sources
  7. Continue from here

Remembered experience is not lived experience

Kahneman distinguishes the experiencing self from the remembering self. The remembering self decides whether you come back, recommend the product and renew the subscription. It is a lossy summary weighted towards extremes and endings.

The related finding, duration neglect, is the more surprising one: total duration has little effect on the remembered rating. A shorter unpleasant experience can be remembered as worse than a longer one that ends more gently.

Where the peaks and ends are in a product

  • Peak candidates: the first time the core value lands, a serious error, a data loss event, an unexpectedly smooth recovery.
  • End candidates: the confirmation screen, the last step of onboarding, the moment after saving, the cancellation flow.
  • Cancellation is an ending. It is the last thing a departing user remembers and the strongest determinant of whether they come back or warn others off.

Designing the shape of an experience

Do

  • Invest disproportionately in confirmation and completion moments.
  • Make error recovery a designed moment, since a well-handled failure can itself become a positive peak.
  • Make cancellation quick and dignified.
  • End long flows with a clear statement of what happened and what comes next.

Do not

  • Manufacture celebration where the user did not achieve anything. Confetti on a routine save is noise.
  • Use the rule to justify a painful middle. It still costs you completion rate even if it is not remembered.
  • Ask for a rating immediately after a friction point, unless you want the friction in your data.

In practice

Order confirmation as the designed ending

Ecommerce

A confirmation that states what was bought, when it arrives and how to change it, in plain language, is the last thing the customer sees. It is a cheap place to buy goodwill relative to the effort spent on the product page.

One-click cancellation

Subscriptions

Products that let users cancel in one step see returning subscribers. Products that run a five-screen retention gauntlet win the current month and lose the reputation, and increasingly attract regulatory attention.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  • When more pain is preferred to less: adding a better end

    D. Kahneman, B. L. Fredrickson, C. A. Schreiber and D. A. Redelmeier, Psychological Science, 1993

  • Thinking, Fast and Slow

    D. Kahneman, Farrar, Straus and Giroux, 2011

    Chapters on the experiencing and remembering selves, and duration neglect.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A CheckoutAn Ecommerce ExperienceAn Onboarding Flow

Why this works

The reasoning this entry rests on.

Applied through

Where this shows up as a concrete interface decision.

Often used with

These usually appear in the same screen or the same decision.

Practical example

A worked decision where this was the deciding factor.

Check your work

Review passes that test whether this was done properly.

Short definition

The one-paragraph version, for when that is all you need.