Behind the product: Duolingo streaks

Jackson Shuttleworth is a Group Product Manager at Duolingo leading the retention team, which owns the streak feature. The conversation traces the streak's evolution from an XP-based goal to a one-lesson mechanic, and covers the experiments, flexibility mechanics, notifications, and team operating practices behind its growth.

01Key learnings

• Streaks are an engagement amplifier, not a substitute: first make sure the core product is something users want to return to daily before layering a streak on top.
• Choose a unit of use that matches real engagement; simplifying the streak to one lesson kept users, but dumbing it down to one exercise lost users who were least engaged.
• Focus effort on the first seven days, since loss aversion appears to kick in once a streak reaches about seven days and retention flattens out after that.
• Give generous flexibility early, such as two free streak freezes at the start, but tighten it for long streaks so users aren't trained to take days off.
• Run many small experiments, including copy tests, since tiny changes like replacing 'Continue' with 'Commit To My Goal' can produce large wins; Jackson notes roughly half of experiments lose.
• Protect the sanctity of the feature by keeping a clear owner or gatekeeper who guards against cheapening the streak and against bloat from too many concepts.
• Use revealed behavior over stated preferences: scheduling practice reminders 23.5 hours after the last session outperformed user-chosen reminder times.
• Organize teams around a clear metric like current user retention rate rather than a single feature, and plan iterations months ahead with engineering and design dependencies mapped.

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.