Who this is for: Teams explaining actionable product alerts.
What to prepare
- Notification and destination states
- Required action evidence
- Confirmed task result
- Actual role labels
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Establish the context
Show the configured sample reviewer account and a stable workspace identity.
On screen:Example reviewer’s work queue
- 02
5–10s
Read the notification
Hold the actual alert referencing R-047 and its required review.
On screen:R-047 needs your review
- 03
10–15s
Follow the destination
Activate the verified link and arrive at the same request. Preserve its identifier.
On screen:Open request R-047
- 04
15–22s
Perform the required action
Inspect the relevant sample content and show the real decision control and commitment step.
On screen:Review, then record the decision
- 05
22–27s
Verify resolution
Hold the request’s confirmed resulting status. Distinguish it from the notification’s read indicator.
On screen:Decision recorded
- 06
27–30s
Close on the same object
Keep R-047 visible and remove competing motion.
On screen:The request’s task is complete
Make it your own
- Alert and object
- Use exact notification wording and the same sample identifier at the destination.
- Required decision
- Supply the actual authorized action and commitment needed to resolve the task.
- Resolution evidence
- Distinguish the notification's read state from the verified underlying task result.
Prepare alert and task evidence
Supply the exact alert, destination route, role requirements and action result. If the destination is a list rather than a detail view, include the selection needed to reach the request.
Adapt the required action
A missing-field reminder can use correction and save instead of a review decision. For 60 seconds, explain the relevant exception or review criterion. A 15-second version should narrow to navigation and avoid claiming full resolution.
Review read versus resolved
Opening or dismissing an alert may change its badge while leaving the task pending. Keep those states separate. If the final result is not evidenced, close with the accurate observed state rather than an invented success message.
Review checklist
- Alert and destination identify the same object.
- The required action is shown.
- Read status is not presented as task completion.