Crossing the Chasm via Single Use-Case Focus
Find the one behavior users already love, then rebuild the whole product around it.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 75%
After Musical.ly launched as a broad short-form video platform with lackluster growth, the team noticed a recurring Thursday-night spike in downloads. Digging into user research, they traced it to a TV show, Lip Sync Battle, whose fans were searching app stores for 'lip sync' and finding Musical.ly because of aggressive keyword stuffing in its title. Rather than staying a general-purpose video app, Alex Zhu and Lewis Yang went all-in on lip syncing: they rebuilt onboarding around it, curated the feed to surface the best lip-sync content, and used notifications and challenges to make lip syncing a habitual behavior. That single-use-case focus is what triggered the platform's breakout growth.
Origin
Musical.ly's team, led by Alex Zhu and Lewis Yang, discovered the pattern while investigating a mysterious Thursday-night download spike tied to the Paramount Network show Lip Sync Battle.
Core principles
- 01Growth signals hidden in usage data often point to an unplanned use case worth doubling down on.
- 02A broad platform needs one flagship use case to cross the chasm before it can support diverse use cases.
- 03Onboarding should teach and reinforce the one behavior you want new users to adopt.
- 04Habitual return is engineered through recurring prompts (challenges/notifications), not left to chance.
How to run it
- 1
Mine Usage Data for Anomalies
Look for unexplained recurring spikes or patterns in your growth data — these often reveal an organic use case you didn't design for.
- 2
Diagnose the Root Cause
Go directly to users (support tickets, fake test accounts, interviews) to understand exactly why the anomaly is happening before acting on it.
Pro tip Alex Zhu created fake accounts to personally interact with users and understand behavior firsthand.
- 3
Commit to One Flagship Use Case
Choose the single use case with the clearest organic pull and redesign the product's onboarding and messaging entirely around it, even if it narrows your positioning.
Watch out This means consciously deprioritizing other use cases the product could theoretically support.
- 4
Curate the Feed Around the Winning Use Case
Surface the best examples of the chosen use case to new users so they immediately understand what's possible and how to succeed at it.
- 5
Engineer Habitual Return
Use recurring prompts like daily notifications and themed challenges to convert passive consumption into regular content creation.
In the wild
Musical.ly noticed Thursday night download spikes, traced them to the TV show Lip Sync Battle, and rebuilt onboarding, feed curation, and notifications entirely around lip-sync video creation.
→ The app hit #1 in the US iOS App Store within two months and never left the top 40 apps for years afterward.
Common mistakes
Staying Too Broad Too Long
Musical.ly's predecessor Cicada tried to serve a broad educational video use case and failed because it didn't align with a natural, self-reinforcing user behavior.
Missing the Signal in the Data
Without close user research, the team could easily have missed that a TV show was driving organic search demand for a specific keyword.
Is it for you?
Best for
Early-stage consumer products with multiple possible use cases and flat growth despite decent retention.
Not ideal for
Products already past product-market fit and looking to expand into adjacent use cases.
From the transcript
“they decide a couple things. One, we need to make a decision and go all in on a particular use case, like classic enterprise software…”
From the episode
TikTok