People do not remember experiences as averages. They remember how they felt at the most intense moment and at the end. The Peak-End Rule was established through research by Daniel Kahneman and colleagues, including a 1993 study with Barbara Fredrickson where participants rated the discomfort of two variants of a cold pressor task. The second variant was objectively worse (it included all of the first variant plus additional discomfort), but participants preferred it because it ended more gradually. The ending overrode the objective total of discomfort in memory. This finding has been replicated across medical procedures, customer service interactions, and product experiences.
The Psychology
The implication for digital product design is significant. The overall quality of an experience in terms of its average moment-to-moment quality matters less to user memory and satisfaction than the quality of its peak moment and its ending. A product that is largely pleasant but ends abruptly with a confusing final screen will be remembered as worse than a product with a frustrating mid-experience that ends with a genuinely satisfying confirmation. The checkout completion page, the end of onboarding, the final step of a form submission, and the logout experience all carry disproportionate weight on how users report their experience.
In Product Design
The practical applications are compelling. Invest heavily in the end states of your most important flows. Order confirmation screens should be warm, clear, and reassuring — not just a receipt. Onboarding completion should celebrate and orient, not just check a box. Error recovery flows should end with clear resolution and a forward path, not just the removal of the error message. Publication flows should conclude with a satisfying moment (your article is live, here is the link). Offboarding flows should end graciously (thank you for your time, here is what you can do with your data) rather than with a begrudging confirmation.
How to Apply It
The peak of the experience deserves equal attention. What is the highest-stakes moment in your product's core flow? That moment — whether it is the first time a user sees their data visualised, the moment an order is confirmed, or the moment a file uploads successfully — is the scene users will describe when they recommend your product to a colleague. It should be designed explicitly as a peak: a moment of genuine delight, relief, or satisfaction that is proportionate to the effort the user invested in reaching it. Confetti is an easy example, but the principle is not about confetti — it is about making the arrival feel like an arrival.
Why It Matters
When the Peak-End Rule is ignored, products invest their design effort evenly across all states and flows, which means the ending and peak are no better than the average. This is a missed opportunity. A mediocre end to a good experience undermines the memory of the whole experience. A great end to a mediocre experience partially redeems it. You have the ability to engineer user memory within the real constraints of what your product delivers — that is not manipulation, it is hospitality.
