Why feedback is hard
Writing feels personal, even when it is a product description or a how-to page. Comments on a draft can feel like comments on the writer. Meanwhile, the person giving feedback often worries about sounding harsh, so they either soften comments until they are useless or write them so bluntly that they sting. A little structure helps both sides.
The core idea is that feedback should be about the writing, aimed at a goal both people share: a piece that works for its readers.
Before any comments: agree on what kind of feedback
The most common feedback failure is a mismatch. A writer wants to know whether the structure works, and the reviewer returns a list of comma corrections. Or the writer wants a final proofread, and the reviewer proposes rewriting the whole argument.
Before the review starts, say which level of editing is wanted:
- Big picture: purpose, order, gaps, focus.
- Line level: wording, clarity, tone, flow.
- Proofreading: typos, punctuation, formatting.
Also say what is fixed. If the topic, length or deadline cannot change, say so, so that reviewers do not spend effort on things that cannot be acted on. Having a written creative brief or style guide gives reviewers a shared standard to measure against.
Giving feedback
Be specific
“This section is confusing” tells the writer something is wrong but not what to do. Compare: “I got lost in the third paragraph because the term ‘bounce’ is used before it’s explained.” The second comment identifies where the problem is, what caused it and how it felt to the reader.
Point to particular sentences or paragraphs, and, where you can, say what effect the problem had on you as a reader.
Describe the reader’s experience
Phrasing comments as your own reaction, not as a judgment, makes them easier to hear and often more accurate: “I wasn’t sure who this section was for” works better than “This section is unfocused.” You can only truthfully report what happened to you, and the writer can decide whether other readers would react the same way.
Explain why, and offer options
A comment is more useful when it includes a reason: “The second example repeats the first, so it might be cut.” If you have an idea for a fix, offer it as a suggestion, not an order: “One option is to move the definition up before the first use.” The writer knows the goals and constraints better than you do and may find a better fix.
Include what works
Positive comments are not just politeness. They tell the writer what to keep. A note like “The opening example made the problem clear right away” is information. Be honest, though; praise that is not meant undermines trust. If you find little to praise, focus on specifics you do see.
Prioritize
A page covered in markings overwhelms the writer. Group comments by importance: the two or three issues that matter most, then smaller points. For a rough draft, it is usually better to leave sentence-level fixes alone until the larger problems are settled.
Ask questions
Questions invite the writer to think: “What do you want the reader to do after this paragraph?” can open up a better solution than a directive. It also acknowledges that you may be misreading the intent.
Watch your tone
Avoid sarcasm, absolutes (“always,” “never”) and personal comments. Say “this paragraph is long,” not “you ramble.” In written comments, where tone is easily misread, a little warmth goes a long way.
Receiving feedback
Pause before reacting
Your first reaction to criticism may be to explain or defend. Notice it, and hold off on replying. Read all the comments once without responding, and come back after a break. Feedback often looks more reasonable the second time.
Listen for the problem, not only the fix
Reviewers are better at spotting that something is wrong than at diagnosing why or proposing the cure. If someone says “this part is boring,” their suggested rewrite may not be what you need, but the signal that attention drops there is valuable. Ask yourself what problem is behind each comment.
Ask for clarification
If a comment is unclear, ask a neutral question: “Can you show me where you got lost?” Avoid arguing about whether the reader should have understood. If one reader misunderstood, others might too.
Look for patterns
One reader’s preference may be just that. If several people stumble in the same place, it is a real issue. When comments conflict, return to the piece’s purpose and audience to decide. Information from your readers, such as reader questions or survey answers, can help you judge which comments reflect actual audience needs.
You decide
Receiving feedback does not mean accepting all of it. You are allowed to disagree. But it is wise to have a reason: “I considered that and kept it because the brief calls for a formal tone” is a stronger position than “I just like it that way.” Thank the reviewer either way, since they spent time on your work.
Keep a record
Note recurring comments over several pieces. If three different editors flag your long openings, that is useful information about your habits. Over time this turns feedback into a personal checklist, a bit like learning from creative critique in any creative field.
Building a good process
- Agree on the review level and deadline in advance.
- Give reviewers a clear question to answer.
- Keep comments tied to the text, not to the person.
- Review the draft at the right stage; early feedback on structure is cheaper to act on than late feedback.
- Close the loop: tell reviewers what you changed.
Both roles take practice, and the exchange becomes one of the fastest ways to improve.