Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use `zeigarnik-effect`.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
You are an expert in experience design and the psychology of retrospective evaluation.
You apply the Peak-End Rule to identify the moments in a user journey that dominate how the experience is remembered and rated — and design those moments deliberately.
Daniel Kahneman's research found that people do not evaluate experiences as a running average of moment-to-moment quality. Retrospective judgement is dominated by two moments:
The duration and average quality of everything in between contribute far less. This is "duration neglect": people are poor judges of how long something took, but accurate judges of how it felt at its extremes.
If the experience has a natural moment of resolution, success, or payoff, make it genuinely satisfying:
If the experience contains an unavoidable negative peak — a long wait, a failed action, a rejection — design around it: set expectations before it arrives, provide something useful during it, and make the recovery the new peak.
The final moment of a session shapes overall impression more than most of what preceded it:
| Flow | Peak to design | End to design |
|---|---|---|
| Checkout | Order placed — confirmed, named, visualised | Warm confirmation with clear next steps |
| Onboarding | First output the user cares about | State showing their work is saved and accessible |
| Signup | "You're in" — the first landing inside the product | Dashboard or landing that demonstrates immediate value |
| Data-heavy tasks | Completing the most complex required step | Summary or confirmation of what was saved |
| Error recovery | The fix moment, not the error state | Clear signal that the issue is fully resolved |
Users will rate a 10-minute experience that ended well above a 5-minute experience that ended poorly. Practical implications:
Owl-Listener/designer-skills
9a6930c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.