Product video use case
Captioned Product Video from Observations
Create captioned product video from approved Journey Observations with transcript, accessibility, editorial, source, and publication provenance.
Captioned Product Video from Observations derives a product clip or film from approved Journey checkpoints and preserves the source, edit, caption, transcript, Review, and delivery lineage behind it. The video explains a real product outcome without presenting fabricated interface or private Run evidence.
Define the video job
Choose one audience and outcome: explain a release, teach a workflow, demonstrate value, support recovery, or provide an accessible alternative to an interactive demo. A short focused clip is often more useful than a long universal tour.
Write the narrative from approved product evidence and an audience brief. Do not add metrics, customer claims, or capabilities outside the source dossier.
Select approved Observations
Use a current Journey Version and declared context. Confirm functional outcome evidence before selecting visual checkpoints. Review accessible names, status, motion, focus, and privacy so narration and captions describe the current product accurately.
Never record customer accounts or reusable credentials for outward media. Use sanitized approved fixture data.
Create a video Rendition
Record:
- source Observation sequence;
- scene order and duration;
- crop, zoom, cursor, and highlight treatment;
- narration script and voice source;
- caption file and transcript;
- background audio and mix policy;
- redaction and privacy policy;
- output codec, size, and frame rate;
- thumbnail and poster image;
- approving Decisions.
Edits live in the Rendition. Source evidence remains immutable.
Write accurate captions
Captions must include spoken information and meaningful audio cues, be synchronized, readable, and reviewed against the final edit. Do not generate captions from the draft script after narration or scene order changed.
Provide a transcript that preserves headings and links where the destination permits it. Avoid putting essential instructions only in an audio track or visual annotation.
Describe visual action
Narration should explain product meaning, not every pointer movement. When a visual change is essential and not apparent from dialogue, provide appropriate description in the narration, surrounding text, or an alternate accessible presentation.
Do not rely only on color, screen position, or animation to identify controls.
Control motion
Use restrained zoom, pan, cursor, and transition effects. Respect reduced-motion needs in interactive viewers and provide a non-animated step or transcript alternative when appropriate. Avoid rapid flashing and motion that obscures the product state.
Review by subject
Product owners approve behavior. Marketing or education owners approve narrative and audience. Editors approve pacing and craft. Accessibility reviewers approve captions, transcript, motion, and alternatives. Privacy reviewers approve visible data. Channel owners approve delivery.
An AI voice or caption tool cannot approve its own accuracy. Record exact versions and corrections.
Publish and verify
Deliver the video, captions, transcript, poster, metadata, and links through the intended Channel. Retain payload hashes and receipts where supported. Play the served result with captions on and audio off, then with assistive technology and keyboard controls appropriate to the destination.
Verify the embedded page exposes useful server-rendered title, description, transcript, and related links. Video-only meaning is difficult for search, AI retrieval, and many users.
Refresh from Journey change
Map every scene and caption range to a checkpoint. A changed control name may affect narration and transcript even when pixels barely change. A new permission boundary can invalidate the entire story. A backend-only change may need a keep Decision.
Choose keep, refresh affected segments, reframe, merge, redirect, block, or retire. Preserve historical launch videos as dated artifacts when they are not current instructions.
Measure separately
Track source lineage, current evidence, caption/transcript completeness, Review, and delivery receipts. Use watch time, completion, click-through, and activation only from connected channel analytics. Do not claim improved outcomes from generated duration or asset count.
Maintain translations
Translate captions, transcript, narration, callouts, metadata, and product terminology through an approved locale workflow. Verify the actual localized Journey context so spoken and visible control names agree. Each language variant shares source checkpoints while retaining independent editorial Review and a delivery receipt.
First production
Create a 45–90 second clip from one approved Journey and three checkpoints. Produce captions, transcript, poster, and a text alternative. Complete subject Reviews, publish to one real channel, and verify the served artifacts. Then change one checkpoint and confirm the affected time range becomes refresh-due.
Continue with Launch Media from Approved Product Evidence, Keep Interactive Product Demos Current, and Product Journey Infrastructure for Marketing.
Start with one release-critical Journey.
Define the outcome, declare its state, run it, inspect the evidence, and record the Decision before expanding coverage.