Peak-end rule

The peak-end rule states that people evaluate an experience based on how they felt at its emotional peak and at the end, rather than on the average quality across the whole experience. In UX it means the worst and last moments matter most.

What is the peak-end rule in UX design?

The peak-end rule is a cognitive bias identified by psychologist Daniel Kahneman and his colleagues. It states that people do not evaluate experiences based on the average quality across the entire duration. Instead, they judge experiences primarily based on how they felt at the most intense moment, the peak, and at the end. A brief period of frustration that represents the worst moment of using a product will disproportionately shape how users remember the overall experience.

Why does the peak-end rule matter for UX design?

The peak-end rule means that creating a uniformly mediocre experience is not enough to generate positive memories, and that a single moment of significant frustration can overshadow many moments of smooth interaction. For UX designers, this has two implications: eliminate the worst moments in any user flow because they will be remembered disproportionately, and deliberately design strong positive endings to flows because the final impression anchors the memory of the entire experience.

What are examples of the peak-end rule in interface design?

A checkout flow that works smoothly until the final payment step, which produces an unclear error, will be remembered primarily for that frustrating ending. An onboarding flow that ends with a congratulatory message and a clear first action creates a positive peak at the end that shapes how users remember the entire onboarding. A form that validates fields inline and shows a genuine confirmation message after submission ends on a positive note that counteracts minor friction earlier in the flow.

How to apply the peak-end rule in UX design?

Map user flows and identify the most likely pain points, particularly those that could create strong negative peaks. Eliminate or reduce these moments before optimizing other parts of the flow. Design strong endings for key flows: confirmation screens, success states, and completion messages that feel genuinely celebratory rather than perfunctory. Use empty states and onboarding endings as opportunities to create positive emotional peaks that shape how users remember their first experience with the product.

Related terms

Related guides