Blog/The developer journey
The developer journey, in video: a map
Six stages, six jobs. A video that tries to do all of them does none well. Here is the map, and how to use it.
Kevin Blanco··6 min read·Every stage
The short answer
Developers move through six stages: awareness, evaluation, activation, adoption, retention and advocacy. Each stage needs a different video, a different call to action and a different number. One video can't serve all six, so decide the stage before you decide the idea, and attach a metric to each.
01
One video, six jobs
Teams often ask a single video to find strangers, convince evaluators, onboard new users and delight customers, all at once. It does none of them well.
A developer's relationship with your product has stages, and the right video changes at each one. The viewer's question changes, so the picture, the length, the ask and the number all change with it.
02
The map
| Stage | The viewer asks | The video | The call to action | The number |
|---|---|---|---|---|
| Awareness | Is this for me? | A problem they feel, shown solved fast | Watch the next one, subscribe | Qualified views |
| Evaluation | Will it work for my case? | A real use case and one honest limit | Try the sandbox, read the quickstart | Clicks to docs or sandbox |
| Activation | Can I get it running? | One task, start to first success | Run the snippet | Time to first success |
| Adoption | What else can I do with it? | Use cases by role, in a series with a path | Try the next feature | Weekly active developers |
| Retention | Is it worth staying? | Releases, advanced patterns, migrations | Read the upgrade notes | Tickets on covered topics |
| Advocacy | Would I recommend it? | Community builds, talks, customer engineers | Share your build | Mentions and referrals |
03
How to use the map
1
Pick the stage
Before the idea. Which stage is this video for?
2
Name the viewer
One sentence: who they are and what they're stuck on.
3
Write the ask first
The call to action sets what the video has to do.
4
Choose the number
The one metric you'll check, decided before you record.
The order matters. Teams that start from the idea tend to end up with videos nobody can place on the map.
04
A post for each stage
Each stage has its own post: who's watching, what a good video looks like, the call to action, the numbers, and how long results take.
The series
- The developer journey, in video: a map6 min →
- Which stage should your next video serve? A ten-minute audit5 min →
- Awareness: video for developers who don't know you yet6 min →
- Evaluation: video that helps developers decide6 min →
- Activation: video that gets developers to a first success6 min →
- Adoption: video that moves developers from trying to using6 min →
- Retention: video that keeps developers and grows usage6 min →
- Advocacy: video that gets users talking about you6 min →
FAQ
Questions people ask
What are the stages of the developer journey?
We use six: awareness, evaluation, activation, adoption, retention and advocacy. Other frameworks name them differently, but the jobs are the same: be found, be believed, get to a first success, give reasons to stay, keep and grow usage, and earn recommendations.
Why can't one video serve every stage?
The viewer's question changes at each stage, and so do the right length, the right proof and the right call to action. A video built for a stranger will bore a customer, and a video built for a customer will lose a stranger.
Which stage should I start with?
Start where your biggest gap is. If developers sign up and don't get anything working, start with activation. If nobody finds you, start with awareness. The audit post in this series helps you find the gap.
What metric goes with each stage?
Qualified views for awareness, clicks to docs or the sandbox for evaluation, time to first success for activation, weekly active developers for adoption, tickets on covered topics for retention, and mentions and referrals for advocacy.
How long until developer video shows results?
It depends on the stage. Activation tends to show first, often within a few weeks. Advocacy is the slowest, usually a quarter or more. These are rules of thumb, not benchmarks.
DevReel
How we do it at DevReel
Every video we make starts with a stage, a viewer and a number. The stage decides the idea, the ask and the length, and the number decides whether the video was worth making.
Cloudinary's videos usually average around 400 views. Ours passed 9,000 in the first week. For ngrok, watch hours tripled and subscribers went from about 450 to over 800 in the first week.
Cloudinary views
9,000+
in the first week, against a usual ~400
ngrok watch hours
3×
subscribers from ~450 to 800+ in the first week
Now the hard part
Tell us which stage of the journey your videos miss, and we'll plan the one that fills it.

Kevin Blanco founded DevReel. He has made 500+ developer-tool videos and spoken at 80+ developer conferences.
Keep reading
The developer journey/Every stage
Which stage should your next video serve? A ten-minute audit
List your last ten videos, mark the stage each one serves, and see where the gaps are.
October 16, 2026·5 min read→The developer journey/Advocacy
Advocacy: video that gets users talking about you
Developers recommend what makes them look good. How to give them something worth sharing.
October 9, 2026·6 min read→The developer journey/Retention
Retention: video that keeps developers and grows usage
Release videos, advanced patterns and migration guides for the people who already use you, and the support questions they answer.
October 2, 2026·6 min read→