Blog/The developer journey
Activation: video that gets developers to a first success
They signed up and nothing works yet. The one-task video that gets a new developer to a working result, and how to measure it.
Kevin Blanco··6 min read·Activation
The short answer
An activation video gets a developer who has signed up to a first working result. It covers one task from start to finish, runs the real product, shows the error people hit first, and ends with the result working. Measure time to first success and completion, and the support tickets it prevents.
01
Who's watching
This viewer just signed up, and nothing has worked yet. The first working result is the line between a developer who stays and one who doesn't come back.
They aren't browsing. They're doing a task, probably with the video on one monitor and an editor on the other.
02
What a good activation video looks like
- 01
One task, one result
If the title needs an "and", make two videos.
- 02
The real run
A real terminal, a real cursor, code large enough to read on a phone.
- 03
The error everyone hits
Fix the first failure on screen. It's the part viewers came for.
- 04
Easy to resume
Chapters, and a repo or snippet link under the video, so someone can pause, copy and carry on.
03
The call to action that fits
The ask at the end should match what this viewer is ready to do. Asking for more than that loses them. Asking for less wastes the video.
The ask that misses
"Explore the docs to learn more."
The ask that fits
"Run the snippet below. When it prints your first result, you're set."
04
What to measure
Time to first success
Sign-up to result
How long from creating an account to the first working call or deploy.
Completion
Last step
The share of viewers who reach the end of the task.
Tickets
On this task
Support questions about the task should drop after the video.
This stage has the clearest number in the whole journey, so use it. If the video works, time to first success falls.
05
When results show up
These are rules of thumb from our own work, not benchmarks. Your audience and your volume will move them.
Days 1 to 7
Completion and drop-off
Where viewers leave tells you which minute to fix.
Weeks 2 to 3
Time to first success
Compare people who saw the video with people who didn't.
Month 2
Tickets
Check whether questions about the task have dropped.
06
The usual mistake
07
The rest of the journey
The developer journey, in video
- 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 is an activation video?
A video that takes a developer who has signed up through one task to a first working result, using the real product and including the error people hit first.
How long should an activation video be?
As long as the task takes. Most single tasks fit in a few minutes. If yours runs longer, split it into two videos or add chapters.
What is time to first success?
The time between a developer creating an account and getting a first working result, such as a successful API call or deploy. It's the clearest measure of whether an activation video works.
How do I choose which task to cover?
Look at the first questions new developers ask support, and at where sign-ups stall. The task with the most stalls is the first video.
How long until activation video shows results?
Faster than any other stage: completion within days, time to first success within two to three weeks, and ticket changes within about two months. These are rules of thumb.
DevReel
How we do it at DevReel
For activation we find the one task new developers stall on, usually from the first support questions, and make the shortest video that gets them through it.
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 where new developers stall. We'll make the video that gets them through 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→