Users don't understand your key features
Embed short video demos next to complex features. Users who watch are 3x more likely to adopt the feature.
When to use
You have features with low adoption that are actually valuable. Users just don't know about them or understand them.
Hypothesis template
If we add fill in: 30-second video walkthroughs next to fill in: key features, feature adoption will increase by fill in: target% because video reduces friction and uncertainty.
Method
The problem: You built powerful features but users don't discover or understand them. Your help docs go unread.
What works: Short (15-30 second) video clips embedded directly next to the feature they explain. Not separate tutorial pages — inline, contextual, auto-playing previews.
The result: Features with embedded video walkthroughs see 2-4x higher adoption rates. Users prefer watching over reading.
How to do it:
- Identify your 3-5 most underused but valuable features
- Record a 15-30 second screen recording of each in action
- Embed them in-app, right next to the feature (not in a separate help center)
- Auto-play on mute with a play button for sound
- Add a "Got it" dismiss button so it doesn't show again
- Track: video views, feature adoption after viewing, skip rate
Key insight: 15 seconds is enough. If you can't show the feature's value in 15 seconds, the feature might be too complex.
Success metrics
- •Video play rate
- •Feature adoption rate after viewing
- •Skip rate
- •Support tickets for featured features
Prerequisites
- Screen recording tool
- A way to embed video in your UI
- Analytics on feature usage
Common pitfalls
- •Making videos too long (30 seconds max)
- •Auto-playing with sound
- •Not tracking which videos actually improve adoption
- •Creating videos for obvious features
Source: Common pattern. Inline video walkthroughs consistently outperform text documentation.
Suggested ICE scores
Ready to run this experiment?
Sign up free to use this playbook with step-by-step guidance and track your results.