User onboarding · Activation

Onboarding videos people actually finish.

One task per video, under two minutes, narrated clearly, with the thing to click lit up. Made from a script, so there are twenty of them instead of one long one.

Why users skip your onboarding video

It is eleven minutes long, it starts with the login screen, and the part they need is at 7:40. Short, task-sized videos placed next to the feature are watched; the grand tour is not. With Tuti Tuti the grand tour is one script, and each chapter exports as its own short file. The welcome video and the twenty feature videos come from the same afternoon.

What makes onboarding video work

The habits of videos that get finished, built in.

01

One task per chapter

Blank lines in the script make chapters; each exports as its own file with its own name.

02

The thing to click, lit

A spotlight ring on the exact element while the narrator names it. No hunting.

03

Captions on screen

Word-synced, so a user with the sound off, or in a second language, still follows.

04

Written for a listener

Every button gets a location, every typed value is spoken. It works as audio alone, which also makes it accessible.

05

Current after every release

A changed screen means re-rehearsing one chapter and exporting one file.

06

Place them anywhere

Help centre, in-app empty states, a tooltip's Learn more link, the welcome email.

Interactive tours and videos

Tooltip tours teach the click; videos teach the why.

Use an in-app tour for the first three clicks and a short narrated video for the task that needs context. Tuti Tuti makes the second kind cheap enough to have one for every feature.

An onboarding library in a day

1

Write the tour as chapters

Each chapter is one task a new user must learn. Open each with a transition, then the path.

2

Rehearse once on a demo account

Seed the demo data from the script so every screen looks lived-in.

3

Export one file per chapter

Place each next to its feature. Re-render only what changes.

Onboarding videos: the questions people ask

Users don't watch our tutorial videos. What works instead?
Shorter ones, closer to the feature. A two-minute video on the empty state of the Orders page gets watched; an eleven-minute tour linked from the welcome email does not. Tuti Tuti exports one file per chapter so the short, placed videos are no extra work.
Interactive product tour or video, which is better for onboarding?
Tours (tooltip sequences in the app) are best for the first few clicks. Videos are better when a task needs explanation, context, or a why. Most teams end up with both. The video side is the expensive one to maintain by hand, and the one Tuti Tuti makes cheap.
How do I make onboarding videos for a SaaS without a video team?
Write the onboarding path as a script: one sentence per step, named by the on-screen labels. Rehearse it once in the extension, export, place the files. A person who can write a help article can do this.
How often should onboarding videos be updated?
Every time the screen they show changes. That is the honest answer, and it is why hand-made videos go stale. With a script, the update is re-rehearsing one chapter and exporting it, ten minutes at most.
Should the video show the login screen?
No. Start from the first screen that matters. Tuti Tuti starts recording on the page where you press Export, so the login is simply not part of it.
Can I make onboarding videos for a mobile app?
Tuti Tuti drives web apps in Chrome today, including responsive layouts at a phone width. Native iOS and Android are on the roadmap.

Twenty short videos, one script.

Make the onboarding library you keep meaning to make.

Tuti Tuti - powered by Pandacat.