Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Approved migration procedure and source eligibility.
- Role and preparation requirements.
- Destination acceptance criteria and recovery guidance.
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–10s
Entry check
Identify the illustrative report and old-builder state; show the stop condition for already migrated reports.
On screen:Does this procedure apply to this report?
- 02
10–20s
Preflight
Show editor permission and the recorded source definition using supplied evidence.
On screen:Confirm permissions and preparation.
- 03
20–35s
Transition
Demonstrate the approved migration action without invented settings.
On screen:Run the documented transition.
- 04
35–50s
Acceptance
Inspect destination filters, grouping and column labels for the same report identifier.
On screen:Check the migrated definition.
- 05
50–60s
Failure route
Hold the acceptance summary and approved help instructions when a check fails.
On screen:If a check fails, follow the supplied recovery path.
Make it your own
- Entry state
- Specify which source version or configuration qualifies.
- Procedure
- Use the actual approved migration steps.
- Verification
- Supply the destination properties that must match.
Specify each gate
Write pass and failure conditions for entry, preparation and acceptance. Avoid ambiguous ready labels. Keep the underlying procedure version with the storyboard so later product changes can be detected.
Adapt the scope carefully
For a data migration, use the owner's actual integrity and reconciliation checks instead of copying the definition example. For 30 seconds, orient viewers to the gates and link to the detailed procedure rather than rushing it.
Review completion proof
A completed operation is not automatically a correct destination. Reserve inspection time for the acceptance criteria. Do not imply that every historical object moved if the procedure's scope is narrower.
Review checklist
- Entry and role requirements are explicit.
- The same report remains identifiable.
- Acceptance matches the actual migration scope.
- Every failure gate has approved guidance.