Aitoma — 30-second software storyboard and review sheet
https://aitoma.ai/guides/software-video-storyboard#worked-software-storyboard

FICTIONAL TEACHING EXAMPLE
The app, roles and interface are invented. This is a proposed feature explanation,
not an Aitoma product demonstration, a client result or a complete tutorial.
Replace labels and behavior with verified details from your product.
The timings are planned, not measured. No video has been rendered for this example.

AUDIENCE: Team lead deciding how to involve a reviewer.
QUESTION: Can someone comment without changing the team's tasks?
MESSAGE: In this fictional app, a reviewer can comment but cannot edit task fields.
NEXT STEP: Read the current role guide before inviting someone.

SCENE 1 | 00:00–00:04 | Establish the question
Picture: A task and its comment area, using sample content.
Narration: Need feedback without changing the work?
Overlay: Feedback, without task edits
Check: Explain task-edit permission without implying all changes are prevented.

SCENE 2 | 00:04–00:10 | Identify the role
Picture: Owner account; existing invitation panel; select Reviewer.
Narration: Choose the reviewer role when you invite someone.
Overlay: Owner account · Reviewer role
Check: Current role name, invitation permission and access scope. This scene does
not show the entire invitation procedure.

SCENE 3 | 00:10–00:18 | Show the permitted action
Picture: Clearly labeled reviewer account. Add “Please check the due date” and
show the comment appearing on the same task.
Narration: They can leave a comment on the task.
Overlay: Reviewer account · Can comment
Check: Actual submission by the reviewer role; same task across the account cut.

SCENE 4 | 00:18–00:25 | Show the boundary
Picture: Stay in the reviewer account; show task fields as read-only.
Narration: Task edits stay with people who have editing access.
Overlay: Reviewer account · Task fields are read-only
Check: Test account plus current permission definition. A disabled-looking
button alone is not proof of access control. Do not test on customer data.

SCENE 5 | 00:25–00:30 | Offer the next step
Picture: Readable invitation to the current role guide.
Narration: Check the role guide before you invite.
Overlay: Read the role guide
Check: A working route from the published post or page. A button drawn in the
video is not an interactive link.

PRODUCTION INPUTS TO REPLACE
Product and version:
Current role/permission documentation:
Owner and reviewer test-account captures:
Approved sample task data:
Role-guide destination:
Product reviewer:
Capture date:
Export version:

TIMING AND CLARITY REVIEW
[ ] Scene durations total 30 seconds: 4 + 6 + 8 + 7 + 5.
[ ] Scratch narration and actual actions fit without rushing.
[ ] Role name and account labels remain readable at intended viewing size.
[ ] Account switch is explicit; task identity is preserved.
[ ] Captions preserve the spoken explanation; overlays are additional cues.
[ ] Narration, interface and current permission definition agree.
[ ] Final destination works in the publication context.
[ ] A reviewer can explain who can comment, who can edit and where to check scope.

Reviewer observation:
Unresolved issue:
Required revision:
Rechecked export:
Final approval / date:

If actions need longer, extend or simplify the video. Preserve the account labels
and permission boundary in shorter cuts. A reproducible tutorial needs the
missing navigation and invitation steps. This review does not establish product
security, conversion gains or other business outcomes.

Blank planner: https://aitoma.ai/templates/video-storyboard
Question selection: https://aitoma.ai/guides/customer-questions-content-ideas
Public contact: hello@aitoma.ai