Sharing a draft for feedback

Right now, sharing a project in Edits means sending a draft over message for someone to watch and respond to, not opening it for someone else to edit alongside you at the same time. That's a real limitation if you were expecting live collaboration, but it's still useful for the thing most people actually need before publishing: a second pair of eyes catching something you've gone blind to after watching the same clip fifteen times.

Ask a specific question, not "thoughts?"

A vague request gets a vague answer, usually just "looks good." Asking something specific gets you feedback you can actually act on. A few examples worth borrowing directly:

• "Does the hook grab you in the first two seconds, or does it take too long to get going?"
• "Is the pacing too slow anywhere in the middle third?"
• "Can you read the captions without pausing the video?"
• "Is it obvious what I'm asking you to do at the end?"

Share it in the format it'll actually be watched in

Feedback on a video watched full-screen on a phone, sound on, is more useful than feedback on the same video watched in a small preview window on a laptop. If you can, ask whoever's reviewing to watch it the way a real viewer would, not just glance at it while doing something else. A response given while multitasking rarely catches pacing or hook problems, since those only show up when someone's actually paying attention the way your audience would be.

Send it before you think it's finished

Feedback on a rough cut, before captions and color are locked in, is easier to act on than feedback on something you've already polished and are emotionally attached to. Structural problems, pacing, missing context, a hook that doesn't land, are worth catching before you've spent time on the details. Getting notes at this stage also means you're not tempted to defend choices you've already invested hours into.

What draft sharing can and can't do today

What to do until real collaboration lands

Since two people can't currently edit the same project together, splitting responsibilities works better than trying to hand a single project back and forth repeatedly. One reasonable split: one person handles capture and rough cutting, the other reviews and suggests specific, timestamped changes rather than general impressions. It's a workaround, not a real substitute for co-editing, but it keeps a two-person workflow from turning into a bottleneck while you wait for anything closer to real-time collaboration to arrive.

Who to actually ask for feedback

Not everyone gives useful notes, and it's worth being selective rather than sending a draft to whoever happens to be around. Someone who's part of your actual target audience gives you a more honest read on whether a hook or a pace works than a friend who's inclined to just say something encouraging. If you can, mix the two: one person who'll be genuinely critical about pacing and clarity, and one who represents the kind of viewer the video is actually made for.

Handling feedback you disagree with

Not every note needs to be acted on, and it's fine to keep a choice you made deliberately even after someone questions it. What's worth doing is understanding why they reacted that way, since even feedback you ultimately reject often points at something real, a moment that reads differently than you intended, even if the specific fix suggested isn't the one you end up using.