How to Give Useful Feedback on a Draft
Give useful feedback by separating facts from preferences, naming the reader effect, prioritizing changes, and offering specific evidence.
Read for the agreed purpose
Before commenting, remember what the draft is meant to do and who will read it. A landing page, internal note, lesson, and technical explanation need different standards. Ask whether the draft has a clear purpose, then separate a problem that prevents that purpose from a personal preference about style.
Point to the exact sentence, section, or example. Describe the effect on a reader: the instruction is ambiguous, the evidence arrives too late, the tone sounds more formal than intended, or the next action is difficult to find. Avoid labels such as "bad" or "confusing" without explaining what created the reaction.
Prioritize the changes
Group comments into must-fix issues, useful improvements, and optional polish. Too many equal-priority notes can hide the change that matters most. Offer a possible rewrite when it clarifies the problem, but do not silently replace the author's voice or solve a different problem.
- Start with what already supports the purpose.
- Use questions when you are checking intent.
- Keep style preferences separate from factual errors.
- Agree on which comments need action before editing.
Good feedback makes the next revision easier to make. Ask the writer which kind of review they need before adding comments, and explain which issues are blocking versus optional. It is specific enough to act on and humble enough to leave room for the author's judgment.