Within my first week, someone said "hey, let's do some videos like this," and shared a link.
What loaded was an event recap. Not ours: a sample reel from one of those video "agencies" that cold-blast every company with a marketing address in it. Crowd b-roll. A keynote wide from the back of the room. Lanyards, in slow motion, for some reason. An upbeat royalty-free track landing on a "thank you to our sponsors" card. It was competent the way a form letter is competent: built to be sent to anybody. Swap the logo and you could run it for, I don't know, an Elevator Maintenance Convention. Are those a thing?
It was also 720p.
I said something agreeable and wrote it down. Not a lower standard, exactly. A different one, arrived at for reasons that made sense in a world I hadn't lived in yet.
What, Precisely, Is a Channel
One of my first real projects was a large batch of videos for the channel partner portal.
My first reaction, in full: wtf is a channel?
I've made a lot of video for the channel since. I have a working definition now (something about partners who resell the thing to the customers who buy the thing) and it still sits slightly out of focus, like a word you've said too many times. The videos work. The concept and I remain on polite terms.
I bring it up because that gap turned out to be the actual shape of the job. Ten years in gaming and esports, at Razer, GoodGame, Twitch and Loaded, and I never once had to ask what the thing was. I knew the audience because I was the audience. Now I'm the Director of Digital Content at an AI security company, and the distance between what I know in my hands and what the business needs is a distance I close on purpose, every time, one project at a time.
Nobody to Argue With
Here's the part I didn't see coming.
On a small video team, the fighting is the process. An editor and a producer go three rounds over a cut. The editor is protecting rhythm; the producer is protecting the story beat the rhythm is stepping on. Both are right about something. Neither is being difficult. The cut that survives that argument is better than the one either of them would have made alone. Not as a compromise: because the friction found the actual problem. Friction between crafts isn't the price of collaborating. It's the mechanism.
Embedded in a marketing team, I'm the only person holding the craft side. The argument still happens. I still have opinions about pace, about restraint, about whether a thing needs a voiceover at all. But there's no interlocutor. What I'm arguing with is a calendar, a funnel, and a KPI, and those don't argue back. They don't concede a point and they don't make one. They sit there being correct about their own concerns.
Which they are. It would be easy and dishonest to write this as craft-versus-philistines. Marketing optimizes for pipeline and cadence and things that can be measured, and every one of those is a real thing a real business needs. The calendar isn't wrong to want four videos this month. The funnel isn't wrong to want the CTA legible in the first eight seconds. What's missing isn't intelligence or taste; I work with sharp people. What's missing is a second person whose job is the other half of the argument. Roles, not people. I have to keep reminding myself of that, and it's true every time.
And that's the quiet cost. Alone, you don't lose your standards; you lose your calibration. Standards you can hold by yourself. Calibration takes somebody else in the room.
Every Hat in the Building
The trade came with something substantial, and it should be on the ledger first.
I own the work end to end. Concept, motion design, live webinar production, cinematography, post, sound design, colour. All of it, on the same project, in the same week. Nobody hands me a locked cut, or a brand book and a bounding box. If a video is bad it's mine. If it's good, that's mine too.
I also build tooling now. My JSON-driven After Effects toolkits exist precisely because there was no one to do it the manual way (and they are their own saga). Necessity, not ambition. In a bigger shop that's a ticket in someone else's queue. Here it was a Tuesday, and now it's infrastructure.
I like this. A lot. A version of my career where I sat in a metaphorical cubicle forty hours a week doing motion graphics and only motion graphics would bore me into the ground. And motion is my foundation, the thing I'm best at and would happily be measured on. It just isn't enough on its own to hold me for a decade. I've stopped pretending otherwise.
So: not enterprise over esports. Not esports over enterprise. Two arrangements of the same tradeoffs, and I got real things out of both.
Variety, and the Other Thing
Variety I've never had to learn to want. I've been, by some accident of hiring, absurdly lucky about it. My first real video job was at Razer, with the title Global Community Video Editor. On day two they put a Canon 5D Mark III in my hands and sent me to E3. I shot photo galleries and videos with the community team; we edited, wrote the copy, and posted from the hotel that night. Back at the office I did cheesy VFX: keyboards that sparkled, the planet getting zapped with green Razer lasers. The job was maybe twenty percent "video editor," and I loved every percent of it. Every full-time position since has been some version of the same arrangement: a solid core, and then everything else. That part is easy to say out loud; it's flattering.
The part I'm more reluctant to admit is that I also need structure.
Every job gave me some ratio of the two. On the video teams, structure came free (a schedule, a shoot day, a lead, other people's dependencies pulling me forward) and the variety came with it, built in. Now the ratio is inverted. More range than I've ever had, and not enough scaffolding around it to be as productive as I want to be. Variety without structure is just a wider surface for open loops. Some weeks that produces the best work of my life. Other weeks it's eleven half-finished things and no particular reason to close any one of them first, and the attrition of holding all of them is what tires me out. Not the work. The holding.
Underneath that sits a problem I haven't solved: aligning what I find creatively interesting with what the business finds valuable. Sometimes they land in the same place and the job feels effortless. Sometimes they don't, and the move is to make the useful thing well instead of the interesting thing beautifully. That's a discipline, not a compromise, and I'm not consistently good at it yet. Probably a lesson I'll always be learning.
I miss being on a team. Not the meetings, not the org chart. The other creatives, and having someone to fight alongside about a cut that neither of us can quite let go. I hope the future holds that again.