Skip to main contentSkip to navigationSkip to footer
168+ Principles LibraryResearch-backed UX/UI guidelines with citationsAI Design ValidatorValidate AI designs with research-backed principlesAI Prompts600+ research-backed prompts with citationsFlow ChecklistsPre-flight & post-flight validation for 5 flowsUX Smells & FixesDiagnose interface problems in 2-5 minutes
View All Tools
Part 1FoundationsPart 2Core PrinciplesPart 3Design SystemsPart 4Interface PatternsPart 5Specialized DomainsPart 6Human-Centered
View All Parts
About
Sign in

Get the 6 "Must-Have" UX Laws

The principles that fix 80% of interface problems. Free breakdown + real examples to your inbox.

PrinciplesAboutDevelopersGlossaryTermsPrivacyCookiesRefunds

© 2026 UXUI Principles. All rights reserved. Designed & built with ❤️ by UXUIprinciples.com

ToolsFramework
Home/Part I - Foundations/Motivation & Engagement

Peak-End Rule

peak-endrulememoryemotionexperiencesatisfactionevaluationux design
Intermediate
12 min read
Contents
0%

Memory lies. Systematically.

People judge experiences largely based on two critical moments. The peak emotional intensity. Whether positive or negative. And the ending.

While nearly ignoring duration. And average quality throughout the experience.

Kahneman, Fredrickson, and colleagues' research (1993) demonstrated the bias. Through the "cold pressor" experiment. Participants preferred longer painful experiences. Adding moderately painful endings. Over shorter experiences ending at peak pain.

Establishing that end experiences dominate memory. More than total suffering.

This memory bias creates systematic differences. Between experienced utility. Moment-to-moment well-being. And remembered utility. Retrospective evaluation. Fundamentally shaping future choices.

The principle: Peaks and ends matter most. Duration? Almost ignored. Design accordingly.

The Research Foundation

Kahneman and colleagues' seminal cold pressor experiments (1993) provided compelling evidence for peak-end dominance in memory. Participants submerged hands in painfully cold water (14°C) for 60 seconds (short trial) versus 90 seconds where final 30 seconds warmed slightly to 15°C (long trial). When asked which trial they'd repeat, 69% chose the longer trial despite experiencing objectively more total pain. The less-painful ending dominated memory making longer suffering feel preferable—participants' remembering selves chose based on peak pain and final pain, completely ignoring 30 extra seconds of discomfort. This duration neglect demonstrated that memory systematically ignores experience length.

Redelmeier and Kahneman's colonoscopy study (1996) validated peak-end effects in real medical contexts. Patients undergoing colonoscopy procedures rated pain in real-time (every 60 seconds during procedure) and retrospectively (after completion). Retrospective ratings correlated strongly with peak pain intensity and final minute pain (r=0.67 and r=0.65) but weakly with procedure duration (r=0.03). Patients experiencing longer procedures with gradually decreasing pain endings rated experiences more favorably than patients with shorter procedures ending at higher pain levels—despite experiencing more total discomfort. These findings revolutionized medical procedure design suggesting strategic pain management focusing on endings rather than minimizing total pain duration.

Fredrickson and Kahneman's duration neglect research (1993) systematically tested how experience length affects evaluation. Participants viewing pleasant or unpleasant film clips showed retrospective evaluations correlating with peak emotional intensity and final moments but not viewing duration. Doubling clip length (from 60 to 120 seconds) while maintaining peak and end quality produced statistically identical evaluations. This established duration neglect as robust phenomenon—memory formation prioritizes emotional intensity peaks and endings over temporal extent creating systematic bias toward moment-specific rather than cumulative evaluation.

Kahneman's theoretical distinction (2000) between experiencing self (living through moments sequentially) and remembering self (retrospectively evaluating stored memories) explains why peak-end rule operates. The experiencing self rates well-being continuously throughout experiences. The remembering self constructs narratives from selected memories dominated by peaks and endings. Critically, the remembering self guides future decisions—people choose based on remembered experiences, not actual experienced moment-to-moment quality. This creates situations where people make choices maximizing remembered utility while sacrificing actual experienced well-being.

Why It Matters

For Users: Peak-end rule explains common interface satisfaction paradoxes. Users rating experiences immediately after completion evaluate based on final moments and peak frustrations/delights rather than typical interaction quality. An interface with smooth consistent performance throughout but frustrating final step (payment failure, unclear success confirmation) receives worse ratings than interface with periodic minor issues but satisfying conclusion. Stripe's checkout demonstrates peak-end awareness—even when payment processing encounters issues, the flow ensures positive conclusion through clear problem explanation, preserved form data, and easy retry mechanisms making final attempt feel successful rather than frustrating.

For Designers: Onboarding experiences disproportionately shape product perception because they contain both peaks (discovering key features, experiencing "aha moments") and ends (completing setup, first successful task). Notion's onboarding creates positive peak through template gallery discovery—users experience delight finding pre-built structures matching their needs. The onboarding ends with successful first content creation providing satisfying conclusion. These moments dominate initial product impressions far more than the intermediate navigation learning and feature exploration comprising majority of onboarding duration.

For Product Managers: However, negative peaks devastate overall evaluations despite brief duration. Single catastrophic errors—data loss, payment failures, broken core features—create intensely negative memories overwhelming positive experiences surrounding them. Users remember "that time the app lost my work" vividly for months while forgetting dozens of successful sessions. Linear's auto-save and version history prevents data loss negative peaks that would otherwise dominate product memory despite occurring rarely. The strategic elimination of worst-case scenarios matters more for satisfaction than optimizing typical-case experiences.

For Developers: The peak-end rule explains why graceful degradation and error recovery receive disproportionate design attention. When failures occur, how systems handle them determines whether negative peaks become catastrophic memories or manageable incidents users quickly forget. ChatGPT's error handling demonstrates this—when responses fail, the system preserves conversation context, explains issues clearly, and enables easy retry. These recovery features transform potential negative peaks into minor bumps users barely remember because final experience (successful retry) dominates memory.

How It Works in Practice

Effective peak-end design begins with identifying emotionally intense moments in user journeys—first interactions, critical achievements, major task completions, and error encounters. These moments receive disproportionate design investment ensuring they create positive peaks or avoid negative peaks. Duolingo celebrates learning achievements through animated rewards and streak acknowledgments creating positive emotional peaks that dominate memory more than routine lesson completions comprising majority of usage time.

Strategic ending design transforms final interactions into satisfying conclusions regardless of preceding experience quality. Every significant user action—completing forms, finishing tasks, ending sessions—deserves intentional closure design. GitHub's pull request merge provides exemplary ending—after merge completion, users see clear success confirmation, summary of changes integrated, and optional prompts for next actions (delete branch, create new PR). This satisfying conclusion creates positive memory of entire PR workflow despite potential frustrations during code review and iteration phases.

Negative peak prevention requires identifying potential failure modes and designing sophisticated error handling eliminating catastrophic experiences. Rather than minimizing error frequency alone, focus prevents worst-case outcomes creating lasting negative memories. Notion's real-time sync with offline mode prevents data loss negative peaks—even with network issues, work persists locally and syncs seamlessly when connectivity returns. Users never experience catastrophic "lost work" negative peak that would dominate product memory.

Recovery design transforms unavoidable negative peaks into manageable incidents through clear communication, easy correction, and positive resolution. When Stripe payment processing fails, the error message explains exactly what happened, preserves all entered information, and provides specific resolution steps. The successful retry becomes the end moment users remember—the initial failure fades to minor bump rather than lasting negative peak because final experience resolved positively.

Artificial peaks create memorable moments in otherwise smooth but unremarkable experiences. LinkedIn's "profile views" notifications and skill endorsement notifications create positive micro-peaks throughout usage—moments of social validation producing emotional intensity absent in typical profile browsing. These manufactured peaks make the product feel more engaging and memorable despite most usage consisting of unremarkable content consumption and connection browsing.

Get 6 UX Principles Free

We'll send 6 research-backed principles with copy-paste AI prompts.

  • 168 principles with 2,098+ citations
  • 600+ AI prompts for Cursor, V0, Claude
  • Defend every design decision with research
or unlock everything
Get Principles Library — Was $49, now $29 per year$29/yr

Already a member? Sign in

Was $49, now $29 per year$49 → $29/yr — 30-day money-back guarantee

Also includes:

How It Works in Practice

Step-by-step implementation guidance

Premium

Modern Examples (2023-2025)

Real-world implementations from top companies

Premium
LinearStripeNotion

Role-Specific Guidance

Tailored advice for Designers, Developers & PMs

Premium

AI Prompts

Copy-paste prompts for Cursor, V0, Claude

Premium
4 prompts available

Key Takeaways

Quick reference summary

Premium
5 key points

Continue Learning

Continue your learning journey with these connected principles

Part I - FoundationsPremium

Flow

Flow (Csikszentmihalyi 1975, 1990) represents optimal experience state where challenge-skill balance, clear goals, and i...

Advanced
Part I - FoundationsPremium

Goal-Gradient Effect

Goal-Gradient Effect (Hull 1932, Kivetz 2006) demonstrates motivation increases approaching completion, with coffee shop...

Intermediate
Part I - FoundationsPremium

Recognition Rather Than Recall

Recognition beats recall consistently with 85-95% accuracy versus 35-50% (Tulving 1973), requiring substantially less me...

Beginner
Part II - Core PrinciplesPremium

Error Prevention

Nielsen's heuristic #5 (1994) demonstrates prevention reduces support costs 40-60%, improves completion 30-50% through c...

Intermediate

Licensed under CC BY-NC-ND 4.0 • Personal use only. Redistribution prohibited.

Previous
Goal-Gradient Effect
All Principles
Next
Zeigarnik Effect
Validate Peak-End Rule with the AI Design ValidatorGet AI prompts for Peak-End RuleBrowse UX design flowsDetect UX problems with the UX smell detectorExplore the UX/UI design glossary