Feature Discovery Videos: Show Users the Features They Miss

Feature discovery videos are short demos (often about 30 seconds) that show one capability users overlook. Place them in release notes, lifecycle email, and in-app surfaces next to the feature itself. Adoption rises when people see the clicks, not when the changelog only names the ship date.

Why shipped features stay invisible#

Users learn a happy path and stop exploring. New navigation items and power filters never enter the routine. DemoVexa's why DemoVexa note on feature discovery says a 30-second demo of each feature gets the ones people miss in front of them: in emails, release notes and in the app.

That is different from a launch anthem. Discovery content is local, specific and easy to replay. For structuring the seconds inside the clip, see how to structure a 30-second feature demo. This post is about placement and the backlog.

How to build the discovery backlog#

1. List features with low usage relative to how many accounts have access.
2. Add questions support answers with "it's under …".
3. Add sales promises that customers never activate after close.
4. Rank by business impact if used, then film from the top.

Making the clips in DemoVexa#

Use Feature Demo. Brief: show the entry point, the key click, the outcome. Keep formats ready for email (16:9) and in-app players. Script tightly; cut throat-clearing lines (Brief, Script).

Export with captions so muted in-app autoplay (if you use it) still teaches. Publish drafts social posts when the same clip doubles as a release announcement (Publish).

Placement that drives discovery#

• Release notes: embed or link under the feature bullet
• Email: one feature per message for lifecycle or tips campaigns
• In-app: empty state, badge popover, or "new" coach mark that opens the clip
• Sales enablement: the same URL in the handoff doc so CSMs reinforce activation

Mistakes that waste discovery videos#

• Shipping a two-minute montage titled "October updates" and expecting every feature to be found inside it
• Showing the feature without showing how to open it from the default home screen
• Using marketing adjectives instead of control names
• Leaving the clip only on YouTube while release notes stay text-only
• Never checking whether usage moved after the tip email went out

Measure discovery with feature adoption among eligible accounts and with "I didn't know we had that" replies, not with raw view counts alone.

Tie discovery to the release train#

When a feature merges, add a checklist item: draft Feature Demo brief, record, embed in release notes, schedule tip email, update in-app entry. Same-day launch videos are covered in the release demo workflow. Discovery clips are the quieter twin of that habit: less fireworks, more "here is the click".

If several tips queue up, build them as a batch overnight so design and length stay consistent (overnight batches).