Who this is for: Teams explaining the connection between onboarding and recurring use.
What to prepare
- Empty-state and creation screens
- Saved-object identity
- Verified reuse behavior
- Explicit elapsed-time label
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Empty starting point
Show the configured account’s empty checklist area with the actual instruction.
On screen:Create a sample review checklist
- 02
5–11s
Create the first object
Enter Sample packaging review and the required fields using supplied product states.
On screen:One checklist for this task
- 03
11–16s
Save and inspect
Show the real save action and hold the resulting checklist identity.
On screen:Checklist saved
- 04
16–19s
Mark elapsed time
Use an explicit transition rather than an automatic loop that implies repeated behavior.
On screen:Later · Example return visit
- 05
19–26s
Reuse the object
Locate the same checklist and perform the actual supported reuse action, such as opening it for another sample review.
On screen:Find Sample packaging review again
- 06
26–30s
Bound the result
Hold the reused object or new instance according to the real workflow.
On screen:A repeatable starting point for the next review
Make it your own
- Initial object
- Supply the sample object name, required fields and verified saving behavior.
- Reuse model
- Specify reopening, duplication or new-instance creation and preserve the correct identity relationship.
- Later-use context
- Label the return visit as illustrative elapsed time rather than measured recurring use.
Prepare first and later states
Supply creation, saved-list and later-use evidence. Verify whether reuse means reopening the original, duplicating it or creating a new instance. These actions produce different object identities.
Adapt the routine
For a template product, show the actual new-instance relationship. For a recurring record, preserve the original identifier. A 60-second version can explain how the user finds the item again; a 15-second version should focus only on reuse in an already prepared workspace.
Review outcome language
Do not turn a planned return visit into a retention claim. The film explains a possible recurring task using illustrative data. Keep “later” visible so viewers do not infer that saving automatically triggers another action or completes future work.
Review checklist
- The initial save is confirmed.
- Reuse behavior matches the product.
- No measured habit or retention outcome is claimed.