Who this is for: Teams creating interface explanations from still assets.
What to prepare
- Matching full-frame screenshots
- State and prototype-status notes
- Exact changed values
- Evidence for any requested interaction
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: explain two supplied states of fictional request R-062 in 30 seconds. Begin with the full unassigned screenshot, crop toward its owner field while retaining the identifier, then use a labeled comparison cut to the screenshot showing Example reviewer assigned. Highlight the changed field through a clearly editorial callout. Do not fabricate a dropdown, save button or pointer action between the images. Close with “State comparison — interaction not demonstrated.” Use matching sample data and preserve any prototype label.
Identify suitable source material
Useful inputs include full-resolution screenshots of the same object, exact labels, capture conditions and a note explaining what each state proves. Matching viewport, theme, account and sample records help the film feel like one coherent explanation.
Unrelated screenshots, low-resolution text crops or concept screens without status labels are weak inputs. A designer can improve composition, but cannot recover missing factual evidence or make tiny text reliable by enlarging it indefinitely.
Choose an honest motion language
Camera movement changes where the audience looks. An annotation explains what they see. A simulated click or drag asserts product behavior. Separate these categories in the brief so visual polish does not quietly become an unsupported capability claim.
In the illustrative example, the two stills support a comparison. They do not establish how assignment is performed or how long it takes. Request a recording or intermediate states if the action itself is the central lesson.
Adapt to the explanation
For a dashboard, use a question-led reading order across supplied values. For a settings comparison, keep all unrelated fields matched and explain one difference. For a prototype, maintain a concept label through every crop and avoid release language.
Choose a wide-detail-wide sequence when viewers need orientation. Use a static paired layout when simultaneous comparison matters more. Neither treatment requires a fabricated interaction; the useful motion is the change in attention.
Review what the motion implies
Watch the planned sequence without narration and describe the behavior it appears to show. If it suggests automatic data transfer, a new control or a successful save absent from the evidence, change the edit or the framing.
Inspect annotations for resemblance to native toasts and buttons. Check full source frames for sensitive information that a later camera move could reveal. This page supplies an illustrative production brief and does not claim the example was rendered or tested.
Review checklist
- Every interaction implication has evidence.
- Camera and callout motion remain clearly editorial.
- Object identity is preserved across states.
- Crops do not remove essential context or concept labels.