Source: Interview with Tommy Lee, lead editor for Sidemen, on the Clipflow YouTube channel.

Tommy Lee described Sidemen's recent hide-and-seek video as "maybe one of the most crazy syncs I've ever made." The scale was beyond what most content teams ever encounter. But the lessons apply to any operation where multiple people need to contribute to the same output.

"We had five editors working on the same timeline. I was project managing more than I was editing. At one point, just getting everybody in the right place, answering all the questions, getting all the technical problems solved."

This is the inflection point that few people talk about. When a project exceeds what one person can handle, the lead doesn't become a better editor. They become a different kind of role entirely.

The Shift From Editor to Conductor

Most editors build their careers around being the best at cutting. The dopamine comes from the creative decisions, the pacing, the moments that land. Managing other people's work feels like a step backward.

But scale demands it.

"I really enjoy being more of a managerial oversight person within the team, as long as I can always also output my creative spirit."

Tommy found a balance. He's not giving up editing. He's adding orchestration on top. The key is recognizing that past a certain project size, the most valuable thing the lead can do isn't cut footage. It's make sure everyone else can cut footage effectively.

"I'm quite comfortable leading and thinking about processes for the entire team. It's quite unique. I've only been here for 7 months and I've already taken on quite a leadership role."

Inventing Workflows on the Fly

The hide-and-seek project didn't come with a playbook. 108 cameras and 7 hours of footage isn't a standard workflow anyone teaches.

"We experimented on the go with workflows that we didn't really know would work or not. Had to try and invent new technical ways of syncing everything and putting it all together."

This is where experience matters more than credentials. Tommy's 8 years of prior work gave him the judgment to make decisions quickly when the normal process wouldn't scale.

But it also required comfort with uncertainty. The team shipped a massive video using workflows they invented during production. No testing period. No pilot project. Just figure it out while the deadline approaches.

This only works if the lead is willing to make calls without complete information, and if the team trusts those calls enough to execute on them.

The Knowledge Hub Problem

When multiple editors work on the same project, questions multiply. What's the naming convention? How do we handle this sync issue? Is this cut approved or still pending? Where's the updated asset?

Someone has to be the central source of answers.

"Getting everybody in the right place, answering all the questions, getting all the technical problems solved. It was a big, big ask."

This is invisible work. It doesn't show up in the final timeline. But if no one does it, the project fragments into inconsistent pieces that don't fit together.

The lead becomes the knowledge hub. Every question routes through them. Every decision gets documented or at least communicated. The tax on their own productivity is significant, but the alternative is chaos.

Knowing When to Edit vs. When to Orchestrate

Tommy's comfort with the shift came from confidence in his own skills.

"I feel very well equipped with all the skills in my editing toolbox that I don't really need to think about certain choices I'm making anymore. I just know intuitively this is how I could do it."

Because the editing part is automatic, he has mental bandwidth available for the orchestration part. He's not choosing between being a good editor and being a good manager. The editing runs on developed instincts, freeing attention for the coordination layer.

This suggests a developmental path. Before you can lead multiple editors effectively, you need your own skills to be solid enough that they don't require conscious effort. Otherwise you're splitting attention between two demanding tasks, and both suffer.

Building Support Systems

Tommy's approach to leadership wasn't about hierarchy.

"I'm not trying to make it feel like I'm the boss of everybody. I'm just trying to figure out ways that I can help people along and teach them what they want to do. Hopefully be a support for anybody that has any questions."

This framing matters. The conductor isn't above the orchestra. They're in service of the orchestra. The role exists to make everyone else more effective, not to accumulate authority.

"If a young editor comes to me with a problem and I give him a solution and his eyes are wide open, he's like, 'Ah, this is great.' I'm like, 'Yes, let's go.'"

The satisfaction comes from enabling other people's work, not from doing all the work yourself.

What This Means for Scaling Your Team

At some point, your projects will exceed individual capacity. When that happens, someone needs to shift from doing the work to coordinating the work.

Recognize the inflection point. If projects are slipping because no one has bandwidth, the answer isn't more hours. It's more people, which means someone needs to orchestrate.

The lead's job changes. They're not the best editor on the project. They're the person who makes sure all the editors can work effectively.

Questions need a home. Designate someone as the knowledge hub. Document decisions. Create channels for quick clarification. The coordination overhead is real, but it's cheaper than fixing inconsistent output.

Trust is required. Multiple editors on one timeline only works if everyone trusts the lead's judgment and the lead trusts everyone's execution. Without trust, you get micromanagement or fragmentation.

The teams that scale past individual capacity are the ones that figure out orchestration. The teams that don't stay stuck at whatever one person can handle, no matter how talented that person is.