Tutorial / How-To

What this format actually is

A tutorial is a promise with a deadline. The viewer arrives with a task they cannot complete, and they leave having completed it. Everything else — your personality, your production values, your opinions about the subject — is subordinate to that transaction. It is the most transactional format on this site, and that is its strength rather than a limitation.

The distinction that matters is between teaching a task and teaching a concept. If someone finishes your video understanding how a thing works but has not done anything, you have made an explainer. If they have a working result on their screen or their kitchen counter, you have made a tutorial. This sounds pedantic until you look at the retention graph: tutorial viewers abandon the moment they realise no concrete outcome is coming, and explainer viewers abandon the moment you start walking through steps they did not want.

Why it survives when other formats don't

Tutorials have the longest useful life of any format here. A good one keeps arriving in search results for years, because the question that produced it — "how do I do X" — gets asked continuously by a rolling population of people who have just encountered X for the first time. The audience never runs out. It replaces itself.

That also means the growth curve looks wrong compared to other formats. A tutorial channel does not spike. It accumulates. Six months in you will have far fewer subscribers than someone who spent those months on reaction videos, and in year three you will have a library that earns while you sleep and they will have a back catalogue nobody watches. If you need visible progress to stay motivated, know this about the format before you commit to it.

The other structural advantage is intent. Somebody searching for how to do a specific thing is closer to a purchase than almost any other viewer on the internet. That is why tutorial channels monetise well below the subscriber counts you would expect, through affiliate links, their own products, or simply being the person a company hires because they clearly know the thing.

What makes a bad one

Three failures account for most tutorials that go nowhere.

Burying the outcome. The single most common mistake is spending ninety seconds on context before showing what the viewer will end up with. Tutorial viewers are not deciding whether they like you; they are deciding whether your outcome is the one they want. Show the finished thing first. If it is not what they wanted, letting them leave in ten seconds is a favour to both of you.

Teaching from memory. Doing the task while recording exposes every gap in your understanding, and that is good — but rehearsing it until it is frictionless removes the very thing that makes tutorials useful. Leave in the moment where the dialog box is not where you expected. That is where beginners actually get stuck, and it is systematically absent from polished tutorials.

Choosing tasks nobody is stuck on. The best tutorial subjects are not the interesting parts of your field. They are the tedious, badly documented, universally required steps that everyone has to get through and nobody enjoys explaining. If the official documentation is good, you are competing with it for no reason.

The honest downsides

You will not become known. Tutorial audiences are loyal to the problem, not to the person solving it, and they will happily watch a competitor tomorrow. Building a personal brand on tutorials takes substantially longer than on almost any personality-led format, and some people find that dispiriting enough to quit.

The format also ages badly in fast-moving subjects. A tutorial for software that redesigns its interface annually is a maintenance obligation, not an asset. Either pick durable subjects or accept that you are signing up to re-record.

And it is genuinely crowded. Nearly every practical topic has a hundred tutorials already. The way through is not better lighting — it is choosing the specific version of the task that the existing hundred all skip, or being noticeably faster and clearer about the same one.

Where to start

Start with the thing a colleague asks you about most often. You already know the explanation works, because you have given it before and watched it land. That is more validation than most first videos get.

Keep it under ten minutes. Show the result first. Screen-record if you can, because it removes lighting, framing and camera confidence from the problem entirely, and none of those things are what makes a tutorial good. Publish three before you judge whether the format suits you — one tutorial tells you almost nothing, because search takes weeks to decide what to do with it.