Peak-End Rule
Users judge experiences by their most intense moment (peak) and their ending — not the average. Design peaks and endings deliberately.
What is it?
The Peak-End Rule is a psychological heuristic by which people judge experiences based on how they felt at the most intense point (the 'peak' — either positive or negative) and at the end, rather than based on an average across the total experience. Identified by Daniel Kahneman and colleagues in 1993, it has profound implications for how we design user journeys.
Why it matters
A checkout flow with 8 smooth steps but a confusing final payment screen will be remembered as frustrating — because the end was bad. An onboarding flow that ends with a celebration moment will be remembered as delightful — even if some earlier steps were unclear. Designing the peak and the end of your flows is as important as designing the flow itself.
Best Practices
- Identify every flow's ending — what is the final moment of the interaction? Make it positive and conclusive.
- Design explicit celebration moments: confetti on signup, success animations on first task completion.
- For long flows, identify the peak moment (highest emotional intensity) and design it deliberately.
- Order confirmation, successful payment, and completed onboarding are peaks — never leave them as plain text.
- The cancellation or offboarding flow ending must not be punishing — users who cancel well are more likely to return.
- If a flow has a necessary negative moment (failed payment), design a recovery that ends positively.
- Use empty states productively — the "no data yet" state is often a user's first experience with a feature. Make it welcoming, not blank.
- End emails, notifications, and messages on a positive, forward-looking note.
- After a difficult support interaction, end with a clear confirmation and a thank-you — the ending colors the whole experience.
Common Mistakes
- Order confirmation pages that show just an order number with no warmth, celebration, or next steps.
- Cancellation flows designed to be punishing (dark patterns) — these create resentful ex-users.
- Onboarding that ends at "setup complete" with no celebration of what the user just accomplished.
- Error recovery flows that fix the problem but end on a terse, clinical note.
- Ignoring the ending of notification emails — they taper off into legal disclaimers.
- Success states that are identical to neutral states — no peak, no differentiation.
Checklist
Research & Theory
Kahneman et al. (1993) — Colonoscopy Study
Patients undergoing colonoscopies rated their pain retrospectively based on peak pain and end pain, not total duration. Longer procedures with a less painful end were rated as better experiences than shorter, more uniformly painful ones.
Why it's relevant
Duration neglect is real. A longer but better-ending experience is remembered more favorably than a shorter, badly-ending one.
Experiencing Self vs. Remembering Self (Kahneman)
Kahneman distinguishes the "experiencing self" (in-the-moment) from the "remembering self" (retrospective evaluation). Products are judged by the remembering self.
Why it's relevant
Design for memory, not just the moment. The peak and end determine what users will say, share, and return for.
Real-World Examples
Mailchimp
The "high five" screen after sending a campaign is famous. A cartoon hand high-fives you. A moment of genuine delight at the peak of the send flow.
Duolingo
Lesson completion is a peak: fireworks, XP gained, streak maintained, celebration screen. Even if lessons were difficult, they end with delight.
Stripe
First successful payment in test mode triggers a celebration banner. The peak of the integration flow is explicitly designed.