I've Been Cheating at Motion Graphics for 20 Years

The test was never which tool touched the pixels. It's who was driving.

I've been cheating at motion graphics for twenty years.

At least, that's what you'd have to call it if you use the logic currently dominating every argument about AI and creative work. Let me explain.

I've done motion graphics professionally for decades — TV shows, movies, client work of every size. And in all that time, here is a partial list of the shortcuts I've used without a single person calling my work fake: templates. Presets. Plugins. Script packs. Stock elements. Expression libraries. Other people's project files, gutted for parts.

Nobody ever looked at a lower third I'd built from a template and said "you didn't really make that." Clients didn't ask which keyframes were mine. The work either served the story or it didn't. That was the whole test.

The new shortcut

This week I've been deep in short-form content for a client — talking-head explainer videos that need motion graphics where B-roll doesn't exist. And the thing quietly working in the background of my week has been AI handling the animation.

Here's the honest description of the division of labor: I'm still having the ideas. The layout, the design, the creative direction — that's me. What the AI does is implement — it animates the thing I designed, dramatically faster than I could keyframe it myself.

Which is to say: it behaves exactly like a template. Or a preset, or a plugin. It's the newest entry in a twenty-year lineage of tools whose entire job is to compress the distance between the idea and the finished thing.

And when you're working for clients, that distance is the business. The longer a project takes to deliver, the lower your effective rate gets — every freelancer runs that math in their head constantly. Shortcuts aren't a moral failing. They're how a one-person shop survives.

Where the argument gets uncomfortable

Now, I can hear the objection, because I've made it myself: a template was designed by a person who got paid. What was the AI trained on?

That's a real difference, and I'm not going to pretend it isn't. The ethics of training data are not solved, and anyone who waves that away is selling you something.

And there's a second honest caveat: the output isn't perfect. There are still slop elements in what it produces — things I don't like, things I wouldn't ship. So I use it sparingly, only when time constraints actually demand it, and everything passes through my hands before a client sees it. That last part is not negotiable, and it's not nostalgia. It's the job.

The line that actually matters

But here's the thing I keep coming back to. For twenty years, the line between "real work" and "cheating" was never about which tool touched the pixels. It was about who had the idea. Whose taste made the calls. Whose eye caught the frame that was wrong.

A template never threatened that, because a template can't want anything. Neither can this.

The danger isn't the shortcut. The danger is handing over the part that was never supposed to be shortcut-able — the ideas, the direction, the taste. That's the line I watch, and it's the line I'd suggest watching in your own work: not "did AI touch this," but "who was driving."

I'm still driving. The tools just got faster. Same as they did in 2005, and 2012, and 2019.

If you've got a shortcut you've used for years that nobody calls cheating — or one you refuse to use — hit reply and tell me. I'm collecting these.

See you next Tuesday.

— Alex

P.S. — If you missed last week's issue about building an entire AI agency and then killing it, [it's here](https://www.creativeeconomist.com/p/i-built-a-fully-automated-ai-agency-then-i-killed-it). This issue is what survived the purge looks like in practice.