Keep a launch video useful after the announcement

A recognizable user problem may remain useful while release-day wording becomes obsolete. Interface controls, eligibility, pricing references and roadmap status can change independently. Mark those dependencies at the scene level.

In an illustrative launch, scene 1 explains a handoff problem, scene 2 shows an owner menu, scene 3 shows the assigned state and scene 4 says “Coming soon.” If public availability changes, the close needs revision. If the owner menu moves, the demonstration may need new assets even though the problem still makes sense.

Record the scene, factual dependency, review trigger, source owner and planned action. This keeps maintenance focused on meaning rather than refreshing dates for appearance.

• Problem scene: depends on the task remaining relevant; review if positioning changes; keep if it still describes the intended viewer.
• Action scene: depends on current controls and permissions; review on the relevant UI release; replace outdated screens and recheck continuity.
• Proof scene: depends on the actual result and status wording; review if behavior changes; revise the claim when necessary.
• Closing scene: depends on availability and destination; review when access changes; update status throughout the asset, not just the link.
• Derived clips: depend on the original scene's facts; identify every reuse so the correction reaches all published variants.

Revise when the central promise remains true and a small number of assets or labels changed. Reframe when the product now serves a different task or audience. Retire an asset when its premise is no longer accurate and a small correction would leave a misleading story.

Do not preserve old footage simply because it was expensive to produce. A polished obsolete interface can teach the wrong action. If it is kept as historical material, make the date and context clear rather than presenting it as a current demonstration.

After editing, repeat the relevant final-artifact checks. New copy can alter timing; a new screen can change cropping; a new CTA can lead to a different destination. Record the substantive revision and its reason.

Maintain the scene register beside source references so another producer can find the right material. A reliable update process begins with knowing which published claims depend on which product facts.