The Boss says The Boss says, if your tutorial needs a tutorial, it probably has one step too many.

How to Make a Video Tutorial

Updated · 6 min read · by the Nine crew

A good video tutorial shows one task, one path, and one result. Start with the question people ask most, script the steps, record clean audio, and test it with one person before you publish.

Your idea, ready to go“Need to show how to submit an expense report, reset a password, or update a shipping address? Start there.”

Make this film

Sign up takes a minute. The idea is filled in, and you can change every word.

Need to show how to submit an expense report, reset a password, or update a shipping address? Start there.

The job is not to make a film about the process. The job is to help someone finish the process. That saves time for everyone.

Start with one job, not the whole process

Pick one task that is short enough to explain in one sitting. A short tutorial can still be useful, because people can find it again later.

Write the exact outcome first. Say what success looks like in plain words. For example, “submit an expense report,” “reset your password,” or “change your delivery address.”

Skip background unless it helps someone finish the task. People do not need the history of the form. They need the next click.

Long process? Split it into two or three films. That is better than one crowded video that nobody finishes.

Write the tutorial like a checklist

Use one step per sentence. Keep each line short enough to read in one breath. If a step has two actions, split it.

Say the button names, menu names, and folder names exactly as they appear. “Click Submit” is better than “Send it over there.”

Read the script out loud. If you trip, shorten it. If you need a second take on paper, the viewer will need one too.

  1. Step 1

    Pick one task. Write the result you want at the top of the page.

  2. Step 2

    List the steps in order. Keep each step small and direct.

  3. Step 3

    Write the script aloud. Use the same words the viewer will see on screen.

  4. Step 4

    Match each line to a screen. Show the form field, button, or page that proves the step happened.

  5. Step 5

    Record and test. Watch it with one new person before you publish.

Plan the screen before you record

Decide what the viewer should see on each step. It might be a page in a browser, a form field, a confirmation box, a hand, or a product.

Use wide shots for desktop steps and close shots for small parts. A tiny checkbox on a phone screen needs more room than you think.

Leave room on screen for text, arrows, or captions. Crowded frames make simple work look harder than it is.

For website steps, show the cursor moving to the exact place. A pointer that jumps from corner to corner makes people lose the thread.

Tip from Story A cursor that moves too fast is hard to follow. Slow it down, then slow it down again.

Record clean audio and simple visuals

Use one mic and one quiet room. Bad sound ruins good teaching. A plain voice in a quiet room beats a fancy setup with echoes.

Speak slower than normal conversation. Not painfully slow, just slower than your first draft wants to go.

Pause between steps so the viewer can catch up. That pause is part of the lesson.

Avoid shaky camera moves, tiny text, and fast clicks. If the viewer must rewind twice, the recording needs another pass.

Edit for the person who has never done this before

Cut anything that repeats what the viewer already saw. Repetition is useful in a classroom. It is annoying in a short video.

Add labels only where they help people stay on track. Name the field, the tab, or the button, then stop.

Keep the ending short. Tell people what to do next, where to ask for help, or what success looks like.

Check the tutorial on the same device people will use. A desktop cut can hide tiny phone problems, and a phone cut can make a desktop page look cramped.

If you want a shorter cut for another use, a separate edit can help. For that, see A long, a short and a snippet from one film.

Common mistakes and the fix

MistakeFix
Covering too many tasks in one video.Make one film per task. If people need three jobs, make three films.
Using vague words like “do the thing.”Name the exact button, menu, or step.
Talking over a fast screen recording.Slow the screen or the voice, preferably both.
Making it pretty but hard to follow.Show the field, button, or result first. Add polish after the path is clear.
Forgetting the final result.Show the finished screen or completed step at the end.

Another common miss is starting with the company story. The viewer does not need a speech before the first click. They need the first click.

Leaving out tiny steps causes trouble too. If a task includes a login, a save button, or a confirmation box, say it. Tiny steps cause big confusion.

How to tell if it worked

Ask one new person to follow the tutorial without help. Do not coach them unless they get stuck for a long time.

Watch where they pause, rewind, or hesitate. Those spots tell you where the tutorial got muddy.

Use this pass or fail check: can they finish the task, can they point to the next step, and can they say what success looks like?

If the answer is no, the script is too long or one step is missing. Fix the film, then test it again.

A quick check is enough. You do not need a big study. You need one honest test with a person who has not memorized the process.

When animation helps more than a screen recording

Animation works well when the process is abstract, safety related, or hard to film cleanly. It can also help when the real screen is messy, private, or changes often.

It is also useful when you want the same tutorial in wide, tall, and square shapes. One film can fit a website, a phone, and a feed.

A film can start from a sentence, a script, a document, a voice recording, or a website address. Nine can do that, and a film of your own comes with a plan. The details are on /pricing.

When you have a website already, you can paste the web address on the front page and see your own colours first. That preview is free and needs no account.

For a service change or public update, a spec film like this one shows how clear a simple explanation can be. It is a spec film, made from the brand's website alone.

If the tutorial needs more than one language, make one film per language from its own translated script. That keeps each version clear.

Ideas you can make

  • Reset a Password in 45 SecondsA short tutorial for a new hire named Jonah, showing how to reset a forgotten password on a work laptop. Keep it to one screen, one login page, one final success screen.Make this film
  • Submit an Expense ReportA clean staff training film for Priya, showing how to upload a receipt, fill in the amount, and hit submit. Make every step one sentence, with the exact button names on screen.Make this film
  • Find the Help PageA customer support tutorial that shows where the help menu lives on a website, how to open it, and how to send a message. Use a calm voice and big labels.Make this film
  • Book a Conference RoomA workplace how-to for a team member named Alex, showing how to check availability, pick a time, and confirm the booking. End with the room name and time visible on screen.Make this film
  • Update a Shipping AddressA customer tutorial for a small store called North Pine, showing how to open account settings, edit the address, and save changes. Keep the cursor slow and the finish screen clear.Make this film
  • One Task, Two DevicesA comparison film that shows the same simple process on desktop first, then on phone. Useful for training teams that use both, and a good reminder to keep each version short.Make this film

Questions people ask

How long should a video tutorial be?

Short enough that one person can finish the task while watching. For one task, use the shortest version that still includes every needed step. If the process runs long, split it into separate films.

Should I use a voiceover or captions only?

Use voiceover if people need to hear the order of steps. Captions help too, especially for noisy places or silent viewing. For a tutorial, voice plus on-screen text usually works best.

Is a screen recording better than animation?

Screen recording is great when the task happens on a computer or phone screen. Animation is better when the process is hard to film, hard to show safely, or easier to explain with simple shapes and motion. Pick the one that makes the next step obvious.

How do I make a tutorial for staff and customers at the same time?

Start with the shared steps. Then keep the language plain and skip internal jargon. If staff need extra detail that customers do not, make a second version.

What format should I export for phone and web?

Pick the shape that matches where people will watch. Wide works well on websites. Tall works better on phones and social feeds. If you need all three, make versions in wide, tall, and square.

Your idea, ready to go“Need to show how to submit an expense report, reset a password, or update a shipping address? Start there.”

Make this film

Sign up takes a minute. The idea is filled in, and you can change every word.

Small businessHow-to & craft