Who this is for: Teams creating asynchronous product explanations for public pages.
What to prepare
- Recurring task and target viewer
- Configured-account prerequisites
- Exact labels and product terminology
- A confirmed finish state and next resource
Answer the questions a presenter would hear
Identify who is acting, what object they are handling and what already exists in the account. A video can begin in a configured workspace, but it should say so. Otherwise the viewer may confuse a recurring task with first-run setup.
This guide concerns a linear explanatory video, not an interactive product sandbox. Avoid labels that imply the viewer can click inside a recorded interface or create an account through the video itself.
Illustrative independent-viewing outline
A fictional workspace contains recurring sample review requests. The viewer wants to find one assigned request and inspect its due date. A 30-second planning outline can stand alone as follows.
- 0–5 seconds: “Find your next assigned review.” Identify the example reviewer account and say the workspace is already configured.
- 5–11 seconds: show the assigned-to-me filter and the product’s actual apply behavior.
- 11–18 seconds: highlight sample request R-051 and open it. Preserve the identifier and title across the transition.
- 18–25 seconds: hold the due-date and status fields with a callout explaining what to check before acting.
- 25–30 seconds: “Open the request to review its details.” Link the surrounding page to the next relevant explanation rather than introducing another task.
Give labels explanatory work
“Assigned to you” explains list scope; “Powerful workflow” does not. Use short labels to name the reason for an action or the meaning of a result. Keep essential labels available in the visual track when the page may be viewed silently.
Introduce unfamiliar product terms at their first appearance. If a “review packet” contains several requests, explain that relationship before using packet status as proof that an individual request is complete.
Review without adding spoken rescue
Ask a reviewer to read the storyboard and identify the starting role, selected filter and final result. Do not explain missing context during the check; record the gap and revise the film. This is a proposed review process, not a claim of completed audience testing.
If the task requires branching choices, create a longer training sequence or separate videos. A short linear demonstration can show one defined path clearly, but it cannot answer every decision a new user might encounter.
Review checklist
- The video identifies actor, task and starting conditions.
- The sequence makes sense without a live explanation.
- Labels explain scope and consequences.
- The final action matches what the viewer has just learned.