How to make a product onboarding video that helps someone start

Imagine a fictional scheduling product for a small repair shop. The owner's first useful result is a booking page with one available appointment type. Creating an account, choosing a timezone, and setting hours may be necessary, but they aren't the reason the owner signed up.

For this example, the video ends when the owner opens a test booking page and sees the appointment time they intended to offer. That gives setup a purpose. We aren't claiming this workflow belongs to Impractical or that we've measured an onboarding improvement; it's a worked example for choosing the scope.

Write the success state in ordinary language before writing narration. 'A customer can see an available repair consultation' is something you can show. 'Your workspace is optimized' leaves both the viewer and the person producing the video guessing what counts as finished.

Tell the viewer which account state the recording assumes. In the repair-shop example, perhaps they need to be the workspace owner and have an empty schedule. If a teammate without permission can't create an appointment type, that distinction belongs before the first instruction, not after they get stuck.

Use a clean demo account that matches the new-user experience. A populated internal account may have shortcuts, saved settings, or permissions a new customer doesn't have. Recording from it can remove exactly the friction the onboarding video needs to explain.

If there are several common starting paths, split them rather than squeezing every branch into one sequence. A small business creating its first schedule and an employee joining an existing schedule need different instructions. Give each video a title that helps people choose the relevant path.

Most clicks don't need a speech, but some settings deserve context. Choosing a timezone changes how the repair shop's availability should be interpreted. Selecting an appointment duration changes which slots can be offered. Explain those choices while the corresponding control is visible.

Avoid reading every label on the screen. The useful narration tells the owner why they're selecting a value and how to check it later. For example, 'Choose the hours when someone can actually take a consultation' gives the availability step a reason without reciting the whole form.

Keep optional customization out of the first task unless it affects completion. The logo, accent color, and welcome message can wait if the person still hasn't made an appointment available. You can link a separate customization guide after they've reached the first result.

This is a hypothetical brief for an instructional video. Unlike a short launch announcement, it needs enough continuity for a person to follow along, including the screens where they make decisions.

Starting state: a new workspace owned by the viewer, with no appointment types configured.
Goal: publish one repair-consultation booking page and verify an available time.
Show the owner creating the appointment type, choosing its duration, confirming timezone, and setting working hours.
Explain the choices that affect availability. Keep the save or publish action and its confirmation visible.
Open the customer-facing booking page and compare the available time with the settings just entered. Use sample shop details.
If no slots appear, show where to check the schedule and duration rather than suggesting random retries.
Finish with a link or button to create the viewer's own appointment type, followed by optional customization help.

The person who needs the video most may be the one who doesn't reach the same result. Choose one common mismatch to explain, using verified product behavior. In our example, an empty booking page could require checking availability settings, but the real cause and recovery must come from the actual product.

Show how to recognize the mismatch and where to go next. A short note beside the relevant step can be enough, while a complicated troubleshooting path deserves its own help article. Don't tell everyone to restart or reconnect an account unless that is the supported fix for the condition you're showing.

Keep labels consistent with the current interface. If the product says 'Appointment types', don't alternate between services, events, and booking options in narration. Familiar wording is especially helpful when viewers pause the video and search their own screen for the next control.

An onboarding video is often watched in pieces. Give each step a recognizable beginning, leave enough time to read the important setting, and avoid cutting away before the save confirmation. If the host supports chapters, name them after the task steps so people can return to the point where they stopped.

Provide accurate captions and a written version of the instructions. W3C explains that captions include relevant speech and non-speech audio; review generated captions instead of assuming they preserve product names and numbers correctly. The written steps also give people a practical reference when replaying a whole scene would interrupt their work.

Check the video with someone who hasn't configured the product before. Ask them to complete the task, and note where they need information the video omits. Don't turn a successful session into a conversion claim; use what you observe to improve the instructions.

W3C: creating and checking captions

Assign someone to review the video when the relevant flow changes. Keep its source recordings and a short list of the controls it references, so a renamed setting doesn't remain in the published tutorial for months. A small, task-specific video is easier to update than a complete product tour.

The end should send the viewer back to the task with a clear next action. Once the repair-shop owner sees the correct booking availability, optional branding and team setup can follow. The first video succeeds by helping them reach that specific state, not by making them watch every other tutorial.