Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Approved old and current task sequences.
- Release records explaining each changed step.
- Matched illustrative task data and source screens.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Task and baseline
Show the illustrative task, preparing a review queue, with the original verified step labels.
On screen:Preparing the review queue: earlier workflow.
- 02
5–11s
Retained preparation
Keep the unchanged prerequisite visible in both paths.
On screen:Keep the required workspace context.
- 03
11–18s
Changed step
Replace repeated filter selection with the supplied saved-view action; mark the change explicitly.
On screen:Changed: reopen an approved saved view.
- 04
18–25s
Current path
Display the full current path with retained and changed steps labeled, not just color-coded.
On screen:Check the same review result.
- 05
25–30s
Scope
Hold both task outlines and the release-period context.
On screen:Workflow changes shown; no timing claim implied.
Make it your own
- Task
- Choose one workflow with a verified before-and-after sequence.
- Step changes
- Classify each step as removed, changed or retained.
- Period
- Supply the actual release period and status.
Build the step map
List each action in both versions and tie its difference to a release record. Do not remove a prerequisite from the old path merely to make the new one look cleaner. A required manual check remains part of both paths.
Adapt the comparison's detail
For a short asset, explain one consequential changed step. A 60-second version can inspect several changes separately. If the task no longer has a comparable endpoint, use a narrative evolution format instead of a matched comparison.
Review fairness before visual polish
Keep the input and completion definition the same. Fewer visible steps are an observation about the mapped procedure, not proof of faster completion. Use actual measurements only when separately supplied and approved.
Review checklist
- Old and current paths use the same task boundary.
- Every changed step has release evidence.
- Retained prerequisites remain visible.
- The diagram does not imply measured savings.