Knowledge Base/Creative Strategy/Collaborating with Video Editors: How to Get the Edit You Actually Need
Creative StrategyProcess

Collaborating with Video Editors: How to Get the Edit You Actually Need

The gap between what marketers ask for and what editors need to hear. How to brief editors, give feedback, and build relationships that produce better video.

By Wreltik Research Team

Collaborating with Video Editors: How to Get the Edit You Actually Need

The relationship between marketer and editor is where most video gets better or worse. A good editor given clear direction produces work that exceeds what was asked for. A good editor given vague or contradictory direction produces work that satisfies no one. Here's how to be the marketer editors want to work with — which is also the marketer who gets the best work.

Brief the outcome, not the technique

Don't tell the editor how to edit. Tell them what the edit needs to achieve.

  • Bad: "Add a jump cut here and a crossfade here."
  • Good: "This section needs to feel faster — the pacing is dragging and we're going to lose people. Can you tighten it?"

The first assumes you know editing better than the editor. The second respects their expertise while being specific about the problem. The editor might solve it with jump cuts, or with something you wouldn't have thought of that works better.

Reference specifically, not generally

Don't say "make it feel like a Nike ad." That's too vague — the editor doesn't know which Nike ad you're thinking of, or what aspect of it you want to capture. Say "the pacing in the first 15 seconds of this specific ad [link] — the way it cuts on action rather than words. Something like that rhythm."

A single specific reference is worth more than five general references. The editor can study it, understand what you're responding to, and apply that understanding to your project.

Feedback in rounds, not streams

The worst workflow: the marketer sends feedback as they think of it, in a stream of messages across multiple days. The editor implements piecemeal, loses the thread, and the edit becomes a patchwork of individual notes rather than a coherent whole.

Better: watch the edit. Write all your feedback. Organize it into one message, organized by priority (what must change vs. what would be nice to change). Send it once. Let the editor implement it as a complete round before sending the next set of notes.

Trust the editor's pushback

If an editor pushes back on a change — "this will make the pacing worse" or "this cut won't work because of [technical reason]" — listen. They're not being difficult. They're doing their job, which includes protecting the edit from changes that will make it worse.

The best editor relationships are collaborative, not transactional. The editor brings creative and technical judgment that complements your strategic judgment. When both are respected, both contribute to a better final product.