Giving feedback a writer can actually use

Feedback in a writing group tends to fail in one of two directions. Either everyone is so polite that the notes are useless (“Great post, really enjoyed it!”), or one person decides to be the honest one and leaves a list of everything wrong with the draft. The first teaches the writer nothing. The second teaches them not to share drafts again.

Useful feedback sits between the two. It tells the writer what actually happened when you read their work, points at the specific places where it happened, and leaves them wanting to write the next draft. None of this needs special training. It needs a few habits, and a camp that agrees to practise them.

Ask what the writer wants first

The single most helpful thing a writer can do is say what kind of feedback they are after, and the single most helpful thing a reader can do is listen. A post that is finished and published needs different notes from a rough draft shared for comment.

In a camp, it helps to agree on a few simple labels that writers add at the top of a post or draft:

• Just reading: “This is done. Tell me what stayed with you.”
• Big picture: “Does the structure work? Where did you lose interest?”
• Close reading: “I'm nearly there. Point out sentences that trip you up.”

If a writer asks for “just reading”, do not send them a list of comma splices. If they ask for close reading, do not stop at “loved it”. Matching the request is a form of respect, and it makes the notes far more likely to be used.

Describe what happened to you as a reader

You are not the author's editor or teacher. You are a reader, and your reading is the one thing you know for certain. So report it.

Compare these two notes on the same paragraph:

“This section is too slow.”

“I started skimming around the third paragraph, where you explain the bus timetable. I came back when your sister appears.”

The first is a verdict, and the writer can only agree or argue. The second is information. It tells them exactly where attention dropped and where it came back, and leaves them free to decide what to do about it. Maybe the timetable goes. Maybe the sister arrives sooner. That is their call.

Phrases like “I was confused when…”, “I expected…”, “I wanted more of…” and “I lost track of who was speaking” keep you on firm ground, because they describe your experience rather than ruling on the writer's choices.

Point to the sentence

Vague notes are hard to act on. “The ending felt flat” leaves the writer guessing which part of the ending and why. Quote the line, or name the paragraph, and say what you noticed.

This works for praise as much as criticism. “Your descriptions are vivid” is pleasant to hear and almost impossible to learn from. “The line about the fridge humming through the wall made the whole flat feel real to me” tells the writer what is working, so they can do more of it on purpose.

If you are reading on a screen, it can help to copy the sentence you want to talk about into your reply. It removes any doubt about what you mean.

One big thing, a few small things

A long list of notes, even good ones, is overwhelming. Writers tend to fix the easy items and miss the important one buried in the middle.

Try to organise what you say like this:

1. One big thing. The single change that would most improve the piece, in your view. Lead with it.
2. Two or three small things. Specific lines or moments, quoted.
3. One thing to keep. Something that is working and should survive the next draft.

If you cannot find a big thing, say so. “I don't think this needs structural changes” is useful feedback in itself, and tells the writer they can stop rearranging and start polishing.

Make praise specific and honest

There is a habit of wrapping criticism between two compliments so it goes down more easily. Writers usually see through it, and it teaches them to discount the compliments. Praise is worth more when it is true and when it stands on its own.

Look for what genuinely works: a strong opening, a clear structure, a moment of humour that lands, a detail you would not have thought of. Say what it is and why it worked for you. If the draft is rough, there is still almost always something worth naming, even if it is only the idea behind it.

And do not invent praise you do not mean. A writer who gets honest, specific encouragement from their camp will trust the critical notes when they come.

Say the hard thing kindly

Sometimes the useful note is a difficult one. The argument does not hold together. The piece is about something other than what the writer thinks it is about. A joke could hurt someone.

Say it anyway, because a reader who notices a serious problem and stays quiet is not doing the writer a favour. But say it privately if you can, say it once, and say it about the writing rather than the person. “I don't think the second half supports the claim in the title” is a note about a draft. “You haven't thought this through” is a note about a person, and it will be heard that way.

Then leave the decision with the writer. They may disagree with you, and they are allowed to. Your job was to report your reading honestly, not to win.

If your camp is still working out how to talk to each other in public replies, our piece on keeping a group conversation kind covers the wider conversation. And when you are on the receiving end, the best response to any note is the same: thank the person for reading closely, take a day before deciding what to change, and remember that every reader is one reader, not the verdict of the world.