Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- Matched old and new captures of one task.
- A stable illustrative record and verified changed action.
- The current scope and availability statement.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second planning sequence explaining a fictional request tool's new owner filter. Label all sample records as illustrative. Begin with the previous queue and a short label, “Previous: inspect the full queue.” Keep the same viewport, request titles and status filter when cutting to the updated version. Show the verified owner-filter control, select Example owner and hold on the resulting matching requests. Retain the active filter label so the cause of the changed list is visible. Use the headline “Focus the queue on one owner.” Do not change unrelated rows, animate an invented menu path or claim measured time savings. End with the approved eligibility line and the same filtered result. Treat the comparison as an editorial sequence, not a recording of an automatic transition between software versions. Use quiet motion and give the changed control and result separate reading holds.
Make it your own
- Changed action
- Replace the owner-filter example with one verified action; change both the copy and result evidence.
- Controlled record set
- Use identical labeled sample records in both versions.
- Scope line
- Insert approved role, availability and behavior limits.
Prepare a comparison that isolates the change
Record which differences are intentional. If the new capture also changes theme, row order or account role, correct those inconsistencies before using the brief. A smaller data set may be clearer, but it must remain consistent across both states.
Adapt the layout to the visible difference
Use an alternating crop for a small control and a side-by-side layout for a larger arrangement change. Establish the full screen before a detail crop. For a 15-second adaptation, remove background context and keep the action, result and essential scope; do not simply double playback speed.
Repair results that imply more than the release
If the final list differs for reasons besides the selected owner, use the correct capture or explain the additional condition. Replace “work faster” with the actual action unless performance evidence exists. The closing frame should let a reviewer identify the control responsible for the change.
Review checklist
- Old and new screens share the same relevant data and state.
- The changed action is visible before its result.
- The comparison makes no unsupported speed claim.
- The final filter state agrees with the displayed records.