Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Retirement record with distinct milestones.
- Affected roles and workflows.
- Verified alternative, gaps and completion instructions.
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–10s
Recognize
Show the legacy scheduled-summary label and identify affected administrators.
On screen:This notice concerns legacy summary schedules.
- 02
10–20s
Timeline
Present approved milestones with their events rather than a single ambiguous date.
On screen:Check when setup and operation change.
- 03
20–35s
Alternative
Show the supplied replacement setup and disclose relevant missing options.
On screen:Create the verified replacement schedule.
- 04
35–50s
Confirm
Inspect the replacement summary using the owner's criteria; do not imply automatic conversion.
On screen:Verify the new schedule before relying on it.
- 05
50–60s
Action record
Hold the owner, required action, confirmed deadline and support destination.
On screen:Administrator action: follow the approved transition guide.
Make it your own
- Retiring task
- Name the user work that depends on the feature.
- Timeline
- Attach each date to its actual event.
- Alternative limits
- State relevant differences in the replacement.
Check the alternative's fit
A replacement may cover the main task while lacking an old option. Keep that gap beside the recommendation. If no suitable alternative exists, replace the transition scene with the owner's approved next step.
Adapt to a 30-second notice
Keep affected task, milestone, owner and destination. Treat the short asset as a notice, not a complete setup tutorial. Do not omit the lack of automatic conversion when that fact changes what users must do.
Maintain the date-bearing asset
Record every scene and publication surface containing a deadline. If timing changes, revise the encoded video and surrounding copy together. A correction in the description alone does not change the burned-in date.
Review checklist
- Every milestone has an approved event and date.
- The replacement actually exists.
- Relevant replacement gaps are visible.
- Automatic conversion is not assumed.