Who this is for: Teams planning first-use product training.
What to prepare
- First-run screens
- Required setup decisions
- Creation and saved-object states
- Return-navigation evidence
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Define the starting point
Show the actual first-run screen and identify any account access already completed.
On screen:First project in a new sample workspace
- 02
7–17s
Complete required setup
Show the supplied workspace name and necessary configuration decisions. Use fictional values and exact controls.
On screen:Set up Sample workspace
- 03
17–25s
Reach the empty area
Open the real Projects area and hold its empty-state instruction.
On screen:Create the first project
- 04
25–38s
Create one object
Enter Sample launch review and show required consequential fields. Identify any prefilled values.
On screen:Project: Sample launch review
- 05
38–48s
Save and confirm
Perform the actual save action and inspect the resulting project identity. Preserve pending feedback if present.
On screen:Project saved
- 06
48–56s
Find it again
Return through the real navigation to the project list and locate the same project.
On screen:Find it in Projects
- 07
56–60s
Name the next task
Hold the saved project without pretending later work has already been completed.
On screen:Next: add the first review item
Make it your own
- First-run boundary
- State which account access is already complete and which setup the film actually teaches.
- Required setup
- Supply the role-specific configuration decisions and exact interface controls.
- Created object
- Repeat the same fictional name and identity through creation, saving and list inspection.
- Next task
- Name a sensible next action without implying it has already been completed.
Prepare first-run evidence
Supply the complete setup path for the intended role, including required choices. If account creation lies outside the film, state that boundary. Do not substitute a configured dashboard and describe it as a complete first-run walkthrough.
Adapt without hiding setup
For 30 seconds, narrow the task to object creation in an already configured workspace and change the title or opening accordingly. For this 60-second version, compress repeated text entry while retaining decisions that affect access or object type.
Review persistence and findability
The final list inspection distinguishes a saved object from a filled form. Confirm the name and identifier match the creation result. This illustrative storyboard does not prove persistence itself; production requires the real observed save-and-return evidence.
Review checklist
- The setup boundary is accurate.
- No consequential required field is skipped.
- The object is found again after saving.