Creative capacity during a system migration: why the video queue goes dark until June
Quick answer: what is creative capacity during a system migration?
Creative capacity during a system migration is the share of a creative team's hours that survives a platform cutover landing on top of their normal queue. It falls hard, and video falls first, because video is the longest single job in the queue and the easiest one to push to next quarter.
What happens to creative capacity during a system migration?
It gets spent twice. The creative team lead at a global medical device manufacturer described her spring to me in one breath.
It is a really busy spring for us. We've got some major systems migrations happening on top of our regular day to day. So it is, things are tight until June, but we probably can find some time.
Read the timeline in that. Four months in which the animation requests keep arriving and the animation stops shipping. Nobody cancelled the migration and nobody cancelled the launch video, so the queue absorbs both, and the requesters find out by watching their tickets age.
A migration consumes creative hours and produces no creative output: data validation, permissions mapping, asset auditing, and a long run of small meetings. None of it shows up as a deliverable, so the team just looks slower.
Why does a systems migration stall the video queue before anything else?
Because video is the only thing on the list that cannot be finished in an afternoon by whoever happens to be free. The same team lead described the range she covers:
It's kind of all over the gamut, like what my team typically would be doing most of the time would be animation stuff. But we also the business, does, you know, technology demos, illustrated, technology, kind of explainer, videos as well as promotional kind of feel good stuff.
Four categories, one team, and animation is the default. Animation also carries the longest chain of dependent steps: storyboard, illustration, build, revision, brand check. A deck gets pushed and somebody stays late. A ninety second animated explainer gets pushed and it moves a quarter.
Which video requests can keep moving without the creative team in the loop?
Sort the queue by how much of each request needs a motion designer's hands. Whatever mainly needs a person who knows the subject keeps moving during a migration.
| Request type | What it actually needs | Can it move during a migration |
|---|---|---|
| Animated set piece for a launch | Illustration, storyboard, motion design, brand review | No. This is the work the migration displaces. |
| Technology demo | Screen capture, an accurate script, locked titles | Yes, if the product owner can fill a template |
| Illustrated explainer | New illustration and custom animation | No, unless the illustration already exists |
| Promotional stat or claim card | One number, one claim, an approved template | Yes. Highest volume, least craft variance. |
| Feel good promo cut from existing footage | Selection, captions, title cards, ratio versions | Yes, if the joins are specified in advance |
This split is what tiering video requests by how much craft each one needs exists for. The bottom two tiers are where a migration quarter gets its air back.
What does a frozen video queue cost the people who requested the video?
They stop asking. A marketing team at a collaboration software company described the same pressure with no migration involved: limited bandwidth, repurposing that eats the week, and a standing tension between brand polish and execution speed. When the queue is visibly blocked, the requester either ships something off brand themselves or ships nothing.
Our own figure for the underlying problem is that 30% of creative time gets spent on tedious tasks. During a migration that share stays flat while the cutover deadline takes priority. The tedious portion is also the most templatable, which makes it the first thing worth handing off. How creative team capacity gets consumed walks through the arithmetic.
How does a creative team protect the queue before the cutover starts?
Take the medical device team's spring as the worked example. Four months, one creative team, four request categories, and a migration owning an unknown but large slice of every week. Schedule the two categories that need illustration. Hand the other two out of the team before the cutover: promotional stat cards to whoever owns the social calendar, recap and update videos to the people who own the message. Both run on a locked template the creative team approves once.
Internal comms video is usually the easiest format to move, because the requester is already the subject matter expert and the format repeats every month. Onboarding onto Capsule takes under an hour and comes with a dedicated CSM, the only piece of this that has to happen while the migration is live.
FAQ
What is creative capacity during a system migration?
It is the working hours a creative team has left once a platform cutover is added to their normal request queue. Migration work produces no creative output, so those hours vanish from video and animation with nothing shipping.
Why do video requests stall during a platform migration?
Video has the longest chain of dependent steps in a creative queue. A migration removes hours from every week in small pieces, and small pieces are exactly what a storyboard, build and revision cycle cannot absorb.
Which video work can continue while a creative team is running a migration?
Repetitive, templatable formats: promotional stat cards, recap videos, technology demos, and cut downs from footage that already exists. Each needs an approved template and a requester who knows the subject.
How far ahead should a creative team plan for a migration quarter?
A full quarter, so templates are approved before the cutover starts. The medical device team lead described things being tight until June, long enough that any format dependent on her team simply waits.