01Overview
The peak-end rule is a cognitive shortcut first documented by Kahneman and colleagues: people evaluate an experience almost entirely based on how it felt at its most intense point (the peak) and at its end. Duration barely matters. A long unpleasant experience with a pleasant ending is rated more positively than a shorter one that ends badly.
For designers, this concentrates enormous leverage on two specific moments — the emotional high point and the final state. Everything in the middle, however well designed, contributes far less to how users remember and talk about the product.
02Detailed explanation
The colonoscopy experiment (Redelmeier & Kahneman, 1996) is the canonical study. Patients undergoing colonoscopies rated their pain moment by moment. Remembered pain correlated strongly with peak pain and final-moment pain — but not with total duration. A group randomised to an extra 60 seconds of mild discomfort at the end of their procedure rated the overall experience as less painful than those whose procedure ended at a high-pain moment. The added time improved the ending, and that outweighed the added total discomfort.
- Participants who had a shorter but worse ending rated their overall experience more negatively than those with a longer but better ending — demonstrating duration neglect.
- The rule applies to positive experiences too: a holiday rated 7/10 throughout but with a peak moment of 10/10 and a warm final day is remembered more positively than a more consistently good holiday that ended in a flight delay.
- In UX: the emotion at the end of checkout defines "what shopping on this site is like." The satisfaction at the end of onboarding defines "what using this product is like."
03Why it exists
Memory is reconstructive, not reproductive. The mind stores summaries, not recordings. The peak captures the emotional high-water mark; the ending is the most recent data point and determines the "exit emotion" stored as the memory of the whole experience. Duration is too unwieldy to store as a meaningful summary variable.
The experience is not the memory. The memory is the peak and the end. Design for those two moments above all others — the rest is infrastructure.
04Effects on users
- A checkout flow with a warm, personal confirmation screen leaves a better lasting impression than a fast checkout that ends with a dry "thank you."
- An onboarding flow with one genuinely exciting moment — first value delivered, first "aha" — anchors the user's memory positively, even if surrounding steps were routine.
- Subscription cancellation that ends gracefully can preserve goodwill and reduce the cost of re-acquisition later.
- A well-designed recovery from an error can become the emotional peak of an experience — better remembered than a flawless transaction.
05Effects on designers & teams
- Sprint reviews: the last slide or demo sets the emotional tone of the team's memory of the sprint. The order of what you present matters.
- Design critiques: an opening strong concept followed by weaker ones is remembered differently than weak-then-strong ordering — the ending biases the overall evaluation.
- User research: the last question in an interview shapes what participants remember "we talked about today." Place the most important topic accordingly.
6Introspective view
Look inward. Interview recall over-weights peaks and endings, so reported satisfaction misrepresents the whole journey.
From an introspective perspective, ask how Peak–End Rule may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.
What you hear first sticks
In early interviews about Peak–End Rule, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Interview recall over-weights peaks and endings, so reported satisfaction misrepresents the whole journey.
Questions you set out to answer
Discovery framed around Peak–End Rule can narrow what you go looking for before the first interview ships. Interview recall over-weights peaks and endings, so reported satisfaction misrepresents the whole journey.
Question order shapes answers
A survey built to study Peak–End Rule often primes respondents before the key item: lead with a vivid scenario and later ratings drift toward that frame. Interview recall over-weights peaks and endings, so reported satisfaction misrepresents the whole journey.
Sessions read through your hypothesis
While moderating a test, Peak–End Rule can steer what you notice — a stumble you expected feels confirming; an unexpected workaround gets filed as noise. Interview recall over-weights peaks and endings, so reported satisfaction misrepresents the whole journey.
7Extrospective view
Look outward. Users remember the peak and the end of an experience, so design memorable highs and strong finishes.
From an extrospective perspective, Peak–End Rule is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.
How far along it feels
Progress bars and step counts change behaviour through Peak–End Rule — users treat sunk steps as a reason to continue, or misread how much work remains. Users remember the peak and the end of an experience, so design memorable highs and strong finishes.
Success and failure moments
Confirmation screens and empty states shape how Peak–End Rule is felt — a dramatic error feels more costly than a neutral one; a celebratory success feels more rewarding than the outcome may warrant. Users remember the peak and the end of an experience, so design memorable highs and strong finishes.
First impressions that stick
Early onboarding screens are high-leverage for Peak–End Rule: the first promise, time estimate, or success story becomes the reference for everything that follows. Users remember the peak and the end of an experience, so design memorable highs and strong finishes.
Cancel and downgrade flows
Retention design uses Peak–End Rule heavily in offboarding — summarising what users will lose, pausing instead of cancelling, and reminding them of accumulated value. Users remember the peak and the end of an experience, so design memorable highs and strong finishes.
08Practical takeaways
- Identify the emotional peak: what's the best moment in your product experience? Have you designed it intentionally, or is it accidental?
- Design the ending: the last screen, the confirmation state, the "you're done" moment is disproportionately important to how the whole experience is recalled.
- Offboarding deserves the same care as onboarding: a graceful cancellation experience with data export and no dark patterns protects future re-acquisition.
- Compress long neutral stretches: the middle is forgotten. Don't let mediocre middle moments be the only thing between a user and their peak.
- Use the rule in testing: "how would you describe this experience to a friend?" — that description is their peak-end memory, not an average rating.
09Design examples
The confirmation screen
The "thank you for your order" screen is the last thing the user sees. A basic confirmation with an order number is fine. A warm, excited confirmation that feels like shared anticipation creates a different memory of what buying from you is like.
The first "aha"
Great onboarding engineers a peak: the moment the user sees the thing they came for. This is often the first real piece of value — the first created item, the first connection made. Design this moment deliberately; don't let it happen by accident.
The graceful exit
Cancellation flows that end with hostile UI, dark patterns, or an indifferent "your account has been cancelled" leave a poor last impression. Graceful exits — "we've cancelled your subscription; your data is available for export until [date]" — protect the relationship for future re-acquisition.
Recovery as peak
A well-designed error recovery can become the emotional peak of an experience. "Something went wrong — here's exactly what happened and what to do next, and we've refunded the charge" is often a better memory than a flawless transaction.
10Ethical risks
The peak-end rule is exploited when designers engineer memorable positive peaks to override genuinely bad middle experiences — using a delightful confirmation screen to paper over a tedious, confusing checkout, or using a warm onboarding peak to distract from a product that won't deliver what it promised.
The memory should not be better than the reality it represents. If users are remembering an experience positively and leaving the product negatively, you've designed a gap between feeling and fact — and that gap erodes trust.
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.