Feedback on writing is one of the more complicated things a writer has to manage — not because it is difficult to receive criticism, though it can be, but because not all feedback is equally useful and acting on the wrong feedback can make a piece worse rather than better. The writer who treats all feedback as equally valid, and revises accordingly, tends to produce a piece that pleases no one and reflects nothing.
The useful skill is not the ability to receive feedback without defensiveness — though that is worth developing — but the ability to evaluate it: to distinguish feedback that identifies a real problem from feedback that identifies a preference, and to know which to act on and which to set aside.
What Feedback Actually Is
Feedback on writing comes in several forms, and they are not equally useful.
The most useful feedback is the response that identifies a problem without prescribing a solution. “I lost the thread here” is more useful than “you should restructure this section”, because it tells the writer where the piece is failing without deciding how to fix it. The writer knows the piece better than the reader and is better placed to find the right solution once the problem is identified.
The least useful feedback on writing is the feedback that is actually a preference. “I would have written this differently” or “I prefer shorter sentences” or “this doesn’t feel like your usual style” — these are not reports of a problem in the piece. They are descriptions of what the reader would do, which is irrelevant unless the reader is the intended audience and the preference is widely shared. A writer who revises to satisfy preferences rather than to fix problems is not improving the piece — they are accommodating the reader.
Between these two is the feedback that identifies a problem but diagnoses it incorrectly. The reader who says “this section is too long” may be right that something is wrong — the reader’s attention wandered — but wrong about the cause. The section may be too long, or it may be that the problem is elsewhere and is making the section feel longer than it is. This feedback requires evaluation rather than either acceptance or dismissal.
How I Evaluate Feedback
When I receive feedback on a piece, the first thing I do is set it aside. Not permanently — but long enough for the immediate reaction to settle. The immediate reaction to feedback is rarely the useful one, whether it is defensive or enthusiastic. Distance produces a more accurate assessment.
When I return to the feedback, I ask three questions. First: does this identify a real problem, or a preference? If a preference, I note it and move on. Preferences are interesting data — they tell me something about how this reader experiences the piece — but they are not instructions.
Second: if it identifies a real problem, is the diagnosis correct? The reader who says “I don’t understand what you’re arguing here” has identified a real problem — a failure of clarity. But the argument may be clear and the problem may be elsewhere: in the structure that led to this point, or in an unexplained assumption earlier in the piece. I look at what the feedback is actually pointing to rather than what it says.
Third: is this feedback consistent with what the piece is trying to do? Some feedback identifies a problem that would exist in a different piece but not in this one. A piece that is deliberately dense, or deliberately slow, or deliberately resistant to easy summary will receive feedback that asks for it to be less dense, less slow, more easily summarised. This feedback is not wrong — it accurately describes the reader’s experience — but acting on it would change the piece into something it is not trying to be.
What to Do With Feedback You Disagree With
The feedback on writing you disagree with is the most interesting and the most dangerous. It is the most interesting because the disagreement is sometimes a signal that the feedback has identified something the writer is too close to see. It is the most dangerous because the writer who dismisses all uncomfortable feedback as wrong tends to produce writing that no one has been allowed to improve.
The useful approach is to hold the disagreement and return to the piece. Does the piece, read fresh, have the problem the feedback identified? Sometimes yes, the feedback was right and the initial resistance was defensive. Sometimes no, the piece does what it is trying to do, and the reader’s experience, while real, is not a problem the piece needs to solve.
The distinction is between feedback that identifies a failure of execution — the piece not doing what it is trying to do — and feedback that identifies a difference in values — the reader wanting a different piece from the one the writer made. The first kind should be acted on. The second kind is information but not instruction.
Feedback on writing is most useful when it is treated as data rather than as direction. The writer who receives feedback as direction tends either to over-revise — changing the piece in response to every comment — or to under-revise — defending the piece against every comment. The writer who receives it as data evaluates each piece of feedback on its merits and revises only what the evaluation justifies.
The piece is yours. The feedback is theirs. The revision is the point where the two meet — and the writer decides what to take from that meeting.
