Software feature launch · Production guide
Update launch screenshots and demos after a UI label changes
Use an asset register containing release version, screenshot name, video timecode, caption key and destination. Change one label and list every affected output.
Input and decision
Start with the release or screen ID, then find every hero, social graphic, help article, video and subtitle that displays the old control.
Set up the comparison
Verify an actual destination after replacement. A stale CDN asset, thumbnail or localized label can still show the old UI even when the editable design is current.
Make the comparison
Follow the old label into the live page, encoded video and test email. Mark each destination complete only after opening the replaced file there.
Worked record
The downloadable worksheet includes the records below and a blank row for your own project.
| Asset | Release version | Old label | Replacement | Destination checked |
|---|---|---|---|---|
| Product page hero | Screen v1 | Old control label | Screen v2 | Open published page |
| Demo caption | Video v1 | Old button name | Updated cue | Play final encoded clip |
| Newsletter image | Release v1 | Old screenshot | New crop | Send test preview |
Check the result
Check rendered captions as well as the image. A new screenshot in the launch page does not repair a stale label burned into a demo clip.
Hand off the revision
Keep a receipt for each changed destination, including the published page, encoded demo and rendered test email.
Review question
How do I confirm every delivery actually displays the new button name?
Open the published web image, encoded subtitles and rendered test email separately. Record each new revision only after checking its final destination.
Use the task on your own brief
Use a copy of the worksheet to keep the project’s source files, reviewed options and decisions together.