Who this is for: Product teams preparing focused launch motion briefs.
What to prepare
- Three or fewer related capabilities
- One shared user task
- Evidence of each capability's role
- A verified resulting state
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second launch sequence for PRODUCT_NAME. Begin with SHARED_TASK and introduce CAPABILITY_LIST as a small stack of labeled panels. Each panel must explain its role in the same task. Do not add features merely to fill the composition. Activate the panels in the order the supplied workflow requires. Keep EXAMPLE_OBJECT visible as context. As the final capability is explained, simplify the composition into RESULT_STATE using the supplied product evidence. The collapse is a graphic summary, not a claim that the product automatically combines steps unless that behavior is verified. Hold the result and state OUTCOME_LINE in concrete terms. Do not add savings, adoption or reliability claims. Preserve any prerequisite that would change the viewer's understanding. End with approved identity, CURRENT_STATUS and NEXT_ACTION. If a capability does not contribute to the shared task, recommend moving it to a separate asset.
Make it your own
- CAPABILITY_LIST
- Give each item a distinct role in the same workflow.
- RESULT_STATE
- Use a supplied result rather than an invented summary screen.
- OUTCOME_LINE
- Describe the observed result with a bounded claim.
- PRODUCT_NAME and SHARED_TASK
- Supply approved identity and one job that every included capability contributes to.
- EXAMPLE_OBJECT
- Keep one supplied object or record traceable through the capability summary.
- CURRENT_STATUS and NEXT_ACTION
- Use verified availability and a real destination that matches the demonstrated result.
Choose contributing parts
An illustrative review product might combine item context, reviewer assignment and approval status. Each supports the same task of understanding where review stands.
A custom theme does not strengthen that task and should not enter the stack just because it is visually attractive.
Adapt the stack
For a narrow composition, activate panels vertically. For a wider scene, align them along one clear path. Keep labels attached to their meaning throughout the collapse.
For a longer version, add the most consequential decision between panels rather than simply increasing the number of features.
Correct false automation
If the collapse implies that separate manual steps happen automatically, replace it with an explicit summary transition. If the result cannot be sourced, hold a labeled diagram instead of fabricating UI.
The final frame should let a viewer explain why each included capability mattered.
Review checklist
- Every panel contributes to one task.
- Workflow order matches the supplied behavior.
- The collapse does not invent automation.
- The final outcome is supported by evidence.