Animation for what a camera cannot show.
Systems, workflows, frameworks and machinery seen from the inside — for subjects where filming the outside of the thing tells you nothing about what it is doing.
What we make
The modules in this category.
Process and workflow explainers
A process shown moving, with the handoffs and the waiting between steps visible — the parts a flowchart flattens into equal-sized boxes.
System and architecture walkthroughs
How data moves, where it is held and what talks to what, at whatever level of abstraction the audience actually needs.
Machinery and technical internals
Cutaways, exploded views and mechanisms shown in motion, for equipment nobody can safely open in order to demonstrate it.
Frameworks and concepts
Abstractions given a consistent visual language and reused across a programme, so the same shape means the same thing in module six as in module one.
Who it's for. Process, product, policy and technical training — especially engineering, manufacturing and financial services, where the honest answer to "what would we film?" is nothing.
Where we stop
What we'd tell you to shoot instead.
Anything you could simply film
If the subject is a person doing a thing in a place, film it. Animating what a camera could have captured reads as a budget decision, and viewers read it that way too.
Animation as decoration
Motion should carry meaning. If a sequence would work as a still diagram with a voice over it, we will say so rather than bill you for movement that teaches nothing.
When is animation the right choice over filming?
When the subject has no filmable surface: internals, data flows, abstractions, or anything at a scale or speed a camera cannot resolve. If the honest answer to "what would we point the camera at?" is a building exterior and a stock shot, animation is not a compromise — it is the only medium that shows the subject.
Can you animate our existing process diagrams?
Yes, and starting from your real documentation rather than a summary of it is what keeps the result accurate. What we will not do is animate a flowchart step for step: a diagram that already fails to land does not improve by moving.
How accessible is animation compared with filmed video?
It needs more care, not less. Where the visual carries meaning the narration does not — which is most of the point of animation — WCAG 2.1 AA expects audio description, so we build that in rather than adding captions and calling it done.
What happens when the process changes?
We hold the source files, so a renamed stage, a changed threshold or a new step means re-rendering that sequence. This is where animation is at its strongest against a conventional shoot: there is no set to rebuild and nobody to bring back.
Will it match the rest of our training?
It should. We build one visual system for the programme and reuse it, so a shape that means "approval step" in module one still means that in module six. Animation done module by module is where training libraries start to look like they came from four different suppliers.
Will it work with our LMS?
Yes. SCORM 1.2 by default because support is effectively universal, with SCORM 2004, xAPI or cmi5 on request, plus captions, transcripts and audio description. We test the package in your environment before handover.
Related modules.
Product training that keeps up with the product.
Feature explainers, software walkthroughs and internal systems training — for products that ship changes faster than training can be rebuilt.
Safety training that shows the actual sequence.
EHS, plant safety, permit-to-work and standard operating procedure — for workforces that read the SOP in a second language, if at all.
Training that fits between two shifts.
One objective per episode, sized for a phone and for the gap someone actually has — and extendable a module at a time rather than commissioned all at once.
Or see all eleven module types.
Send us the one
you're dreading.
One module is enough. We'll come back with how we'd make it, what it would take, and a free audit of the curriculum you already have.