Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- The approved migration path and applicable source state.
- Role, preparation and recovery requirements.
- The destination acceptance checks and help route.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second orientation sequence for a fictional report-definition migration. Start by identifying the old builder and the report it contains. Show an entry checkpoint: this procedure applies only to the supplied source state. Next identify the required editor role and preparation record. Present the approved migration action without inventing settings or skipping consequential confirmations. Move to the destination report with the same identifier. Hold on the owner's acceptance checks for filters, grouping and column labels. Use the checkpoint labels “Applies to me,” “Ready to migrate” and “Verify the result.” If a check fails, direct the viewer to the approved procedure or support route rather than illustrating a guessed reset. Do not imply historical data migration when the supplied procedure moves only a definition. End at the verified destination criteria, not a decorative progress bar.
Make it your own
- Source eligibility
- Define the exact state for which the procedure applies.
- Approved action
- Insert the real ordered migration step or procedure reference.
- Acceptance criteria
- Name the destination properties that must be checked.
Map the gates before the scenes
For every checkpoint, specify a pass condition and a failure route. A label such as “Ready” is insufficient without the role and input requirements behind it. Keep private operational details in the approved procedure rather than inventing public instructions.
Adapt for a longer migration
Use this short version as orientation and a longer asset for the detailed path. Preserve the same checkpoint names so users can connect them. Do not accelerate a complex setup until important choices become unreadable.
Repair false completion
A completed operation may still require inspecting the destination. Replace a generic success ending with the supplied acceptance checks. If the migration's scope excludes historical records, say so before a visual transition could imply that everything moved.
Review checklist
- Entry conditions and role requirements are explicit.
- Every checkpoint has an approved failure route.
- The shown action matches the documented procedure.
- The ending verifies the actual migration scope.