Achievement Badges
Recognize specific accomplishments with badges that reinforce the behaviors you want repeated.
In practice: Duolingo
Achievement badges recognize meaningful progress by turning completed actions into visible accomplishments. By celebrating milestones and building a collection of achievements, products reinforce motivation and give users a reason to keep engaging over time.
A claimable collection of achievements
Duolingo shows earned achievements as a collection of named badges (Weekend Warrior, Sage, Scholar) where common wins sit beside harder milestones. Badges are claimed, not awarded: tapping one plays a celebration animation and pays out gems, so completion feels like an event and the gaps in the set become a to-do list.
Why it works
Badges make progress visible and give users moments of recognition beyond the core activity itself. They turn repeated actions into achievements users can collect, remember, and use as signals of how far they've come.
Behavioral principles
Progress Visibility
Visible achievements help users understand how far they have progressed.
Goal Gradient Effect
Clear milestones encourage users to continue as they approach the next achievement.
Collection Effect
Existing achievements create motivation to complete the set or unlock additional rewards.
Identity Formation
Achievements become part of how users see themselves and their relationship with the product.
Design considerations
Badges should celebrate meaningful behaviors, not just activity volume. Too many superficial rewards shift attention away from the actual goal and make users optimize for points rather than value.
Implementation prompt
Use the pattern above as the reference, then prototype the same behavior in your own product surface.
I want to incorporate the Achievement Badges approach, inspired by Duolingo, into my product. The goal is to translate the behavior design principle into a real product flow, not just a standalone UI component. Please suggest how to implement this in the product: • Explain where this pattern should appear in the user journey • Define the behavior it should encourage • Suggest the data, states, and product logic needed to support it • Include user-facing copy that feels calm, respectful, and appropriate for the product context • Identify risks, edge cases, and ways to avoid pressure or manipulation For implementation, propose: • Product flow changes • Required screens or states • Interaction logic • Success and failure states • A lightweight rollout plan for testing whether the pattern improves engagement.