Who this is for: Teams with screenshots but no verified screen recording.
What to prepare
- Matching full-frame stills
- Asset status and provenance
- Exact changed values
- Editorial annotation style
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Establish the source
Show the full first screenshot with a production label outside the interface.
On screen:Supplied state: request R-062
- 02
5–11s
Inspect the initial value
Crop toward Owner: Unassigned while retaining R-062 and its subject.
On screen:Initial owner: Unassigned
- 03
11–16s
Explain the comparison
Hold a neutral comparison label; do not animate a fabricated dropdown or click sequence.
On screen:Compare the supplied states
- 04
16–22s
Show the second state
Cut to the matching assigned screenshot with the same object identity.
On screen:Supplied state: Example reviewer assigned
- 05
22–27s
Highlight the difference
Use a clearly editorial annotation pointing to the changed owner field.
On screen:The owner field differs
- 06
27–30s
Close honestly
Return to a stable comparison composition with both state labels.
On screen:State comparison · Interaction not demonstrated
Make it your own
- Supplied states
- Use matching full-frame stills with the same sample object and known implementation status.
- Changed field
- Identify the exact before-and-after values without inventing the missing interaction.
- Editorial treatment
- Specify camera framing and annotations that are visibly separate from native UI.
Prepare source stills
Supply full-resolution before-and-after images and verify that they represent the same sample object. Record whether they are shipping screens or prototype concepts. Do not crop away the label that communicates that status.
Adapt the motion
Camera movement and annotation can explain a dashboard, settings pair or selected detail. If the actual interaction is essential, obtain its evidence and revise the storyboard. For 15 seconds, use a static paired comparison with fewer moves.
Review implied behavior
Watch the sequence without narration and describe what action it seems to show. Remove any motion that suggests a missing drag, click or automatic update. The comparison can be useful without claiming a complete workflow or measured response speed.
Review checklist
- No missing control sequence is invented.
- The same object appears in both states.
- Annotations are distinct from native UI.