Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Old and current route captures.
- The intended user's role.
- The verified destination screen and any rename mapping.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Recognize the task
Show the familiar member-list task and enough old navigation for orientation.
On screen:Looking for workspace members?
- 02
5–9s
Previous location
Label the old Settings then Members path as previous behavior.
On screen:Previously: Settings, then Members.
- 03
9–17s
New route
Cut to the current overview; show Workspace menu and People in the verified order.
On screen:Now: Workspace menu, then People.
- 04
17–24s
Destination
Hold on the actual member list and its workspace identity.
On screen:Your workspace member list.
- 05
24–30s
Reference
Keep the new path readable with any approved role condition.
On screen:Use the new route for this task.
Make it your own
- Stable task
- Keep a task label recognizable across versions.
- Route
- Supply every required menu level.
- Role scope
- Use screens from the intended role.
Map the complete route
Record prerequisites such as selecting a workspace. A missing starting level can make an otherwise accurate menu sequence unusable. Check whether a renamed item also needs a term-mapping cue.
Adapt to different screens
Use a dedicated verified route for mobile rather than assuming the desktop path applies. For 15 seconds, retain the old cue, full new path and destination; remove redesign background first.
Review whether the path is reproducible
Ask a reviewer to name each required action from the initial current-version screen. Add unshown steps. Do not imply that old bookmarks redirect or that permissions changed unless the release record confirms it.
Review checklist
- The task remains recognizable across the cut.
- Every required current-route level appears.
- The destination and role match.
- Old-link behavior is not invented.