How Duolingo Reignited User Growth
Source: https://www.lennysnewsletter.com/p/how-duolingo-reignited-user-growth ↗
A detailed case study of Duolingo's growth team and how they rebuilt user growth through a sequence of experiments and structural changes — push notifications, the streak mechanic, activation funnels, a new model of experimentation.
The piece is worth reading not for its specific tactics (which are Duolingo-specific and often replicated badly) but for the underlying shift it documents: growth as a disciplined, continuous practice rather than a one-off campaign.
For product direction the most useful takeaway is organisational — Duolingo built a team structure and a decision cadence that made growth work legible, which is rarer than the tactics themselves.
Lenny's Newsletter is full of this kind of reporting; this is one of the sharpest pieces.
Central argument
Mazal argues that Duolingo's user growth revival was not the result of a single product insight or viral mechanic, but of building a repeatable, structured experimentation practice — a growth team with clear ownership, a disciplined cadence of experiments, and a shared model for interpreting results. Specific interventions like the streak mechanic and push notification redesign are presented as outputs of that system, not as the explanation for growth. The central claim is that sustainable growth requires institutional infrastructure, not just clever features.
Critique
The piece is candid about what worked at Duolingo but largely silent on the failure rate and resource cost of the experiments that didn't — which makes the system look more efficient in retrospect than it likely was in practice. More importantly, Duolingo operates at a scale and with a data volume that makes high-cadence A/B testing genuinely viable; the article offers limited guidance on how to adapt this model to products with smaller user bases or less measurable engagement loops, where the same discipline could produce false confidence rather than signal.
Why it matters for product
For a CPO, the most transferable challenge this piece surfaces is organisational legibility: how do you make growth work visible and accountable to the rest of the product organisation without turning it into a metrics-gaming operation? Duolingo's answer — a dedicated team with a defined decision cadence and a shared model for what counts as a valid result — is a structural design choice, not a process tweak, and it has direct implications for how growth, retention, and activation work gets staffed and governed at the leadership level.