Make a Tutorial Commercial Teach the Action Without Becoming a Manual
Make a Tutorial Commercial Teach the Action Without Becoming a Manual
A how-to brief usually arrives complete. Somebody has already written down every step, in order, because that's what the instructions say, and the instructions are correct. The trouble starts when you shoot all of it. Thirty seconds of tapping becomes a manual with a soundtrack, the person who was supposed to be helped never appears, and the film has no reason to exist except that the feature does.
The way out isn't to trim steps until the film fits. It's to choose one bounded action, be explicit about where the viewer starts, keep the step that actually causes the result, and hand the rest to instructions that can hold it. A tutorial commercial can be selective about its lesson without being misleading about the action it shows. Selective, not vague. That's the standard.
To keep this concrete, the examples below use an invented notes app and an invented task: move one open note into a folder named Receipts, then find it there later. The app, its screens and its behavior are stipulated for the sake of the argument. Nothing here describes a real product, and none of it has been checked against one.
Choose the one action the viewer should understand
Write three sentences before you write a shot.
Starting state: the note is open, title visible. Action: move it into the folder called Receipts. Visible result: the note's header now reads Receipts.
Those three sentences are the film's contract with the viewer. If you can't write them, you don't have a tutorial yet — you have a mood board with a voiceover. If you can write them but they keep shifting between drafts, that's usually a sign the brief is organized around features rather than around a person's problem.
That much is reasonable. Somebody spent a year on tags. But "show that the app keeps your notes organized" is a claim about the product, and it can be established in five seconds with a beautiful montage without anyone learning anything. "Move one note into a folder and find it again" is different. It creates an obligation. Once the film says do this, the viewer will try to do it, and the film now owes them a sequence that works.
That's the trade. A demonstration asks to be believed. An instruction asks to be followed. A film can do either job, but a film that starts out looking like an instruction and turns out to be a demonstration has spent the viewer's attention on a promise it never meant to keep. Give a feature montage the same running time as the lesson and it still hasn't taught the move — a shorter montage hasn't found a better way to teach. It has decided not to.
So pick the action from the place a person gets stuck, not from the place the product is proudest. In the invented example, the stuck place isn't opening a note. Anyone can open a note. It's the moment after, when the note is written and the person wants to find it again in six months without remembering what they called it.
Find the transition that cannot be skipped
Walk the approved operation in order and look for the joint: the place where a viewer could lose the connection between an input and its result.
Three things go missing in the edit, and all three are the same mistake — a wait, a confirmation, a condition.
In the invented notes app, the move shows a brief "Moving…" state before the note's header changes to Receipts. Cut that pause and the film teaches that confirmation is instant. A viewer who taps Move, looks at the header immediately, sees nothing yet and concludes the move failed may tap again or start hunting for the note somewhere else. The pause isn't decoration. It's the app telling the person to wait.
The header change is the confirmation, and it's the one beat that can't be deferred to a later film. Without it, the viewer sees a tap and no consequence, and "tap here" becomes a superstition rather than a cause.
The condition is the folder itself. The task says the folder named Receipts. If the viewer's app has no such folder, the real operation includes creating one first, which is a different sequence with different steps. A film can absolutely decide the folder already exists — that's a legitimate narrowing of scope — but the narrowing has to be visible. Put it on screen, or open on a folder list that plainly contains Receipts. A prerequisite that lives only in the writer's head becomes a viewer's dead end.
None of this is an argument for long films. Shortening repetitive explanation is free: if the film has already shown the folder list twice, a third showing buys nothing. Removing a required step is not free — it changes the lesson. The test is embarrassingly simple. Watch what remains and imagine performing exactly that. Does the note end up in Receipts, or does it sit there while nothing happens?
And when the answer is genuinely unclear, that isn't the treatment writer's call to make alone. What's required for correct use is a product decision, made by someone who owns the operation and knows the current authorized instructions. You can argue for pace. You can't quietly win that argument in the edit and hope nobody checks.
Use the person's purpose to select detail
The reason to move a note into a folder is retrieval. Not filing for its own sake — retrieval, months later, by someone who no longer remembers the title.
That purpose decides what the camera has to bother showing. The folder name needs to be legible, because the viewer will be looking for it later. The note's title needs to be legible, because that's how they'll recognize the note. The folder list needs to look like a place they can come back to.
Detail that serves the task earns its screen time. Detail that serves the feature list competes with it. In a film this short, the competition is direct.
Show a consequential choice and then its effect, in that order, close enough together that the viewer can connect them. In the invented example, the choice among folders is small but real: the film shows the folder list with Receipts among the options, then shows what choosing it produced. Cause, effect, stop. Don't cut away to a second feature and come back; the connection has a shelf life measured in seconds.
The step most often cut is the return. After the move, the film leaves the note, opens the folder list, opens Receipts and shows the note sitting there. On the page it looks like a repeat, and a pace-minded editor will want it gone. Keep it. The person's purpose was never pressing a button; it was finding the note again. The return is the only part of the film that demonstrates the thing they actually wanted.
Optional settings are where a selective film most easily starts lying, in both directions. If a tag chip sits on the note and the viewer never saw it applied, the reasonable inference is that the app tags things for you. If a pin appears in the header, notes may look pinned by default. The film never said either of those things. It didn't have to. Showing a result without its cause is a claim about the cause. The reverse also holds: leaving something out can imply it doesn't matter, so if a setting is the reason the task succeeds — sync, an account, a permission — then its absence changes the task, and it belongs in the film or in the handoff.
Where the film does stop, say so. A closing line or card pointing to the full instructions isn't an admission of failure. It's the boundary marker that lets the rest of the film be short without being misleading. The viewer should know they've watched a bounded lesson, not the whole operating guide.
Test the written route against the real operation
Before anyone shoots, read the treatment against the current authorized instructions, action by action, and check whether each depicted step corresponds to a real one. This is unglamorous work and it catches most of the trouble.
Then run the same three checks over the edit, because the cut is where problems get introduced. Did trimming remove the wait? Did the confirmation end up on the floor? Did the condition survive, or is the folder's existence still only implied?
There's a class of operation where this check isn't the right tool, and the correct answer is to change the lesson rather than the information. Anything irreversible, anything that spends money or affects health or opens someone else's data, anything where a wrong tap can't be undone — a commercial's runtime is probably the wrong container for teaching it. That isn't a reason to simplify the consequential part for the sake of pacing. It's a reason to teach a different action, or to use a format that can hold the whole thing. The notes task works as an example here precisely because getting it wrong costs almost nothing.
One more thing about what this check proves. Matching the authorized instructions shows the film describes the operation faithfully. It doesn't show that anyone learned it, remembers it, or can perform it, and it says nothing about whether they'll do it safely. Those are questions for a comprehension study with real viewers — separate work, with its own method. A treatment that lines up cleanly against the manual is accurate. Accurate is worth having. It isn't effective, and nobody should be told it is.
Where the film should end
Go back to the purpose. In the invented example, the last shot isn't another feature. It's the person, weeks later, opening Receipts and finding the note. That closes the lesson at the point it was meant to serve, and it returns the film to a human being — which is where it started, and usually where it should finish.
The viewer should come away knowing one action, understanding what makes it work, and knowing where the rest of the instructions live. That's a complete short film, and a bounded one.
What no amount of careful writing here supplies: screens, a working interface, a product owner's sign-off, or evidence about how an audience responds. The example above is an editorial plan built on a made-up app. A real one starts with the current authorized instruction and someone qualified to confirm what the operation actually requires. Until that exists, the film is a proposal — not yet a lesson anyone has learned.
Frequently asked questions
What should a tutorial commercial choose to teach?
It should choose one bounded action from the place a person gets stuck, not from the feature list. The piece recommends writing three sentences as a contract: starting state, action, and visible result. An instruction asks to be followed, while a demonstration asks only to be believed; a feature montage of the same length still hasn't taught the move.
Which beats are most often lost in the edit, and why do they matter?
The wait, the confirmation, and the condition. In the notes example, a brief 'Moving…' state tells the viewer to wait, the header change confirms the move, and the folder's existence must be visible if the task assumes Receipts already exists. Removing a required step changes the lesson; shortening repeated explanation does not.
Why keep the return after the action?
The person's purpose is retrieval, not filing. Showing the folder list, opening Receipts, and finding the note there demonstrates the thing the viewer actually wanted; cutting it as a repeat loses the payoff.
When is a commercial runtime the wrong container for instruction?
When the operation is irreversible, spends money, affects health, opens someone else's data, or cannot be undone after a wrong tap. The piece says that is a reason to teach a different action or use a format that can hold the whole thing, not a reason to simplify the consequential part for pacing.
What does matching the authorized instructions prove, and what does it not prove?
It shows the film describes the operation faithfully. It does not show that anyone learned, remembers, can perform it, or will do it safely; those require a comprehension study with real viewers. A real film also needs screens, a working interface, and a product owner's sign-off, while the example is an editorial plan built on a made-up app.