Who this is for: Launch teams planning a specific communication asset and its production handoff.
What to prepare
- A shared launch promise
- Approved concept and product evidence
- One follow-up question
- Current destinations for each asset
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–4s
Teaser: name the problem
Show a simple illustrative request without an owner.
On screen:Who takes the next step?
- 02
4–10s
Teaser: preview direction
Use a labeled concept or approved narrow preview.
On screen:A clearer handoff is taking shape.
- 03
10–15s
Teaser: close with status
Hold identity and accurate access wording.
On screen:Coming soon. Join the waitlist.
- 04
15–20s
Reveal: establish the task
Reintroduce the example request so this asset stands alone.
On screen:Give the request a visible next owner.
- 05
20–30s
Reveal: demonstrate
Use supplied assignment states with a stable object identifier.
On screen:Choose the owner in the request.
- 06
30–40s
Reveal: hold the proof
Keep the supplied result readable and explain its boundary.
On screen:The owner and context stay together.
- 07
40–45s
Reveal: offer next action
Show current identity, status and destination.
On screen:Explore the product's current access.
- 08
45–50s
Follow-up: ask a new question
Reintroduce the relevant context without replaying the reveal.
On screen:What does the next owner see?
- 09
50–56s
Follow-up: answer with evidence
Show only the supplied recipient view and actual visibility.
On screen:See the verified handoff context.
- 10
56–60s
Follow-up: direct to detail
Show the actual supporting workflow resource.
On screen:Read the complete workflow.
Make it your own
- Shared motif
- Retain recognition without repeating the same explanation.
- Follow-up question
- Answer a new supported viewer need.
- Asset destinations
- Match each closing action to its actual resource.
Understand the package clock
The 60-second timeline describes three separate planning assets: 0–15 teaser, 15–45 reveal and 45–60 follow-up. Produce and review them as distinct cuts unless a continuous compilation is specifically wanted.
The request example is illustrative. The recipient-view follow-up requires its own source evidence and must not invent permissions.
Adapt the distribution jobs
The teaser introduces direction, the reveal explains the action and the follow-up answers a new question. Changing only dimensions or headlines would not create the same distinction.
If no useful follow-up evidence exists, choose a different supported question rather than recycling the reveal as an answer.
Review each deliverable
Each cut needs its own opening context and accurate closing action. Viewers may encounter them in any order.
Track shared scenes so later UI or availability changes reach every derivative. Check the actual final files individually rather than approving the package from a single source timeline.
Review checklist
- The three cuts have distinct jobs.
- Each cut stands alone.
- The follow-up has independent evidence.
- All final assets are reviewed separately.