Most people who need to explain something complicated are not video people. They are the person who knows the subject: the trainer, the compliance officer, the professor, the operations lead. For example, one of our customers, a professor of medicine, said: he knows the science and can tell you the medicine, but making something look slick was never how his head worked.
The comms team could help in theory, except they don't have time. A manager at an ambulance service told us his comms team is really good but hasn't got time for this sort of thing. So it lands back with the person who understands the material.
A director of education at a pharmaceutical company, who has been making these for years, says the slow part isn't building the video. It's deciding what he wants to do.
Which is exactly what this guide is for. Below are six structures, grouped by the four jobs people usually need one for: explaining a concept or a process, getting a policy or a change across, onboarding someone new, and winning over a buyer who's nervous. Find the job, take the shape, and most of your script decisions are already made. There's a short list at the end if you want to skip straight to it.
First, earn the five seconds
People talk about keeping videos under two minutes as though two minutes is the target. It isn't. The same customer from the ambulance service reckons his colleagues won't watch even a two-minute video. They are scrolling, half-reading a bulletin, deciding in five or ten seconds whether this is worth their attention.
So the opening has to do real work. Not a logo, not a title card, not throat-clearing. Name the problem the viewer already has, or show the thing that makes them think "wait, that's my job."
What whiteboard is good at
The hand tells people where to look. It draws in one spot at a time, in the order you want them thinking, so the "one point per moment" rule happens naturally. You draw a thing, it lands, you draw the next. That progressive reveal is doing more than pointing. It keeps how much the viewer has to hold in their head at any moment low, which is exactly what a complex idea needs.
A peer-reviewed study of 521 adults (Smart Learning Environments, 2025) taught the same material in five formats with the same script and narration throughout. The whiteboard version scored highest for memory retention, and the gap was still there when they brought people back a week later. The thing that made the difference was watching the content get drawn.
You also get to decide what stays and what vanishes. Let a whole diagram build up and it's all sitting there at the end, so you can pull back and show how the pieces connect without redrawing anything. Or fade and erase to clear the canvas when you're moving to a new idea.
Explaining a concept or a process
These are for when the only job is getting someone to understand something.
What → Why → How. Say what the thing is, then why it's worth caring about, then how it works. That order matters. People can't take in how something works until they know what category it's in and why they should bother.
Overview → step → step → recap. For anything that's a sequence. Tell them how many stages there are up front, walk through each one on its own, then zoom out to the finished thing. Whiteboard gives you that closing recap for nothing, since the steps are all still on the canvas.
Parts → how they fit → the whole. For a system, where the pieces relate but aren't in a line. Start with the fuzzy whole, bring in each piece one at a time, draw the links between them, then pull back and let it resolve.
Templates that already have these shapes: Whiteboard Explainer for What / Why / How, Step-by-Step and Problem-Solving Process for a sequence, and The Water Cycle Explainer or Mind Map for a system of parts. Longer piece to structure? The 7-Point Whiteboard Story gives you the beats.
Open the Step-by-Step template →
All three need restraint, and restraint is hardest for the person who knows the subject best. One founder described herself as a wordy person. She gives more detail than she should, runs long, and then the questions start and everyone gets flustered. Experts do this. Beginners don't have enough to say.
So: one idea at a time, and cut anything that isn't pulling its weight. Hang the new idea on something the viewer already knows where you can. And show why the obvious simpler approach doesn't work, or the complicated real answer feels arbitrary.
Parts-and-whole also fixes a particular workplace problem: two teams who each think the other's job is simple. An ambulance service and the hospitals it delivers to had that, each side holding a different picture of how the other works and why certain data gets recorded when it does. Draw both halves of the process in order and you get further than another meeting will take you.
Explaining a policy or a change
A policy isn't a concept and it isn't a pitch. It's a rule that lands on the viewer, and their questions are selfish: does this affect me, what do I have to do differently, what happens if I ignore it. Answer those.
This is the material that most often gets shipped as a text-heavy module nobody reads. An instructional designer at a large health insurer put it as her learners receiving chunks of very dry regulatory content. She wanted video wherever she could get it in, for that reason and no other.
What's changing → why → what it means for you → what to do. The "what it means for you" part is the one everyone leaves out, and it's the only reason anyone pressed play.
Bend it. If people won't know whether it applies to them, lead with who it's for. If it's a compliance thing with teeth, go with the rule, then the reason behind it, then the consequences of ignoring it. If you're updating something people already know, say plainly what's staying the same, or they'll assume everything changed and panic.
Whatever the variant, keep the reason in. A rule with a reason attached feels fair. The same rule with no reason feels like someone throwing their weight around.
Policies also change, which is the argument for building this yourself as a project you can reopen rather than commissioning it. When the rule shifts next year you want to redo the two scenes that moved, not the whole thing.
Templates to start from: Health & Safety, Training Template, or Big Announcement when the change itself is the news.
Onboarding new staff
"Onboarding" is four or five different jobs sharing a word, and each wants its own shape. Trying to cover them in one long induction video is the usual mistake.
A business owner training a network scattered across a hundred countries gave the honest reason for making them: he doesn't want to hold everyone's hand for the rest of his life, and sure as the world, he's going to forget to tell someone something. A recording says the same thing every time. Another customer set out to turn her company's staff handbook into an onboarding video for the same reason.
- Welcome: who we are, how things work here, where you fit, what happens next. This one's about belonging and orientation, not facts.
- Tool training: what it's for, where it lives, how to do the main thing you'll use it for, where to get help. Anchor it on the one task they'll actually do, not a tour of every button.
- Process training: when this comes up, what you do, who else is involved, what a good result looks like. That last part is the bit internal training almost always forgets.
- Role and expectations: what you own, what success looks like, how you'll be supported, and where your job stops. Telling someone what isn't theirs, and when to escalate, saves a lot of grief later.
Don't try to be complete. A new starter can't hold it all in week one, so make several short videos in a sensible order rather than one marathon. End each on something to go and do, or you get passive watching and no change in behavior.
Templates to start from: New Employee Onboarding for the induction itself, Personal Introduction for the welcome, and HR Perks and Benefits for the practical side.
Open the New Employee Onboarding template →
Persuading a serious buyer
When you're selling something complex, whether that's professional services, machinery or technical kit, the buyer isn't short on desire. They're worried about risk, and they answer to other people. These shapes work by building trust and taking the risk off the table, not by turning up the volume.
Problem → what it's costing → solution → proof. The cost step is the one to get right. Put a number on what the problem is costing them, and buying from you reads as saving money rather than spending it. Then finish on evidence, because this kind of buyer won't move on your say-so.
Why change → why now → why us. A B2B buyer has to agree to three separate things before you win, in that order, and most videos skip the first two and go straight to boasting.
Their goal → what's in the way → how you clear it → what it looks like after. Keeps the buyer's outcome in the middle and makes you the one removing obstacles rather than the star of the show.
Give proof its own moment on screen, and make it real: a number, a named client, a certification. If you're cutting for time, cut something else. And spend most of the runtime on why they should change at all rather than on how good you are. "Should we do anything?" is the harder yes to win.
Templates to start from: Problem to Results, which follows this shape almost exactly, plus Case Study and Client Testimonial for the proof beat.
Open the Problem to Results template →
Which one to grab
Name the job and the shape follows:
- Teaching an unfamiliar idea: What / Why / How
- Explaining a sequence: Overview / steps / recap
- Explaining how parts fit together: Parts / how they fit / whole
- Getting a rule or change across: What's changing / why / what it means for you / what to do
- Bringing someone up to speed: the matching onboarding shape
- Winning a cautious buyer: Problem / cost / solution / proof, or Why change / now / us
None of these are clever. They're just the orders in which people can actually follow things, which is most of the work when the material is hard.
Once you've picked a shape, how to storyboard an explainer video in five steps covers turning it into something you can build.
.png "VideoScribe")
.jpg)
COMMENTS