Put Version Context in a Product Demo Before the UI Changes

Decide which version detail affects the claim

Imagine a fictional scheduling app called Slateway. Its team records a demo of sending a draft for review. The workflow is available to workspace owners in the current release, but the team is testing a different review menu in a private beta.

The public video should use the current stable interface and the owner role. The internal record should capture the product build, date, environment, role and sample workspace. The public caption may only need “Current owner workflow” if that is the truthful scope. A long build string across the video could distract from the task; omitting the role would be worse.

This is a sample ledger for a fictional product. Do not copy the labels into a real video without checking the current implementation and rollout state.

Capture a complete task from one environment

Record the start, action and result in the same safe account whenever possible. For Slateway, show the owner opening the draft, selecting a reviewer and seeing the pending state. Do not use a beta menu for the first shot and a stable release for the result because they look cleaner together.

If a test workspace is required to avoid exposing customer data, label that internally. It can still show real product behavior, but the reviewer must verify that the flow matches the public version. Never edit a test-only feature into a production claim.

Keep the source recording untrimmed. A later editor may need the screen just before the selected action to verify which role was signed in. A thirty-second export alone can hide the clue that the visible menu came from an admin account.

Keep the public qualifier short and useful

The viewer needs enough context to act, not every internal identifier. A caption such as “Workspace owners can send a draft for review” is useful if true. A badge saying “new” will age quickly and may be wrong after the next release. A date in the article or description can help with a tutorial whose exact clicks matter.

Place qualifications beside the claim they limit. If the first line says “anyone can approve a draft” and a tiny final card says “owners only,” the video has already misled many viewers. Rewrite the hook instead of shrinking the exception.

Check the destination too. A video recorded in one version should link to a current help page that either still matches or clearly explains the new path. The content team should own both the media and the link review.

Create a repeatable version ledger

For every short, retain an internal row with source file ID, app build or release, capture date, account role, feature flags, approved claim, published URL and review owner. Add the destination-specific export names. If the team later gets a report that a menu has moved, it can filter the ledger instead of opening every MP4.

Do not put secrets, customer IDs or private workspace URLs into the public metadata. The ledger can keep a safe internal reference that the product owner understands. Keep it access-controlled if it includes deployment or customer details.

When two teams share a library, include the owner of the public claim as well as the editor. The editor can verify that the frame is sharp; the product owner can verify that the role and feature flag still describe current access. Both approvals should refer to the same export hash or asset version, not two files with similar names.

The product tutorial series guide helps plan multiple lessons. This ledger is smaller and operational: it ensures every single tutorial knows which version it depicts.

Build the short after the capture is approved

Video Hook & Demo uses an owned product recording. Supply the approved Slateway clip and a hook scoped to the version and role it shows. The current format replaces the source recording's original audio with library music or silence; plan the visual explanation so the result remains understandable without the captured speaker.

Review the returned video at phone size. Can the draft-review state be read? Does the hook promise a role that the screen never showed? Does the CTA reach the current page? Store the returned asset ID in the version ledger. A generation job ID alone does not identify every published variant.

If the product changes before scheduled publication, pause the affected short and recheck the source. The fact that the recording was approved last week is not proof that it still represents today's interface.