Stop Leaving Comments and Start Having Conversations: The Case Against Pure Async Feedback

Let me say something that might ruffle a few feathers in the remote-work crowd: the async-everything approach to collaborative writing is overrated. And in some cases, it's actively harmful.

I know, I know. Async is the gospel of distributed teams. "Respect everyone's time zones." "Don't interrupt deep work." "Leave a comment and move on." These are reasonable principles, and for a lot of tasks, they hold up. But when it comes to creative writing, ideation, and the early messy stages of collaborative documents? Pure async feedback can kill an idea before it ever gets a real shot at life.

This is an opinion, and I'm owning it. But hear me out.

The Comment Thread Graveyard

You've seen it. Someone shares a rough draft — maybe it's a new positioning statement, a product announcement, a creative brief — and they're genuinely excited about it. It's not polished, but there's something real in it. An angle. A voice. A spark.

Then the comments start rolling in. Over the next 48 hours, the document fills up with tracked changes and little yellow bubbles. "Unclear." "Can we soften this?" "I don't think this is on-brand." "What does this mean exactly?" Each comment arrives in isolation, stripped of tone, context, and the conversational back-and-forth that might have turned "I don't get this" into "Oh wait, I see what you're going for — what if we tried it this way?"

By the time the writer sits back down to address the feedback, the energy is gone. The draft that felt alive on Tuesday feels like a crime scene by Friday. And the ideas that might have emerged from a real conversation — the unexpected directions, the "yes, and" moments — never happened because nobody was in the room together.

That's the hidden tax of async-only feedback: it's efficient at transmitting criticism, but terrible at generating momentum.

Async Isn't the Problem. Async-for-Everything Is.

To be clear, I'm not arguing that async collaboration is bad. For plenty of writing tasks, it's genuinely the right call. Proofreading, light copy edits, factual corrections, final approvals — all of that works fine in a comment thread. The document is essentially done; the feedback is transactional.

The problem is when teams apply the same async-comment model to work that's still in formation. Early drafts. Brand messaging. Creative concepts. Strategic narratives. These are documents that need energy, dialogue, and a bit of productive friction to reach their potential. Dropping a comment and logging off doesn't create that. It just creates a queue.

There's also a power dynamic buried in async feedback that we don't talk about enough. When feedback arrives as a series of written comments, the loudest or most senior voice tends to dominate — not because their ideas are best, but because they're most comfortable committing strong opinions to text. The more collaborative, exploratory thinking that tends to surface in live conversation gets squeezed out. The comment thread rewards certainty. Real creative collaboration often starts with uncertainty.

What Real-Time Writing Collaboration Actually Unlocks

Think about the best creative session you've ever been part of — a brainstorm, a workshop, a whiteboard session where things actually clicked. What made it work? Almost certainly it was the back-and-forth. Someone threw out a half-baked idea, someone else built on it, a third person redirected it somewhere unexpected, and suddenly you had something none of you would have arrived at alone.

That dynamic is available in collaborative writing too, but only if you create the conditions for it. When two or three people are working in the same document at the same time — watching each other's cursors move, reacting in real time, talking through a paragraph as they write it — the thinking is fundamentally different. It's generative, not corrective. You're building together, not critiquing in sequence.

A copywriting duo at a brand agency in New York described their process this way: "We never send drafts back and forth anymore for the early stuff. We just get on a call, open the doc together, and write. One of us will start a sentence and the other will finish it. It sounds chaotic but it's actually the fastest way we've found to get to something good."

That's not a novel idea — it's basically how good writing partnerships have always worked. The technology has just made it accessible to teams who aren't sitting next to each other.

A Framework for Knowing When to Go Sync

So how do you decide when to gather the team in real time versus letting comments accumulate overnight? Here's a rough guide that works for a lot of teams.

Go synchronous when:

• The document is in its first or second draft and the direction isn't locked yet
• The feedback you need is evaluative or strategic, not just editorial
• Previous rounds of async comments have stalled or created confusion
• The stakes are high enough that misreading tone in a comment could derail the project
• You want to preserve the energy and intent behind the original draft

Stick with async when:

• The document is structurally solid and you need line-level polish
• The feedback required is factual or compliance-based
• Contributors are in wildly different time zones and a live session would require someone to work at 2 a.m.
• The changes needed are straightforward enough that a comment thread won't lose anything in translation

The key is that this should be a deliberate choice, not a default. Too many teams fall into async-only because it feels considerate and low-friction. But friction, in the right amount, is actually what good collaborative writing runs on.

Reclaim the Energy in Your Writing Process

Here's the bottom line: if your team's documents keep coming out flat, over-edited, or somehow less than the sum of their parts, the problem might not be the writing. It might be the feedback process.

Async comments are a tool. A useful one. But they're not a replacement for the kind of live, generative collaboration that turns a decent draft into something your team is actually proud of. The next time you're about to drop a vague comment on a colleague's first draft and log off, consider whether a 20-minute call might do what 20 comments can't.

Some ideas need a room — even a virtual one — to survive.