Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- Verified roles and permissions
- Matching screens for one shared item
- Exact pending and completed states
- Approved identity and access copy
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Name the shared task
Introduce an illustrative draft that needs review, with author and reviewer roles labeled.
On screen:One draft needs a clear review path.
- 02
7–16s
Show the author's contribution
Use the supplied author view to prepare and submit the draft.
On screen:The author submits the draft.
- 03
16–24s
Make the handoff explicit
Carry the same draft identifier into the supplied reviewer view.
On screen:The reviewer receives the relevant context.
- 04
24–35s
Show the review decision
Display one approved review action or comment, preserving the role label.
On screen:Review the draft and state the next action.
- 05
35–45s
Show the response
Return to the author or responsible role for the verified next step.
On screen:Respond to the requested change.
- 06
45–54s
Hold the final status
Show the supplied final state with the draft identifier and actual status readable.
On screen:The draft's status stays visible.
- 07
54–60s
Close with the job
Display identity, current availability and a task-specific descriptor.
On screen:A shared workspace for a visible review path.
Make it your own
- Roles
- Use actual functional roles and permissions.
- Shared object
- Keep one item identifiable across views.
- Final status
- Preserve the supplied state exactly.
Preserve role ownership
The draft-review example is fictional and illustrative. Replace its steps with the actual supplied workflow. Do not imply that all roles can edit, approve or view the same information.
A stable draft identifier and role labels are more reliable orientation devices than changing avatar colors alone.
Adapt the complexity
For a 30-second version, show submission, one review decision and the verified final status. Remove secondary discussion rather than collapsing different roles into one generic user.
For a narrow presentation, use sequential role scenes. A wider layout can keep two labeled lanes visible if the text remains readable.
Verify the handoffs
Check that every transition corresponds to a real change in role, view or status. A smooth animation should not imply automatic notification or synchronization absent from the source.
Keep pending states accurate. If review has been requested but not completed, the final copy must not say approved.
Review checklist
- Roles remain identifiable.
- The shared object stays continuous.
- Handoffs do not invent automation.
- Pending and completed states remain distinct.