- Start with the new action or decision, not the old video’s scene order.
- Reuse visuals only after checking that the screen and claim still match.
- Keep a follow-up announcement separate from a correction to an existing tutorial.
A product shipped a reporting dashboard last quarter. This month customers can schedule the report. The original video may already contain the right introduction and a clear view of the dashboard, yet replaying the first launch would hide the reason for this follow-up: customers can now choose a delivery time.
Decide whether this is a new video or a correction
Make a new release video when the old one still answers the question it was made for. Reuse its approved material selectively. If the old video now gives incorrect instructions and its audience has not changed, correct that video instead. A follow-up announcement should not leave an obsolete tutorial in circulation unexamined.
Write one sentence that only the new release can support. In this example: “A report owner can schedule delivery after choosing a reporting interval.” Verify those controls before drafting either the narration or an animated callout.
Inventory the old cut by scene
Keep a screen only if its navigation, terminology and visible result are current. Keep a graphic only if it still explains the same relationship. Replace a screenshot when it would send the viewer to an old menu. Check dates, plan requirements and calls to action separately; these often expire before the visuals do.
Start the new brief with an owned conversation reference when the source project is yours. The example below shows the named reference in the composer. Its presence identifies the source; your instructions decide what belongs in the new story.
Write a brief around the difference
For example: “Use the earlier dashboard introduction only long enough to orient existing customers. Show the new scheduling control using the current screenshot. Explain who receives the report and where the owner can check the schedule. Use this month’s release note for the facts.”
Keep new and returning customers distinct. An existing customer may need only the changed step. A new user may need the original tutorial first. The feature announcement workflow can serve the former, while release notes to video can supply the source for a broader update.
Review with the first video open
Play both cuts through once. Can you tell what is new by the first meaningful example? Can the customer perform the new action from the follow-up alone? If a reused scene suggests a feature still works as it used to, replace that scene even when its production quality is excellent.
You just read it. Now watch it.
ngram turns this post into a short explainer video: scenes, voiceover, and motion graphics included.






