The template
Help a new user complete one valuable first task with a short guided walkthrough.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. Welcome | Show the first screen a new user encounters. | Set one achievable first-use goal. | Is the viewer's role clear? |
| 2. Prerequisite | Show any required account or setup state. | Explain what to prepare. | Is setup actually required? |
| 3. First task | Demonstrate the essential action. | Guide each step in order. | Can a new user follow without coaching? |
| 4. Success check | Show the expected completed state. | Tell viewers how to confirm it worked. | Does the app display this confirmation? |
| 5. Next help | Show where to find the next guide. | Name support or the next milestone. | Is the help link still current? |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Choose the first task from evidence about where new users get stuck or what they need to accomplish, rather than trying to introduce every feature. State required access, data or setup before the first step. Use the same labels a new user will see and pause long enough for the viewer to follow. Test the draft with someone unfamiliar with the interface; note where they pause, choose a different control or need a term explained. If the task changes by role or plan, make the variation explicit and provide a route to the correct version. Keep support links and screenshots current as the interface changes.
Prepare the final handoff
Publish the guide near the step where new users need it, and provide a transcript or text guide for viewers who cannot use video. Record the product version and owner, then watch for interface changes and user questions that suggest the instructions need revision. A video is one part of the onboarding path, not a replacement for usable in-product help.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
A new customer should be able to complete one useful first task after watching. State what they need before starting, guide the essential steps and point to the next resource.
Evidence and review
Ask someone new to the product to follow the steps. Confirm terminology, account prerequisites, permissions and plan limits with the product or support owner.
Do not overload the first-use path with every option. Put advanced setup, troubleshooting and role-specific branches into their own videos or written guides.
A worked example
Illustrative scenario, not a customer story: Welcome a new user, show the prerequisite, guide one first task and finish with where to get help. Put optional setup in a separate resource instead of lengthening the first-use path.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
Should onboarding be one long video?
A short series organized around milestones is often easier to use and maintain: first setup, first task, and next steps. Link to written help for branches and exceptions.
How can I check if the onboarding video works?
Ask a new user to complete the task using the video and its linked material, without coaching. Note where they pause or choose a wrong control and revise those moments.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.