Who this is for: Teams explaining role-sensitive tasks.
What to prepare
- Confirmed role matrix
- Matched object states
- Restricted-control evidence
- Authorized result
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Set the task
Show sample request R-024 and the question beside its status.
On screen:Who can approve this sample request?
- 02
5–11s
Contributor view
Label Example contributor and show the actual available controls on R-024.
On screen:Contributor · View and permitted edits
- 03
11–16s
Explain the boundary
Highlight the verified restricted approval state without inventing an error dialog.
On screen:Approval requires the verified reviewer role
- 04
16–19s
Separate-account transition
Preserve R-024’s identity through an explicit actor change.
On screen:Separate reviewer account
- 05
19–26s
Authorized action
Show Example reviewer using the real approval control and commitment step.
On screen:Reviewer records the decision
- 06
26–30s
Inspect the result
Hold R-024 with the observed final status and relevant role context.
On screen:Decision recorded for R-024
Make it your own
- Role pair
- Use documented names and the exact view, edit or approval difference.
- Matched task state
- Keep the same sample request, record status and workspace conditions.
- Restricted-user next step
- Show only a verified request or escalation action appropriate to the role.
Prepare role facts
Obtain the actual rules and matched screenshots. Confirm that an unavailable button is caused by role rather than missing data or an incompatible record status. Use exact role names in production.
Adapt the boundary
A view-versus-edit comparison can replace approval if it is the actual question. For 60 seconds, show the restricted user’s supported next step, such as requesting access. Do not imply that switching the editorial view grants permissions.
Review visible information
Check fields, attachments and history as well as buttons. A screenshot from an administrator account may reveal information unavailable to the role named in the film. Keep conclusions limited to the configured example and its verified capability difference.
Review checklist
- Both accounts are accurately labeled.
- The restriction’s cause is verified.
- The transition cannot imply self-escalation.