How to Give Constructive Feedback That Writers Actually Use

You have spent forty minutes on someone's chapter. You have flagged the wobbling timeline, queried the ending and marked three adverbs. The revised draft comes back unchanged. The writer thanked you warmly and moved every sentence exactly nowhere.

That is not stubbornness. Most feedback fails at the same point: it tells a writer what you think of their work instead of giving them something to do with it. The strengths-questions-suggestions framework changes that, and it takes about as long as your current method.

Lead with strengths — and make them earn their place

"I really enjoyed this" is kind, but a writer cannot repeat a compliment they cannot decode. Specific praise does two jobs at once. It tells them what to protect in revision, and it proves you read closely, which makes the harder notes easier to hear.

Compare these:

• "Great voice." — pleasant, forgettable, unusable.
• "The narrator's habit of correcting herself mid-sentence — 'I was fine, mostly fine' — is the strongest thing on the page. If that's the novel's register, I'd trust it." — the writer now knows what to defend.

Keep it to two or three points. If you list ten things you liked, the two things you didn't will feel like a trap. And pick strengths that genuinely apply to this piece: if the atmosphere is superb but the plot is thin, don't praise the plot out of politeness. Writers spot filler praise quickly, and it makes them discount the rest of your note.

Questions do the heavy lifting

A good question hands the fix back to the writer, where the authority belongs. It also protects you when you are not certain whether something is deliberate.

Useful shapes:

• "I lost track of who was speaking in the third paragraph. Was that deliberate?"
• "The chapter ends on the image of the closed door. What do you want the reader to feel in that last line?"
• "We spend three pages on the journey and half a page on the arrival. Is the arrival the part you're least sure about?"

These are real questions, not rhetorical ones. "Did you not notice the tense shifts?" is an accusation wearing a question mark, and everyone can tell the difference. Ask no more than three. If you have fifteen, pick the ones that would change the draft most.

Suggestions: offer routes, not orders

Name the experience, then the experiment

"The middle sags between the argument and the reunion" is a diagnosis. "I'd try cutting from 'She left the keys on the counter' straight to the reunion and see whether the gap holds" is an action. Both belong, but only the second is something the writer can use tonight.

Give two options, not one

Two routes turn a correction into a choice. Writers often take a third route you had not considered, which is exactly what you want.

Mark your confidence

Say whether something is a firm note, a hunch or one reader's reaction. A line you feel strongly about and a line you are merely wondering about should not sound identical, or the writer will either over-correct or ignore you entirely.

Don't rewrite the prose

Offer an example phrase if it clarifies the note, then stop. If you redraft the whole passage, the writer's next job is editing your voice back out of their work, which wastes everyone's evening.

All three parts together

Say a writer shares a 900-word opening about a woman waiting for a bus that never arrives.

Before: "Nice atmosphere but it drags. The bus thing is confusing and I don't know why she's there. Maybe start later."

Now the same note, restructured:

• Strength: "The waiting is genuinely tense. The detail about counting the buses that do come past is doing a lot of quiet work."
• Question: "I couldn't tell whether she knows the bus isn't coming. If she does, what is she actually waiting for?"
• Suggestion: "One route: start on the third bus and keep the earlier paragraphs in reserve. Another: keep them, but give us one concrete reason she stays."

Roughly the same number of words. Three decisions instead of a verdict, and not one of them asks the writer to become somebody else.

Etiquette that keeps a group working

Workshops and online critique groups live or die on tone. A few habits worth keeping:

1. Read the whole piece before writing a single note. Half of what bothers you on page one is answered on page four.
2. Ask what kind of feedback the writer wants. Line edits and structural notes are different jobs, and doing the wrong one is exhausting for both of you.
3. Comment on the draft in front of you, not the draft you would have written.
4. Keep notes about choices separate from typos. Save proofreading for last so it cannot crowd out the bigger conversation.
5. If you are the only person who noticed something, say so. "This might just be me" is honest, and often the most useful line in the thread.
6. Debate the writing, not the writer.
7. Stay inside the agreed time. A two-minute spoken note in a workshop beats a fifteen-minute monologue every time.

A five-minute check before you send

Read your feedback once and ask:

• Would a stranger know exactly which sentence or scene I mean?
• Have I given the writer at least one thing to keep?
• Have I asked at least one honest question?
• Is every suggestion phrased as something to try rather than something they got wrong?
• Could I cut a third of this without losing anything useful? Usually, yes.

Then send it. Critique works best when the writer can close your note and immediately open their draft with a plan. Strengths tell them what to protect, questions tell them what to think about, and suggestions give them somewhere to start. Three parts, ten minutes of care, and a much better chance that the next version of that chapter comes back changed for the better.

Photo: rawpixel / Pixabay