Who this is for: Launch teams planning a specific communication asset and its production handoff.
What to prepare
- One launch promise
- A verified workflow with prerequisites
- Matching source states
- A clear module boundary and current CTA
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–5s
State the launch task
Show one illustrative request and its unresolved handoff.
On screen:Who takes the next step?
- 02
5–12s
Show a concise proof
Use supplied states to reveal the assigned owner on the same request.
On screen:Make the next owner visible.
- 03
12–15s
Create the module boundary
Hold the product identity and a clear transition statement.
On screen:See how the handoff works.
- 04
15–26s
Establish prerequisites
Show the configured starting view and the relevant role or condition.
On screen:Begin with the correct role and request.
- 05
26–42s
Explain the action
Walk through the verified selection and save steps with readable labels.
On screen:Choose the owner and confirm the change.
- 06
42–53s
Verify the result
Inspect the supplied final state and explain one relevant limitation.
On screen:Check the owner and recorded status.
- 07
53–60s
Close the full explanation
Show approved identity, current status and supported destination.
On screen:Explore the workflow and current access.
Make it your own
- Announcement promise
- Keep it within the first module's evidence.
- Deep-dive task
- Add genuine explanatory depth.
- Module destination
- Give the short cut a supported next step.
Make the boundary deliberate
The first 15 seconds form an announcement module for the illustrative assignment product. The remaining sequence teaches the verified workflow. It should add context and steps rather than replaying the opening more slowly.
If the short module is published alone, give it an appropriate destination to the full explanation or current product page.
Adapt the depth
A 30-second complete version can keep the opening brief and demonstrate only the consequential decision and result. Retain prerequisites that affect interpretation.
If the workflow needs more detail than the planned runtime allows, narrow the task. Do not remove required steps merely to preserve a modular structure.
Review both cuts independently
Check that the short module does not imply a capability the longer version later qualifies. Essential boundaries must survive in both.
Inspect identity, object continuity and closing status in each final asset. A module boundary in the storyboard is not proof that every exported cut remains coherent.
Review checklist
- The first module can stand alone accurately.
- The deep dive adds steps rather than repetition.
- Essential conditions survive every cut.
- Each published version receives its own final review.