What you leave out of a motion system is part of the design, not a hole in it.
Quick answer: should everything go into a motion system?
No. A good motion system is defined as much by what it deliberately excludes as by what it templates. Formats that teams want custom, that carry unusual requirements, or that do not repeat enough to templatize belong outside the library on purpose, so the system stays coherent.
Why is exclusion a design decision?
Because a system that tries to hold every format holds none of them well. When you template the work that truly repeats and leave the rest out, each piece in the library earns its place and stays easy to use. The creative ops lead I spoke with was explicit about one such boundary, keeping certification video:
"outside the library"
on purpose. That was not a backlog item. It was a call that certification content had needs the library was not the right home for, so it lives elsewhere by design. Drawing that line is the same skill as designing a good template. You are deciding what the system is for, which means deciding what it is not for.
What kinds of video are worth leaving out?
The custom, the rare, and the ones with distinct production needs. Certification and training video is a common example, because teams often want it tailored per course, sometimes with AI voiceover, and produced on a rhythm that does not match the marketing library. Forcing that into a template built for repeatable brand content would bend both out of shape. Leaving it out keeps thelibrarysharp for the work it was built for.
| Format | Templatize? | Why |
|---|---|---|
| Repeatable brand and product clips | Yes | High volume, consistent structure |
| Social cutdowns of existing assets | Yes | Same recipe, many outputs |
| Certification and training video | No | Custom per course, distinct needs |
| One off executive or event pieces | No | Too rare to earn a template |
How do you decide where the line goes?
Ask whether a format repeats enough, holds a stable shape, and shares the library's production needs. If a format is produced often, looks structurally similar each time, and follows the same brand rules, it belongs in the system, where Capsule customers turn that repetition into 8x faster production. If it is custom every time, or carries requirements the rest of the library does not, put it outside and let it be its own thing. The mistake is treating outside the library as failure. A named boundary is a feature, because it tells everyone exactly where to go for what.
A worked scenario
A creative ops team is standing up a motion system. They templatize product explainers, customer story cutdowns, and social snippets, all high volume and consistent. Certification video comes up, and the pull is to add it because it is video too. Instead they leave it out, noting that courses want custom treatment, some use AI voiceover, and the cadence follows the learning team, not marketing. Six months on, the library is fast and trusted because every template in it repeats cleanly, and certification video is served well by its ownprocessnext door. Had they forced certification in, they would have a library full of exceptions and a template no one trusted. The exclusion is why the inclusion works.
FAQ
Does leaving something out mean it is unimportant?
Not at all. Certification video can be mission critical and still belong outside the library. Importance is not the test; repeatability and fit are.
Will excluded formats drift off brand?
They can if you ignore them, so give them their own light guardrails rather than pretending the library covers them. A separate home is not an unmanaged one.
How often should the boundary be revisited?
Whenever an excluded format starts repeating in a stable shape. That is the signal it may have earned a template after all.
Who should draw these lines?
Creative ops, close to the teams making the work, so the boundary reflects real production patterns rather than a tidy diagram. Pair it with yourtemplateowners so inclusion and exclusion are decided together.