Who this is for: Product teams preparing focused launch motion briefs.
What to prepare
- Verified current scope
- Approved beta and planned items
- Exact status labels
- Any approved timing and eligibility facts
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second launch explanation for PRODUCT_NAME with three possible states: CURRENT, BETA and PLANNED. Include only states present in the supplied release record. Use readable labels and distinct scene treatment so viewers do not confuse a future item with an available action. Lead with CURRENT_CAPABILITY and demonstrate it using supplied evidence. If a beta item matters, explain its eligibility and limits separately. Present PLANNED_DIRECTION as a clearly labeled concept or statement; do not fabricate working UI or a release date. Keep the final summary organized by status rather than presenting every item as a checked feature. End with the next action that corresponds to current access. If a supplied date is uncertain, omit it or use the approved uncertainty wording. The purpose is to explain the boundary of the launch, not to create a promise from an internal aspiration.
Make it your own
- CURRENT_CAPABILITY
- Use a verified released action and its evidence.
- BETA_SCOPE
- Include actual participation limits.
- PLANNED_DIRECTION
- Use approved future-oriented language and concept labeling.
- PRODUCT_NAME
- Use approved identity for the capabilities in the current release record.
- CURRENT, BETA and PLANNED status labels
- These are separate status categories, not default claims that all three exist; include only approved items with their real conditions.
- Current next action
- Choose a destination that corresponds to present access, not the planned direction.
Separate evidence levels
An illustrative product might currently organize personal tasks, test a limited sharing feature and plan a later reporting view. The film should not display all three as equally available.
Give the working task the demonstration and the planned item a plainly labeled concept treatment.
Adapt the scope
If the roadmap adds little to the launch decision, omit it and keep the film focused on current value. If future direction is central, use a longer explanation with more space for boundaries.
A summary card can be useful if its statuses remain readable and attached to the correct items.
Correct roadmap certainty
Remove countdowns or date labels that were not approved. Replace a fake functional prototype with a labeled concept if no working evidence exists.
Check whether the final CTA invites access to a planned capability; if so, revise it to the actual current action.
Review checklist
- Current, beta and planned states are clearly labeled.
- Only current verified behavior is demonstrated as available.
- No date or capability is invented.
- The closing action matches present access.