Who this is for: Product teams briefing an accurate and useful update explanation.
What to prepare
- The verified old and new export paths.
- Supported format, scope and permission facts.
- An approved completion state and example output.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second planning sequence for a fictional reporting tool moving export into the report menu. Use one labeled illustrative report. Show the previous route briefly, then establish the current report menu and exact Export label. Demonstrate only the supplied format option and scope choices. Keep any permission or row-selection condition visible where it affects the action. Include the actual completion feedback, then inspect the approved example output only if it is available. Do not invent file formats, transparent backgrounds, resolution choices or automatic downloads. Do not use a generic checkmark as proof that a file was produced. End with the new route and the verified way to confirm the result. Treat all format details as facts about the example product, not capabilities of the platform used to plan the video.
Make it your own
- Export route
- Supply exact current labels and required steps.
- Output facts
- Name only verified format and scope options.
- Completion evidence
- Specify the actual status or output that confirms success.
Separate route changes from output changes
A relocated button does not imply a new format or improved output quality. List which facts changed and which remain the same. If the release changes both, give each a distinct explanation rather than blending them into a single reveal.
Adapt for permission or data-scope choices
Show the intended role and whether the export includes selected rows, filtered rows or another approved scope. Keep sensitive source data out of the illustrative example. If the output is unavailable, end at a clearly labeled workflow preview.
Repair false file proof
Do not fabricate a file preview to create a satisfying ending. Request the approved output or narrow the claim to the route being taught. A filename animation should match actual naming behavior only when the team supplies it.
Review checklist
- The route and output changes remain distinct.
- Only supported format options appear.
- Export scope matches the demonstrated selection.
- The result is evidenced or clearly labeled as a preview.