Industrial training video is an information-design problem first.

A company decides it needs a training video. They pick their most experienced person, hand them the SOP and point a camera at them. Twenty minutes later they’ve got a video that technically contains everything. Internal terminology, every step, every exception. And who’s going to sit through twenty minutes to find the one step they forgot?

Usually the biggest problem isn’t production quality. Sometimes it’s shot on a phone, sure. But a well-lit, well-shot version of that same video fails the exact same way. The company knows the subject too well, so they try to put all of it into one video.

That’s why I treat training video as an information-design problem before it’s a filmmaking problem. You have to decide what someone needs to learn, in what order and in what form. The camera comes after that.

An SOP and a training video do different jobs

The SOP should hold every detail. That’s what it’s for. When somebody needs to check a setting or the exact sequence, they open the document.

The video has a different job. It has to make the process understandable, show what someone actually needs to do, and make the important information difficult to miss. Film the SOP word for word and you get a video nobody finishes, and they still end up going back to the binder.

If it’s in the manual, it doesn’t automatically belong in the video.

I start with the person who actually knows it

Not marketing. The person who does the work, or the one who built the product. Give me the SOPs, the manuals, the existing PowerPoints, whatever the company actually uses. Then I go back to the subject-matter expert with questions until I understand it myself.

That last part matters more than people expect. Before video, I worked in training and product management, and the job was basically the same: take something complicated and make it make sense to someone seeing it for the first time. If I can’t explain a step, I can’t direct anyone else to explain it on camera.

What they need to see, hear or read

Once I understand the process, I split it up. What does someone need to see? What do they need to hear? And what’s better handled as text or graphics on screen?

Physical actions, controls and procedures should usually be demonstrated. Show the hands on the controls, in the order it actually happens. Numbers, settings, warnings and sequences are better reinforced with graphics. Same with anything happening inside a machine that the camera can’t show. Asking an expert to read out a list of settings while you watch them talk is about the least effective way to teach it.

One video, one task

I’d much rather make five focused three-minute videos than one 15-minute video covering five procedures. Each video should answer one clear question or teach one task. When someone on the floor needs a refresher on one thing, they shouldn’t have to scrub through fifteen minutes to find it.

Some tasks genuinely need more time, and that’s fine. The length should come from how complex the task is, not from somebody wanting every paragraph of the manual in there.

Getting experts to explain it on camera

I generally don’t ask technical people to memorize a polished script and perform it. They already know the subject. My job is to get that knowledge out of them in a way someone who doesn’t know it can follow.

So I have them show me the process, and I ask very simple questions while they’re doing it:

• What are you doing now?
• Why does that matter?
• What happens if I skip this?
• What should I be looking for here?

Then we shape those answers into something much cleaner. They still sound like themselves. Just easier to follow.

Alpha Controls is a good example. They’re in instrumentation and calibration, which gets technical very quickly. The content worked when we stopped trying to communicate everything the expert knew and built each piece around one thing the customer actually needed to understand. Same thinking whether it’s product education, internal training or an industrial process.

Where it ends up changes how you build it

The finished videos can live almost anywhere. Employee onboarding. An LMS or internal training portal. A knowledge base. Tablets on the production floor. QR codes beside the equipment. Dealer and distributor training. Even customer-facing product support.

That’s worth knowing before anything gets planned. Something a new hire watches at a desk during onboarding and something an operator pulls up on a tablet next to a running machine shouldn’t be built the same way.

What drives the cost

Cost usually goes up with the number of procedures and videos, how many machines or locations we need to capture, how much scripting and technical development it takes, and whether we need animation or graphics to explain things the camera can’t show.

Industrial access can change things a lot. Shutdown windows. Safety requirements. Limited time on the machinery. Needing more than one operator or subject-matter expert. Sometimes a process only runs for a short window, and that’s the window we have to get it in.

It works the other way too. If we can shoot several modules around the same machine, location and crew day, the cost per finished video comes down considerably. Another reason to plan training as a series instead of one video at a time. For rough numbers, see what a video like this costs.

So if you’re sitting on a stack of SOPs and a training problem, start by working out what each video needs to teach and where people will be when they watch it. Then bring in a camera. That order is most of the work, and it’s the part that decides whether anyone actually uses what you make.