Why Most Writing Feedback Doesn't Work
If you've ever received feedback on your writing that made things worse instead of better, you know the problem isn't a lack of opinions. Everyone has opinions. The problem is that most feedback is either too vague to act on, too prescriptive to be useful, or too focused on the reader's preferences instead of the writer's intent.
This guide is for the person giving feedback -- the beta reader, the critique partner, the writing group member who wants to help but isn't always sure how. Giving good feedback is a skill. It can be learned. And the writer in your life will thank you for learning it.
The Cardinal Rule: Diagnose, Don't Prescribe
The single most important principle of writing feedback is this: your job is to identify the problem, not to write the solution.
When a doctor tells you "your knee hurts because the cartilage is worn," that's useful. If the doctor grabbed a scalpel and started operating without explaining anything, you'd run. The same principle applies to writing feedback. Tell the writer where the problem is and what kind of problem it is. Don't rewrite their sentences.
Prescriptive feedback: "You should change 'She walked into the room and sat down' to 'She entered, dropping into the chair like a sack of flour.'"
Diagnostic feedback: "This moment where she enters the room feels flat. Given what just happened in the previous scene, I expected to feel her emotional state in how she moves. Right now it reads like a stage direction."
The prescriptive version imposes your style on the writer's work. The diagnostic version tells the writer what isn't working and why, then trusts them to fix it in their own voice. The writer might come up with a solution you never would have imagined -- and that solution will sound like them, not like you.
How to Read Before You Comment
Read It Once Without a Pen
The first read should be as a reader, not as a critic. Let yourself experience the story. Notice where you're engaged and where your attention wanders. Notice where you feel something and where you feel nothing. These gut reactions are your most valuable data, and you can only access them on the first read.
Don't stop to write comments. Don't fix typos. Just read. Your emotional response to the story as a whole is the foundation for everything else.
Read It Again With Notes
The second read is where you work. Now you're analyzing why you reacted the way you did. The scene that felt slow on first read -- what specifically makes it drag? The character moment that felt false -- what's the gap between what the author intended and what you experienced?
This two-pass approach prevents a common trap: confusing your craft observations with your reader experience. A paragraph can be technically well-written and still not work in context. A technically rough passage can be emotionally perfect. Read as a reader first, analyze as a critic second.
What to Comment On
Your Reader Experience
The most valuable feedback you can give is a clear account of what you experienced as a reader. Not what's "right" or "wrong" -- what you actually felt, thought, and understood while reading.
- "I was confused here." Tell the writer where you lost the thread. Don't try to figure out what they meant -- just mark where your understanding broke down.
- "I got bored in this section." Be honest. If you skimmed, say so. If your attention wandered, say where it started wandering. This is the most helpful feedback a writer can receive, even though it's uncomfortable to give.
- "I didn't believe this." When a character's action, a plot development, or a piece of dialogue felt false, name it. Say what felt off without necessarily knowing why.
- "I expected X, and you gave me Y." Subverted expectations can be brilliant or frustrating. Let the writer know which one you experienced.
- "I felt [emotion] here." When the writing works, say so. Writers need to know what's landing, not just what isn't.
Patterns You Notice
Individual issues can be flukes. Patterns are useful feedback.
- "I notice you tend to tell emotions rather than show them, especially in the early chapters." (For concrete examples of this distinction, see our show don't tell examples guide.)
- "The dialogue scenes are your strongest writing. The description-heavy scenes feel like they're written by a different person."
- "Every scene with Marcus feels vivid and specific. The scenes with only Elena feel more generic."
- "You frequently start scenes with weather or setting description. By chapter 10, I was skipping the opening paragraphs."
Patterns help writers see habits they can't see themselves. A single comment about a single adverb is nitpicking. Noting that the writer uses adverbs as an emotional crutch throughout the manuscript is developmental feedback.
Questions Rather Than Statements
When you're not sure whether something is a problem or an intentional choice, ask rather than declare:
- "Is it intentional that we don't know Marcus's motivation until chapter 12? I found it frustrating, but if the mystery is the point, that might be working as designed."
- "The timeline skip between chapters 7 and 8 confused me. Was this supposed to be disorienting, or did I miss a transition?"
- "I read this scene as comedic, but I'm not sure that was your intent. Is the tone intentional?"
Questions respect the writer's agency. They say "I experienced this, and I want to understand whether that's what you wanted" rather than "you did this wrong."
What Not to Do
Don't Rewrite Their Sentences
This is the most common mistake, especially among critique partners who are also writers. Resist the urge to show how you would have written it. The writer isn't asking you to write their book. They're asking you to help them write theirs. When you rewrite a sentence, you're replacing their voice with yours. It doesn't matter if your version is "better" by some objective standard -- it's not their version.
Don't Focus on What You'd Do Differently
"I would have made Marcus a woman" or "I would have set this in space" is not feedback. It's a different book. Evaluate the book the writer is trying to write, not the book you wish they were writing.
Don't Make It About Taste
"I don't like present tense" or "I prefer third person" is your preference, not their problem. Unless the writer specifically asked "which tense should I use," your genre and style preferences aren't relevant. Focus on whether the choices they've made are executed well, not whether you'd have made the same choices.
Don't Sandwich Criticism in False Praise
The "compliment sandwich" -- say something nice, deliver the criticism, say something nice again -- is transparent and condescending. Adults can handle direct feedback. If something isn't working, say so clearly and respectfully. If something is working, say that too, with equal specificity and sincerity. But don't manufacture praise to make criticism palatable. The writer can tell the difference.
Don't Comment on Everything
A manuscript returned with comments on every page is overwhelming, not helpful. Prioritize the big issues. If the plot structure has problems, focus on that rather than line-level prose. A writer can't process 200 comments; they can process 20 meaningful ones.
Structuring Your Feedback
Start With the Big Picture
Before any scene-level or line-level notes, give an overall response:
- What's the story about (in your understanding)?
- What worked best?
- What's the biggest issue holding the manuscript back?
- How did you feel when you finished reading?
This orients the writer before they dive into specific notes. It also tells them whether you understood their intent -- if your summary of the story doesn't match what they thought they wrote, that's the most important feedback of all.
Organize by Priority
Group your feedback from most to least important. Structural issues before scene issues. Scene issues before line issues. This helps the writer focus their revision energy where it matters most.
Be Specific About Location
Vague feedback is unhelpful feedback. "The pacing is off" is less useful than "Chapters 7-9 feel slow -- the subplot with Elena's mother doesn't seem to connect to the main plot, and I think that's what's dragging." Specificity lets the writer go directly to the problem.
Name What Works, Not Just What Doesn't
Positive feedback isn't just encouragement -- it's navigation. When you tell a writer that chapter 4 is the strongest chapter, that their dialogue is excellent, or that a particular image was unforgettable, you're telling them what to lean into. Writers often don't know what their strengths are. Telling them is genuinely useful.
Special Situations
When the Writer Is a Beginner
Focus on the biggest issues and ignore the small ones. A beginning writer who receives 50 corrections will be discouraged. A beginning writer who receives 3 clear, actionable observations will improve. Meet them where they are, not where you want them to be.
When You Don't Like the Genre
Be upfront about it. "I don't usually read romance, so take my feedback on genre conventions with a grain of salt. But here's what I noticed as a general reader..." This frames your feedback appropriately and prevents you from flagging genre conventions as problems.
When the Writing Is Very Good
Don't invent problems. If the manuscript is strong, say so. Focus your feedback on the few things that could make it better rather than finding flaws to justify your role as a critic. "I only have three notes, and they're all minor" is a perfectly valid response.
Making Feedback Easier to Give
The logistics of giving feedback matter. Tools that let you leave comments attached to specific text passages are better than a separate document of notes. Voice-recorded feedback -- like Fable's suggestion system, where viewers select text and record their thoughts -- can capture nuance that's hard to type. Hearing someone say "this part confused me" with their actual tone of voice conveys something that a written comment doesn't.
Whatever method you use, make it easy for the writer to connect your feedback to the specific text you're reacting to. The more friction between your observation and the relevant passage, the more likely your feedback is to be misunderstood or ignored. For a broader look at platforms built for this kind of exchange, see our roundup of the best collaboration tools for writers and editors.
The Goal
Good feedback helps the writer see their manuscript the way a reader does. Not the way you do specifically, but the way a fresh pair of eyes encounters the story for the first time. Your job isn't to fix the book. Your job is to give the writer information they can't get on their own -- what it's like to read their work. What they do with that information is up to them. If you are on the receiving end of feedback, our companion piece on how to get useful beta reader feedback covers how to structure the process from the writer's side.