Who this is for: Product teams planning a truthful and usable release storyboard.
What to prepare
- Approved example alert and preference labels.
- Initial and saved setting states.
- Affected channels, roles and exceptions.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Recognizable alert
Show a labeled illustrative comment summary without private message content.
On screen:Choose how this summary reaches you.
- 02
5–11s
Find the preference
Open the verified notification-preference path and identify the matching control.
On screen:Comment-summary preferences.
- 03
11–18s
Make the choice
Show the current option, then select the supplied alternative neutrally.
On screen:Select the option that fits this task.
- 04
18–25s
Save
Include the real save action and hold on the stored state.
On screen:Confirm the saved preference.
- 05
25–30s
Boundary
Retain the affected channel and any relevant unchanged alert category.
On screen:This choice applies to the stated summary notifications.
Make it your own
- Alert
- Choose the exact notification type controlled.
- Choice
- Supply available options and their effects.
- Scope
- Name personal or workspace-level impact.
Match the alert to the control
The opening notification must belong to the setting being shown. A direct-mention alert is misleading if the control affects only summaries. Keep sample content clearly illustrative.
Adapt personal and team scope
An administrator preference needs the role and affected audience visible. A personal-setting version should not imply changes for teammates. Use separate verified instructions when the two scopes differ.
Review effect and timing
Do not invent delivery schedules, immediate queue cancellation or channel behavior. If the choice takes effect under a documented condition, include it. The saved-state scene establishes the selection, not every downstream notification outcome.
Review checklist
- The alert matches the preference.
- Initial and saved states are visible.
- Personal and workspace scope are not conflated.
- Timing and channel effects are verified.