The working approach
- Draft the promise in one sentence.
- Pair each sentence with visual evidence.
- Read the script aloud while watching the rough cut.
Write around recognition time
The viewer has to recognise a screen before a sentence about it becomes useful. Avoid starting a new explanation at the exact instant a complex interface appears. Allow a short visual arrival, introduce the important change and leave room for the confirmation. This is especially relevant when a caption, native interface label and narration all carry different words at the same time.
Make a two-column script with spoken explanation on one side and observable evidence on the other. Highlight any sentence that promises an outcome absent from the second column. Shorten those claims before recording voiceover. During revisions, update both columns together. A new visual may use a different product term, and an unchanged narration line can accidentally describe a control that no longer appears in the released interface.
A concrete example
Replace “click the blue Save button” with “keep this reference with the rest of your campaign ideas”.
Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.
The mistake to avoid
Long narration forces artificial speed-ups or scenes that outlast their meaning.
If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.
Put it into a production brief
Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.
Review before delivery
- Evidence: can a new viewer identify the result described in the example without being told where to look?
- Reading distance: are the relevant controls and labels understandable at the intended placement size?
- Continuity: does each cut preserve the relationship between the action and its result?
- Accuracy: does the final caption describe the visible product state, including any limits?
The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.
Check the current preview scope →Keep the workflow moving
Choose the next resource based on the decision you still need to make.