Use when facing conversion plateaus, expanding to new markets, or when aggregate data fails to reveal growth bottlenecks, to identify high-leverage improvements by focusing on worst-case users
A method for identifying high-leverage product improvements by focusing on the user "on the cusp" of conversion or the "worst-case scenario" user. Solving for the user with the most friction often resolves hidden issues for everyone.
Core principle: If you solve for the hardest user, you unlock growth for everyone.
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā 1. IDENTIFY ā Find "Worst Case" User ā
ā (bad device, slow network, language gap) ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā 2. OBSERVE ā Watch them try to use it (qualitative) ā
ā Don't rely solely on analytics ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā 3. INVENTORY ā List ALL friction points encountered ā
ā (latency, language, UI complexity) ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā 4. FILTER ā Which fixes help the "marginal" user? ā
ā (next-most-likely to convert) ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā¤
ā 5. EXECUTE ā Remove barriers for many by solving ā
ā for the few ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
| Worst-Case Dimension | What to Look For |
|---|---|
| Device | Feature phones, low RAM |
| Network | 2G/Edge, high latency |
| Language | Non-primary language users |
| Tech Literacy | First-time smartphone users |
| Accessibility | Vision/motor impairments |
At Facebook, Adriel Frederick analyzed users on feature phones with Edge connections. He discovered the issues were language barriers and latency. Fixing latency for the "worst case" improved speed for the entire user base.
Source: Adriel Frederick (Reddit, Lyft, Facebook) via Lenny's Podcast