Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- A fictional task sequence
- Matching product states for one object
- Approved identity assets
- Verified availability and next action
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
A task arrives
Show a clearly labeled illustrative workday with one request, 'Review the draft,' entering a coordinator's list.
On screen:An example workday: one request needs an owner.
- 02
8–17s
The context is scattered
Show the request and its short supporting note in separate neutral panels. Avoid exaggerated notifications or invented mistakes.
On screen:The task and context need a handoff.
- 03
17–27s
Introduce the product moment
Bring the supplied product record into view and identify the same request and note.
On screen:Keep the request and context together.
- 04
27–39s
Choose the next owner
Use approved assignment states and preserve the request title while the relevant person is selected.
On screen:Choose who takes the next step.
- 05
39–49s
Inspect the completed handoff
Hold the supplied final record with owner, note and actual status readable.
On screen:The next owner is visible.
- 06
49–55s
Return to the day
Return to the simple workday overview and show this one task in its accurate state, without implying all work is finished.
On screen:One handoff, with clear context.
- 07
55–60s
Close honestly
Display approved product identity and current access wording.
On screen:Coming soon. Join the waitlist.
Make it your own
- Workday object
- Use one approved fictional or permission-cleared object throughout.
- Completion state
- Replace assignment with the actual verified result.
- Closing status
- Match current product availability.
Keep the workday small
This is a fictional narrative, not a customer case study. The story follows one request rather than claiming that the product transforms an entire day. Do not add time saved, reduced stress or business results unless separate evidence supports them.
The surrounding workday provides context. The product record supplies the evidence. Preserve that distinction when replacing the illustrative scenes with actual assets.
Adapt the sequence
For a 30-second version, combine arrival and context, show the assignment directly and retain the proof hold. Remove the return-to-day scene before cutting a necessary condition.
For a different task, retain one object and one visible completion criterion. A saved note, assigned request and confirmed booking are different results; use the actual one.
Prepare matching assets
Supply the starting, action and resulting states with consistent example data. If the product does not store the supporting note, revise the promise rather than drawing it into the interface.
Review the story without narration. The viewer should understand why the product appears and what happened to the request.
Review checklist
- The scenario is explicitly illustrative.
- One object anchors the day.
- The product result is bounded and supplied.
- Retiming preserves the proof and access condition.