Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- Three approved release facts with current scope.
- One task and proof asset for each fact.
- The full release-note destination and availability copy.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second digest for a fictional document-review tool. Organize it around “Find the work,” “Check the version” and “Follow up.” Begin with that shared review-workflow theme. Give the first job the longest beat: show a personal saved queue reopening with its verified filters. For the second, hold on a supplied revision identifier and explain what it identifies. For the third, show the approved unresolved-comment filter and its matching example discussion. Label sample content as illustrative and preserve object identity wherever the actual product supports continuity. Do not imply that these controls form an automatic end-to-end workflow. Keep each job's title visible during its evidence moment. State any differing availability conditions beside the relevant change. End with a compact three-job recap and the approved release-note destination. Omit unrelated cosmetic changes rather than adding a fourth rushed panel.
Make it your own
- Three jobs
- Use concrete verbs and objects from the supplied release list.
- Lead change
- Choose the item that needs the most explanation and evidence.
- Availability per item
- Retain different eligibility rules instead of one overbroad closing statement.
Group before writing scene copy
Map each source item to its job and record why it belongs. “Productivity” is too broad to guide a scene. If two items answer the same question, combine their explanation or choose one rather than manufacture separate jobs.
Adapt the structure to the actual release
A two-item edition is valid when only two changes merit explanation. A 60-second version can add setup and exceptions for the lead story; it should not automatically double the number of items. Keep the recap shorter than the demonstrations.
Fix a digest that feels like a list
Replace generic benefit cards with an observable task and result for each item. If the only connection is that everything shipped that week, use a straightforward roundup title rather than claim a unified workflow. Review the spoken transition between jobs for invented causal links.
Review checklist
- Each job maps to a verified release item.
- The lead receives enough room for its proof.
- The sequence does not imply unsupported automation.
- Different eligibility conditions remain attached to their items.