I'm a creative operations director. Not a title I picked because it sounds impressive, it's the actual job: I take creative work that needs to ship reliably, at a real quality bar, across a team bigger than one person can hand-hold, and I build the system that makes that possible instead of hoping it happens.

The part I'm actually good at starts before anyone's touched a single asset. Most creative problems aren't solved by working harder on the obvious brief, they're solved by reading the actual situation, the category nobody's questioned, the catalogue nobody's looked at twice, the process everyone's just tolerating, and finding the read that changes what's worth building. That's the instinct behind every strong creative call I've made, and it's the same instinct I bring to evaluating a new tool or a stalled process.

Leading a team means the system has to survive contact with reality, not just look good on paper. I write SOPs people actually follow and build QA gates that catch problems before a client does. I manage performance against a real, stated bar, and when someone tries to route around that bar, I act, including making the hard call to let someone go when the alternative is letting errors reach a client. I've grown teams past 30 people directly and helped scale a spin-off venture to roughly 300. None of that is theoretical.

Right now, that same discipline is pointed at AI. I don't chase whatever model has the best demo reel. I evaluate tools on whether they hold up in real production: whether a video model takes multiple reference images instead of just a start and end frame, or whether it generates native audio instead of needing a bolted-on post pass, the kind of detail that decides whether a pipeline scales or falls apart. I've built AI production pipelines from brief to delivery, and I've stood up an agent system running actual content operations, not a proof of concept sitting in a sandbox.