You can learn a lot about a writing group from the thirty seconds after someone finishes reading. Feedback is a craft in its own right, and most of the harm done in workshops is accidental: a compliment so vague it means nothing, a true observation delivered like a verdict, twenty minutes spent on commas while the real problem sits three scenes away. None of it comes from cruelty. It comes from habit. Here are the habits worth breaking.

Saying "I loved it" and moving on

Vague praise feels generous and costs nothing. It also leaves the writer with nothing. "I loved it" might mean the voice, the ending, the fact that you finished it at all — the writer can't tell, so they can't protect whatever worked. Worse, they can't repeat it. A story that lands once by accident is a story the writer will spend months failing to land again.

Be specific about the cause, not just the effect. Not "the ending was powerful" but "the last line landed because you'd spent two pages making that kitchen feel safe." Name the moment, name what it did to you, and name why. Even a rough why is better than none.

Specificity also protects you from the opposite failure, which is praising everything. If every draft gets the same warm nod, your nod stops carrying information. A reader who says "the dialogue in the car scene is the best thing here, and I'd cut the dream sequence" is worth ten readers who liked it.

Praise the risk as well as the polish. A writer who tries something strange and half-succeeds needs to know the attempt registered: "I wasn't sure the second-person sections would hold, and by the third one I was in." That sentence tells them the experiment has a future, even if this draft doesn't quite find it yet.

Honesty without a blunt instrument

Writers are often told to be tough and say what they really think. But honesty and a verdict are different things. One is a reader's report; the other is a sentence handed down.

Compare these two responses to the same story:

This didn't work for me — I lost the thread when the timeline jumped and never quite found my footing again.

And then: "The structure is a mess." The first shows the writer where you were and what happened to you. The second just leaves a mark.

Two habits make this worse. The first is absolutes: "the reader will be confused here", "no one will care about this character". You are one reader. Speak as one. "I stopped caring when she left the flat" is both fairer and more useful. The second is the pile-on — twelve problems in a row, delivered at speed, with no sense of proportion. Say which two matter most. A workshop that sends a writer away knowing exactly what to fix next beats one that sends them away knowing everything that's wrong.

And skip the praise sandwich. Writers can taste it, and it teaches them to distrust your compliments.

Turning the workshop into a proofread

Typos are easy to spot, easy to say out loud, and easy to feel useful about. They are also the least valuable feedback a draft can receive. Ten minutes on comma splices is ten minutes not spent asking whether a character's decision in scene three is believable.

If you're workshopping early drafts, proofreading is mostly noise. If the writer has asked for line notes, or the slips form a pattern, mention it once and move on.

A rough order of operations, largest to smallest

1. Shape and structure: does the piece hold together, and does it end where it should?
2. Character and stakes: do we know what people want, and what it costs them?
3. Voice and point of view: who is telling this, and are they the right one to tell it?
4. Scene-level work: does each scene turn, or do some of them just sit there?
5. Sentences: rhythm, clarity, repetition — the line-by-line texture of the prose.
6. Mechanics: typos, punctuation, consistency. Last, and only if asked.

The order matters because problems near the top can make everything below them irrelevant. Polishing the sentences in a scene that gets cut is wasted effort, and it's the kind of wasted effort that feels productive, which is why workshops fall into it so easily. Work your way down. Stop where the draft stops.

Arguing with the story instead of reading it

There's a particular kind of feedback that sounds rigorous and is actually a refusal to engage: the note that tells the writer what you would have done. "I'd have had her tell him the truth at dinner." Maybe. But that isn't a reading of the draft; it's a draft of your own, and you're handing it to the wrong person.

You can usually spot it by the grammar. Notes that begin "you should have" are almost always about the reader's preferences. Notes that begin "I didn't understand why" or "I stopped believing in" are about the page.

This doesn't mean you can't offer suggestions. It means the suggestion should follow the diagnosis rather than replace it. "I lost track of why she'd lie here — she's been so careful up to now. If you want the lie, I need one more beat showing me what she's afraid of." Now the writer has a problem and a possible solution, and can take one without the other.

Saying back what you heard

Before you judge a draft, prove you read it. "Here's what I understood happened" is the single most useful sentence in a workshop, and the most frequently skipped. If your summary of the story doesn't match the one on the page, you've just found the writer's biggest problem without having to argue about it.

Be honest about the confusions. Say where you got lost, not that the piece is confusing. "I thought the brother was dead until page four" is a gift. "The chronology is unclear" is a shrug.

Then say what the piece seemed to be about — the question it kept circling, the emotional argument underneath the plot. Sometimes a writer will discover that the story they thought they were telling is only visible at the edges of the one on the page. That's the note that changes a draft.

None of this requires you to be softer, or tougher, or better read. It requires you to be useful: to say what happened to you as a reader, to say it once, and to leave the writer with a next step instead of a verdict. The writers who last aren't the ones who got the kindest feedback. They're the ones who got the clearest.

Photo: 1857643 / Pixabay