The one number that beat the whole roadmap
How Duolingo went from stalled to 50M+ daily users by optimizing less — and how to find your own compounding metric.
Growth stalls, and the reflex is to add. Another channel. Another feature. Another twelve experiments in the backlog, each pointed somewhere different.
Around 2020, Duolingo was flat at roughly 5 million daily active users. Not short on ideas, not short on engineers, not short on things to ship. Flat anyway.
What broke the plateau wasn’t more. It was picking the one number that compounds and aiming everything at it. Four years later they were past 50 million daily users.
Here’s the mechanism, the actual experiments, and how to find your version of that number.
A 30-metric dashboard is a 0-metric dashboard
When growth flattens, broadening feels like the responsible move. More surface area, more chances something lands. Spread the bets, protect the downside.
It fails for a mechanical reason: nothing gets hit twice. Twelve experiments across twelve metrics produce twelve one-off bumps that each decay on their own schedule. Nothing accumulates because nothing is pointed anywhere long enough to accumulate.
Open your dashboard and look at what’s on it. Installs. Signups. Downloads. Virality coefficient. Feature adoption. Push volume. Trial starts. All rendered at the same size, all implicitly labelled important. A dashboard where everything matters equally can’t tell you what to do on Monday — it can only tell you what happened.
Duolingo’s move was subtraction. Find the single metric that drags the rest along, and stop pretending the other twenty-nine deserve equal attention.
CURR is a rate, not a count
The metric they landed on: if a user is active today, what’s the probability they’re back tomorrow? Next-day return probability. Duolingo calls it CURR — current user retention rate.
The distinction that matters isn’t the name. It’s rate versus count.
Counts make headlines. A signup number, an install number, a download record — you bank it once and it’s spent. A rate applies itself to every cohort you will ever acquire, every day, indefinitely. Improve it and you’ve improved the yield on all future acquisition without touching acquisition.
When Duolingo’s team looked at what actually moved DAU, CURR moved it roughly 5x more than any other input — more than installs, more than virality, more than downloads. That’s their read on their own data, not a law of nature. But it’s the finding that justified pointing the entire company at one number.
And the arithmetic behind it is the part that transfers. Improving “do they come back tomorrow” by 1–2% a month is exponential over a few years. A feature launch is linear, and then it decays.
Many small bets, one target
The discipline is the boring part, which is why most teams skip it: every experiment aimed at the same metric. Not distributed across the roadmap. Not one per squad. All of them, at CURR.
Three of the plays:
They moved the streak counter to the top of the app. DAU up ~3%. A UI change measured in pixels, aimed squarely at return behavior.
They shipped a “streak wager” — commit to keeping your streak, put something on the line. 14-day retention up ~5%, in-app purchase revenue up ~600%. A commitment mechanic pointed at coming back tomorrow.
They A/B tested guilt. After about five ignored days, the notification opens with “These reminders don’t seem to be working…” — and then the reminders stop. Even the tone of a push notification became an experiment on return probability.
None of these is a stroke of genius. The streak counter is a position: fixed. The value isn’t in any single test — it’s that they were all cheap, all repeatable, and all nudging the same number by 1–2% a month.
That’s the whole trick. Alignment beats cleverness over a four-year window.
Why it compounded instead of spiking
The results, as reported: DAU from ~5M to 50M+. Churn in core markets from 47% down to 28%. And 55% of users now return the very next day. Over roughly four years.
No hero quarter in there. No single launch you could point at. That’s the tell that the mechanism was real — they optimized a rate that feeds on itself rather than a sequence of one-off launches, so each month’s gain started from the previous month’s baseline.
Worth being honest about the limits: this is one company, self-reported, in a habit-forming consumer product where daily return is the obvious behavior to chase. The transferable part is the method, not Duolingo’s exact definition of CURR.
Find your one compounding metric
Three steps, and you can start on Monday.
1. Pick a rate, not a count. Ask which single behavior, if it happened more reliably, would drag everything else up with it. For a habit app it’s next-day return. For B2B SaaS it’s usually weekly active teams rather than users, or the repeat rate on your core action. If the candidate metric can be banked and spent, it’s a count — keep looking.
2. Kill the dashboard. One north star, a handful of drivers underneath it, a few guardrails so you notice when you’re breaking something. Everything else moves to on-demand, not on-display.
3. Aim the portfolio. Small, repeatable experiments, all pointed at that one number. And change what you judge yourself on: moving it 1–2% a month, not shipping count.
Growth isn’t 40 optimizations. It’s one compounding metric, moved a little, every month.