Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Approved old and new terminology.
- Specific verified continuity statements.
- Current navigation and representative task assets.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Old recognition
Show Boards beside the illustrative task columns users recognize.
On screen:You knew this as Boards.
- 02
5–12s
Name mapping
Hold the full old and new words together; use a restrained transition.
On screen:Boards are now called Workspaces.
- 03
12–19s
Purpose continuity
Retain the same columns and sample items using supplied evidence.
On screen:Find your existing columns and saved items.
- 04
19–24s
Current location
Show the actual new label in its verified navigation location.
On screen:Open Workspaces here.
- 05
24–30s
Reference
Hold the new term with a compact old-to-new mapping.
On screen:New name: Workspaces.
Make it your own
- Names
- Use exact approved spelling and capitalization.
- Purpose
- State the task that connects both names.
- Location
- Confirm whether navigation also changes.
Confirm what stays the same
Name specific retained behavior instead of saying nothing changed. If permissions or limits also changed, those facts need their own explanation and must not be hidden by the rename treatment.
Adapt long labels
Use a stacked mapping when side-by-side names would become too small. Avoid splitting a product term in a way that makes it hard to recognize. Approved translations need separate layout inspection.
Check term consistency
After the mapping, use the new name consistently. Keep supporting documentation and screenshots aligned where possible, and describe any confirmed transition period accurately. Do not claim every old label has disappeared without checking.
Review checklist
- Both terms match approved names.
- Continuity is specific and supported.
- Any location change is taught separately.
- The new term is consistent after the mapping.