Training video
Nobody watches a training video for pleasure — the only success metric is whether the task gets done correctly afterwards.
What this is about
A training video teaches a defined skill to people who will have to perform it: operating a machine, running a process in a software tool, handling a customer situation. Its audience is already employed and often already impatient, so the format is built in short modules that can be watched at the moment of need and updated one at a time. That is a different job from the onboarding video, which orients newcomers and sets tone, and from the safety video, which discharges a legal duty to instruct. Production is usually a series rather than a single film: many short pieces, filmed on location or captured on screen, with a subject-matter expert beside the camera.
The format determines scope, crew and timeline — before the first location has been scouted.
What runs differently here
In planning terms, that means:
- Modules are cut along tasks, not along chapters of a manual, so a learner can jump straight to the one step they are stuck on
- The script gets a technical review before the shoot: a wrong sequence on camera trains the wrong sequence into everyone who watches
- Demonstrations need a second angle on the hands or the screen, because the wide shot never shows which button was pressed
- Anything that changes — software interfaces, tool versions, part numbers — is isolated into its own module so updates stay cheap
- Learners often watch on a phone in a noisy hall, which makes captions and clear on-screen labelling part of the shooting plan
What the plan has to deliver
A production plan is useful to this role when it provides the following:
- A module list with one learning objective per piece and the order in which they build on each other
- A script signed off by the person who is responsible for the process being taught
- A shooting plan that books the real machine, the real system access and someone competent to demonstrate
Common pitfalls
What most often goes wrong in practice:
- Producing one long film instead of modules, which forces every future correction into a full re-edit
- Letting a presenter demonstrate the task who does not perform it daily — experienced viewers spot it immediately
- Filming a software workflow with test data that looks nothing like what users actually see
With TillyGen
TillyGen breaks a training brief into modules with learning objectives, review steps and a shooting plan per location — including which pieces are built to be replaced later.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
How long should a training module be?
One task, one module, ending when the task ends. If a piece needs a summary to be understood, it was carrying two objectives and should be split.
In-house expert or professional presenter?
The expert demonstrates, the presenter can narrate. Credibility comes from hands that clearly know the machine; polish can be added in voice-over.
How do we keep the videos current?
Separate the stable parts from the volatile ones at planning time. When only the interface module changes, only the interface module gets re-shot.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.