Who this is for: Teams explaining collaborative review workflows.
What to prepare
- Actor-specific screens
- Comment and revision evidence
- Resolution permissions
- Final thread and document statuses
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
Introduce the object
Show D-008, Sample instruction card, in the author’s account. State the configured workspace condition.
On screen:Example author · D-008
- 02
8–17s
Request review
Perform the verified request action and show its pending state.
On screen:Request a review
- 03
17–27s
Reviewer comments
Switch explicitly to Example reviewer and show the comment Clarify the opening step beside the passage.
On screen:Reviewer: clarify the opening step
- 04
27–38s
Author revises
Return to Example author with D-008 and the same comment; show the specific supported revision.
On screen:Name the first action clearly
- 05
38–47s
Reply to the thread
Show the author’s actual reply confirming the described change without replacing the underlying evidence.
On screen:The opening now names the first action
- 06
47–55s
Resolve the discussion
Switch to the permitted resolver and activate the real Resolve control.
On screen:Discussion resolved
- 07
55–60s
Inspect the bounded result
Hold the thread’s resolved state and the document’s actual overall status.
On screen:This thread is resolved
Make it your own
- Document and passage
- Keep one sample document, comment target and revised passage traceable.
- Actors and permissions
- Name the author, reviewer and permitted resolver without confusing actor and owner.
- Resolution scope
- State whether the result concerns one thread or a separately evidenced document decision.
Prepare role continuity
Supply screens for each actor with the same document, passage and thread. Record who owns the document and who may resolve a discussion. The current actor need not become the object owner.
Adapt the collaboration
For a 30-second version, shorten initial context and show one concise revision. Preserve role labels and the resolution boundary. If the task truly includes document approval, add the separate verified approval action instead of renaming thread resolution.
Review asynchronous time
Use explicit transitions when the edit compresses waiting between people. Do not imply automatic or simultaneous responses through seamless morphs. The illustrative timings are editorial choices and do not measure collaborator availability.
Review checklist
- Every actor change is explicit.
- The same passage and thread are tracked.
- Thread resolution is not whole-document approval.