Clarity Over Cleverness in Feature Design
Comprehensibility is a retention lever — make the design a plain distillation of what you're tracking.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 88%
Duolingo repeatedly found that the more easily users understand a feature, the more retentive it is — even for something as apparently obvious as a streak. Many users don't grasp how streaks or freezes work. So they lead with plain number-forward design ('form follows function') over evocative metaphor, and win with tiny copy changes that simply explain the mechanic. Delight is preserved, but never at the expense of comprehension.
Origin
A recurring design principle Jackson Shuttleworth's team surfaced across copy tests, redesigns, and international UX research (including a metaphor that failed in India).
Core principles
- 01Comprehensibility directly increases retention
- 02Your users are not tech workers — design for all ages and cultures
- 03Form should follow function: show the thing you're actually tracking
- 04Metaphors (a flame) don't travel across cultures; the underlying number does
- 05Clarity and delight are not in tension — celebrate without obscuring
How to run it
- 1
Diagnose whether users actually understand the feature
Don't assume an 'obvious' mechanic is understood. Use support reports and international UX research to find comprehension gaps.
Pro tip Duolingo found many users didn't understand how streaks or streak freezes work at all.
Watch out The flame metaphor for a streak did not resonate at all in UX research in India — metaphors are culturally specific.
- 2
Explain the mechanic in the fewest possible words
Add short, plain copy that states exactly how the feature works, right where users first encounter it.
Pro tip An eight-word explanation of the streak was a massive win worth ~10,000+ DAU.
- 3
Let form follow function in the visuals
Redesign so the UI foregrounds what you're actually tracking (the number) rather than a decorative story element.
Pro tip Duolingo replaced a lit-flame design with an odometer-style number that ticks up, plus a calendar that looks progressively more calendar-like to signal 'daily'.
Watch out Don't get caught up in a beautiful story at the expense of a comprehensible feature.
- 4
Add delight without sacrificing clarity
Layer in celebration (animation, haptics, milestone moments) on top of the clear core, and reserve richer/advanced concepts for users deep enough to handle them.
Pro tip Introduce cooler/advanced streak concepts only after users are past day 7, when they can manage the added load.
Watch out Introducing too many concepts too early universally loses — cognitive load kills comprehension.
In the wild
Jackson's first win at Duolingo was rewriting the small 'flavor' copy at the bottom of the streak screen to explain, in eight words, exactly what a streak is and how you lose it.
→ A massive win of roughly 10,000+ DAU and a top-three current-user-retention win at the time.
The streak was historically represented by a lit flame. A redesign shifted focus to an odometer-style number that ticks up each day, labeled '7 day streak, 8 day streak.'
→ A clearer distillation of what's tracked; Duolingo now leads with the number rather than the flame.
Common mistakes
Assuming an 'obvious' feature is understood
Even a streak — trivial to a tech audience — confused real users about freezes and how days count; unexplained mechanics retain worse.
Prioritizing an evocative metaphor over comprehension
A beautiful flame metaphor failed in India and obscured the tracked number; leading with the plain number (form follows function) retained better across a global, all-ages base.
Is it for you?
Best for
PMs and designers whose user base is broad and non-technical, iterating on a mechanic they assume is self-explanatory.
Not ideal for
Narrow expert-user tools where richer domain metaphors genuinely aid the target audience.
From the transcript
“the more that we can make the feature easily comprehensible to users the more retentive it is”
“start a day to extend your streak but miss a day and it resets”
“form should follow function here”
“we did some uxr in India many years ago and this was something that just like did not resonate at all”
From the episode
Behind the product: Duolingo streaks
Jackson Shuttleworth (Group PM, Retention Team)