tezvyn:

The Peak-End Rule: Design for Memory, Not Averages

AI-drafted, machine-checkedSource: Wikipedia: Peak–end ruleintermediate

Users don't remember the average of an experience; they remember its most intense moment and its end. This shapes recall of onboarding, support calls, or checkout. The footgun is optimizing for overall 'goodness' while ignoring a painful peak or weak ending.

WHY IT EXISTS Human memory is not a perfect recording. To operate efficiently, our brains use heuristics, or mental shortcuts, to summarize past events. The Peak-End Rule is a heuristic for evaluating an entire experience, saving the cognitive load of recalling and averaging every single moment.

THE MENTAL MODEL An experience isn't a movie we replay frame-by-frame; it's a highlight reel. Memory latches onto two key moments: the point of highest emotional intensity (the peak, whether good or bad) and the feeling at the very end. The duration of the experience and the average feeling across all other moments are largely ignored in our final judgment.

HOW IT WORKS When asked to recall an experience, the brain retrieves the emotional data from the peak and the end. It then forms a judgment by averaging these two points. This is a specific form of 'duration neglect,' where the length of the experience doesn't factor into how we remember it. Information from other moments isn't necessarily lost, but it's not used to form the overall impression.

WHEN TO USE IT Use this rule to consciously design user experiences that leave a lasting positive impression. First, identify and mitigate painful peaks in your user journey, like a confusing form field or an unexpected error. Second, architect a strong, positive final step. This applies to finishing an onboarding flow with a success message, ending a customer support call on a helpful note, or making the final click of a purchase feel rewarding.

WHEN NOT TO USE IT Don't use the Peak-End Rule to justify a fundamentally broken product by just tacking on a nice ending. If the core experience is consistently frustrating, a good ending is a temporary patch, not a fix. It's for optimizing good experiences and mitigating necessary evils, not for excusing a terrible product.

ONE CANONICAL EXAMPLE A famous study had participants submerge a hand in uncomfortably cold water. One group did this for 60 seconds. A second group did the same 60 seconds, but then kept their hand in the water for an additional 30 seconds as the temperature was raised slightly, but was still unpleasant. When asked which trial they'd prefer to repeat, a majority chose the second, longer trial. The less painful ending dominated their memory, making the entire 90-second ordeal seem preferable to the shorter, 60-second one, even though it involved more total time in discomfort.

Read the original → en.wikipedia.org

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.