Who this is for: Launch teams planning a specific communication asset and its production handoff.
What to prepare
- An approved problem and product direction
- Verified current capabilities
- Approved identity assets
- A register of concept and missing material
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Name the problem
Show a plain illustrative task situation without fake UI.
On screen:The next step should be easier to understand.
- 02
5–11s
Introduce the intended job
Use approved copy and simple labeled objects to explain the product direction.
On screen:A clearer view of the task and its owner.
- 03
11–18s
Show the labeled concept
Display the approved concept with a persistent concept label.
On screen:Concept preview.
- 04
18–24s
State current scope
Present only owner-approved facts about what exists today, separate from planned behavior.
On screen:Here is the current product stage.
- 05
24–27s
Explain the next update
Name the actual way viewers can receive future availability information.
On screen:Follow current availability updates.
- 06
27–30s
Close with status
Hold approved identity and the real access state.
On screen:Coming soon. Join the waitlist.
Make it your own
- Concept status
- Use the correct prototype or planning label.
- Current scope
- Separate verified behavior from intended direction.
- Replacement criteria
- Define what final evidence is still needed.
Separate design from evidence
The illustrative task-and-owner concept is a planning device. It is not a substitute for a released product screen or a verified interaction.
Do not build a polished fake dashboard merely to make the launch look complete. A simple concept can be useful when its status and intended job are clear.
Adapt to available material
If one real product screen becomes available, add it as evidence for that narrower behavior while retaining concept labels elsewhere. Do not let one verified asset imply that the whole proposed workflow is complete.
For a 15-second teaser, use problem, labeled concept and waitlist close. For a 60-second explanation, add the product principle and a clearly bounded roadmap discussion.
Set replacement criteria
Record which scenes require final assets and what those assets must demonstrate. Assign an owner rather than leaving a generic image placeholder.
Before public delivery, either replace provisional material or intentionally keep it labeled as concept. Review every status statement against the actual destination.
Review checklist
- Concepts remain visibly labeled.
- No working behavior is fabricated.
- Current and planned scope are distinct.
- Availability agrees with the destination.