Who this is for: Teams publishing asynchronous product explanations.
What to prepare
- Configured-account screen
- Actual filter behavior
- Matching list and detail states
- Exact role and object labels
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
State the task
Show the sample reviewer workspace with its role label and populated request list. Keep the illustrative-data label visible.
On screen:Find your next assigned review
- 02
5–10s
Set the scope
Open the actual reviewer filter and select the sample account using supplied states. Retain the filter label.
On screen:Configured account · Example reviewer
- 03
10–15s
Apply the condition
Show the verified Apply action or observed live-filter behavior. Keep any processing state distinct.
On screen:Show requests assigned to you
- 04
15–21s
Open one result
Select R-041, “Sample booklet review,” and preserve its identity as the detail view appears.
On screen:Open sample request R-041
- 05
21–26s
Inspect the result
Hold the reviewer, status and due-date fields. Highlight only the field needed to understand the next task.
On screen:Check the review status and due date
- 06
26–30s
Close with direction
Return to a stable detail frame; leave the result readable rather than adding a feature montage.
On screen:Review this request’s details
Make it your own
- Viewer and starting role
- Supply the configured account, role and prerequisites stated at the opening.
- Task object
- Replace R-041 and its fields consistently across list, detail and closing copy.
- Filter and completion
- Use the actual scope controls and the fields that prove the selected task.
Prepare the configured start
Supply the real account role, filter controls and matching request states. Tell the viewer that setup is complete before the film begins. This prevents a recurring-task explanation from being mistaken for onboarding.
Adapt the task while preserving the chain
Replace review requests with another recurring object, keeping context, selection and inspection. For a 15-second cut, remove the return or secondary field and retain the starting condition and confirmed destination. For 60 seconds, explain one relevant exception rather than adding unrelated regions.
Review independent understanding
Read the sequence without a presenter’s explanation. A reviewer should identify who is acting, why the list changed and what the final screen proves. If they cannot, revise the labels or scene boundaries. The example is an unrendered planning asset; its timing still needs a readability pass.
Review checklist
- Starting prerequisites are explicit.
- The task remains singular.
- Final fields answer the opening question.