Who this is for: Product teams preparing focused launch motion briefs.
What to prepare
- Three related user tasks
- A supplied completion state for each
- One shared example object
- Approved product identity and access copy
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 around JOB_CHECKLIST. Each item must be a concrete action with a supplied COMPLETION_CRITERION. Do not use checks to imply reliability, universal coverage or customer results. Introduce the checklist in an incomplete state. Focus on one item, show its supplied product evidence and mark it complete only after the relevant result is visible. Preserve EXAMPLE_OBJECT across the sequence where appropriate. Keep completed items as quiet context while the next action leads attention. Use exact task wording rather than vague labels such as productive or effortless. If a task remains pending, show its actual status instead of a checkmark. Finish with a readable summary of what the example completed, the approved product name, CURRENT_STATUS and NEXT_ACTION. Do not add a final completion percentage unless it has a defined and supplied basis.
Make it your own
- JOB_CHECKLIST
- Use distinct tasks supporting one workflow.
- COMPLETION_CRITERION
- State the observable result required before each check appears.
- EXAMPLE_OBJECT
- Keep the example consistent across related tasks.
- PRODUCT_NAME
- Use approved identity for the product whose actions supply the completion evidence.
- CURRENT_STATUS and NEXT_ACTION
- Keep access and the closing action accurate after the illustrative checklist is complete.
Define real completion
An illustrative handoff checklist might be “Add context,” “Choose an owner” and “Save the handoff.” Each needs its own supplied state.
“Improve collaboration” is not a checkable action in this sequence and should not receive a success mark.
Adapt the checklist
For a short version, use two essential tasks instead of compressing three demonstrations. For a longer version, explain the condition that makes a task complete.
If the product has pending approvals, use a pending label and explain the next role rather than forcing the checklist into an all-complete ending.
Correct empty progress
If checks appear before evidence, move them after the proof. If all items repeat the same action, merge them and add a useful distinction.
A checklist can organize the story, but it should not create an impression of measured progress outside the illustrative example.
Review checklist
- Every item is an observable task.
- Checks follow verified completion states.
- Pending work is not presented as finished.
- The checklist supports one coherent workflow.