Announce a shipped feature in twenty-five seconds
Existing users do not need positioning; they need to know what changed and where to click. This outline opens with the change itself and treats every second spent on build-up as a second stolen from the switch-on instruction.
Launch videos for existing users have a different job from explainers: the audience already knows the product, so the video must respect their time. This outline skips positioning entirely and opens with the change itself, then spends the middle proving the friction is gone and ends with the switch-on instruction.
Use it for release notes worth watching, changelog highlights and in-app announcements. If the feature needs teaching rather than announcing, record a guide instead — this template is intentionally too short to explain a new concept.
Because it is short and structured the same way every time, a release cadence can reuse it weekly: the only new material is the feature, the path through it and the setting that enables it.
Scene outline
4 scenes · ≈25s of 25s
- 01~5s
What shipped
Name the change in one sentence with no build-up.
- 02~9s
In use
The shortest realistic path through the new feature.
- 03~5s
Friction removed
Name the old step that is now unnecessary.
- 04~6s
Switch it on
Where to find it and what to click, for current users.
Example prompt
Create a 25-second square announcement for a scheduled-reports feature in an analytics product. Open by stating that reports can now be scheduled by email. Show choosing a report, setting a weekly Monday send and adding recipients. Point out that the old manual export step is no longer needed. End by telling existing users where to enable it in settings. Direct, collegial tone for people who already use the product.
Best for
- Release announcements
- In-app what's-new slots
- Customer newsletters
Frequently asked questions
- Where should this video live?
- In-app what's-new slots, release notes and customer newsletters — places where the audience already knows the product and is deciding whether the change affects them.
- Should we use it for a paid launch campaign?
- No. Cold audiences need the problem stated first. Use the explainer or a vertical ad for acquisition and keep this one for the installed base.
- Can we mention the feature is in beta?
- Yes, and you should. Put the caveat in the switch-on scene so the expectation is set in the same breath as the instruction.
Ship the announcement with the release
Paste the change, the shortest path through it and the setting that turns it on, then generate and publish.