Stickiness (Made to Stick)
Pride
Recognition and achievement
What it is
Moments of pride capture us at our best — moments of achievement, of being seen, of courage. They are about being recognized specifically for what we actually did.
Why it works
Moments of pride, in the Heaths'' framework, capture people at their best — achievement, recognition, courage. Their guidance is to multiply milestones rather than waiting for the finish line, because a long journey with a single endpoint offers almost no occasions for pride, while the same journey broken into named waypoints offers many. Recognition works through a mechanism designers often miss: specificity. Research on praise, notably Carol Dweck''s work, shows that recognition naming what the person actually did produces persistence, while generic praise produces fragility. The practical consequence is that "Well done!" is close to worthless, whereas naming the specific act and the identity it implies — you showed up four times this week, you are someone who does this now — converts an action into self-concept.
How to apply it in design
Design recognition moments at meaningful intervals — first action, first milestone, first contribution, first comeback. Recognition must be specific to what the user did, not generic.
Where you'll see it
- Milestones named for what the user did, not for a round number
- Recognition that states the specific act before the congratulation
- Waypoints placed early enough that beginners reach one quickly
- Artefacts the user can keep or show — a summary, a certificate, a record
- Comebacks recognised as explicitly as streaks
Example
A pottery school sending after week one: "You showed up four times this week. You're already someone who throws." The recognition names the act and confers identity.
Failure mode
Generic "You did it!" recognition that could apply to anyone reads as automated and actively dilutes pride — worse than no recognition.
When not to use it
Do not manufacture pride for trivial actions. Celebrating that someone filled in a field devalues the currency, so that genuine achievements later carry no weight. Recognition is also misplaced when the user has not really done anything — congratulating a new signup on their commitment is flattery, and it reads as such. Be cautious too in comparative or public form: pride displayed as ranking motivates the top of the distribution and demoralises everyone below it, which in most products is the majority of users.
The ethical line
Pride is engineered dishonestly when recognition is attached to behaviour that serves the business rather than the user — praising someone for a streak of daily logins tells them their attendance is an achievement, when it may only be a habit you profited from. The other failure is recognition as leverage: building someone''s identity around participation and then invoking that identity to prevent them leaving. Recognition should describe something the user would be glad to have done even if the product disappeared tomorrow.
What to measure
Compare continuation rates immediately after a recognition moment against a control that omits it, and check whether users reference the milestone language in their own words later. Also watch for the dilution signal: if lift declines as you add milestones, you are recognising too much.
Frequently asked questions
What is a moment of pride in UX design?
It is one of the Heath brothers' four defining moments: recognising a user for something they genuinely accomplished. The design work is mostly in multiplying milestones — breaking a long journey into named waypoints so there are many occasions for recognition rather than one at the end.
Why does specific praise work better than generic praise?
Because generic praise carries no information. Research on recognition, including Carol Dweck's work on praise and mindset, shows that naming the specific act builds persistence while non-specific approval produces fragility. In interfaces this is the difference between 'Well done!' and naming exactly what the user just did.
How many milestones should a product celebrate?
Enough that a new user reaches one quickly, and few enough that each still means something. The signal you have gone too far is dilution — when adding another milestone no longer changes behaviour, recognition has become background noise.
Are leaderboards a good way to create pride?
They work for the small group at the top and demotivate the majority below it. Recognition measured against the user's own past performance reaches everyone, while recognition measured against other people only rewards the people who were already winning.
Pride in a real redesign
- UX case study: onboarding redesign for a plant & botanical shop
Turned a signup form into meeting a companion: the plant gets a personality and a name before it asks the customer for anything.
- UX case study: enrollment page redesign for an online pottery school
Reframed enrolment as a twelve-screen onboarding, so a beginner feels part of a class of eight before they pay.
Related skills
Source: Heath — The Power of Moments (Part 4)
Practise Pride on a real brief
Quest gives you a client brief that targets this skill and 60 minutes to ship an iteration.