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 plate
Reach for this when
- Designing confirmations, completions and offboarding.
- Prioritising which moments in a long flow deserve extra investment.
- Interpreting satisfaction survey results.
- Deciding where to spend a limited amount of design attention across a long flow.
Common mistakes
- Confusing a celebratory animation with a genuine peak.
- Ignoring the middle of the flow because it is not remembered.
- Placing satisfaction surveys immediately after friction.
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.
Where the peaks and the ends actually are
Most products design the middle carefully and let the moments that get remembered happen by default.
| Moment | Why it weighs more than its length |
|---|---|
| First successful action | The peak that decides whether there is a second session |
| The first error | A negative peak, and the one most likely to be told to somebody else |
| Payment confirmation | The end of the flow people describe when asked about the product |
| Cancellation | The end of the relationship, and the version that shapes the recommendation |
| Support resolution | Often the highest peak available, positive or negative |
In practice
- i.
Order confirmation as the designed ending
EcommerceA 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.
- ii.
One-click cancellation
SubscriptionsProducts 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.
- iii.
The long wait that was remembered well
Duration neglectA six-minute setup that ended with a working result and a clear summary was recalled more favourably than a three-minute one that ended on an ambiguous screen. Retrospective judgement is remarkably insensitive to how long something took.
Commonly confused with
Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.
Serial Position Effect
LawRecall varies with an item's place in a sequence.
Key difference
Serial position is about position in a list of items. Peak-end is about moments in an experience over time. One shapes how you order a menu; the other shapes how a flow is remembered once it is over.
Use Peak-End Rule when
- The subject is a flow, a session or a support interaction.
- You are deciding where to spend effort across a journey.
- Duration matters less than the worst moment and the last one.
Use Serial Position Effect when
- The subject is a list, a menu or a set of options.
- Everything is present at once and order is the variable.
Local chart
LAW·007 · Region I · Grid A2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
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
- [2]
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
Applied through
Where this shows up as a concrete interface decision.
- ConfirmationPAT·008 · Pattern
The last screen of a flow is weighted out of proportion in what people remember.
- Empty StatesPAT·010 · Pattern
- Usability TestingRES·001 · Research method
- MicrocopyWRT·001 · UX writing
Often used with
These usually appear in the same screen or the same decision.
- Journey MapTPL·004 · Template
Practical example
A worked decision where this was the deciding factor.
- Designing a Cancellation FlowCASE·008 · Case study
Check your work
Review passes that test whether this was done properly.
- Onboarding ChecklistCHK·005 · Checklist
Short definition
The one-paragraph version, for when that is all you need.
- ChurnTERM·102 · Term
- Journey MapTERM·117 · Term
- TouchpointTERM·018 · Term
Related concept
Connected closely enough to change how you apply this.
- Help Users Recognise, Diagnose and Recover From ErrorsHEUR·009 · Heuristic
- User Control and FreedomHEUR·003 · Heuristic
- Aesthetic-Usability EffectLAW·011 · Law
- Goal-Gradient EffectLAW·014 · Law
- Zeigarnik EffectLAW·010 · Law
- Deceptive PatternsPRIN·011 · Principle
- ForgivenessPRIN·006 · Principle