Feedback only helps if you know how to ask for it, who to ask, and what to do when it contradicts itself.
Start Writing Better →These three feedback roles are often confused, and using the wrong one at the wrong stage wastes time and produces misleading information. Beta readers are audience members: ideally, they are representative of the readers who will buy your finished book. They read as readers, not as writers, and their feedback tells you how the story lands emotionally and experientially. Critique partners are fellow writers who bring craft knowledge to your work: they can identify structural problems, diagnose pacing issues, and explain why a scene isn't working rather than merely reporting that it isn't. Editors are professionals paid to improve your manuscript: developmental editors work at the story level, copy editors at the sentence and consistency level, and proofreaders catch errors that survive everything else. Use all three, at the right time, in the right order.
The questions you ask your beta readers determine the quality of the feedback you receive. Useful questions produce specific, actionable data. Useless questions produce reassurance. Ask: at what point did you consider stopping? Which character did you care most about and why? Was there any moment where you lost track of what was at stake? Did the ending feel earned? What did you expect to happen that didn't? Do not ask: was the writing good? Did you like it? Would you recommend it? These questions produce answers calibrated to your feelings, not your craft. A kind beta reader will tell you they liked it. What you need to know is where they looked at the clock. The reader's experience is the only data that matters. Ask questions designed to surface experience, not opinion.
The two most common failure modes when receiving feedback are defending the work (explaining why the reader is wrong) and dismissing the work (agreeing with everything to end the discomfort). Both prevent you from hearing what the feedback is actually saying. When a reader flags a problem, resist the impulse to explain your intention. Your intention is irrelevant. What matters is what the reader experienced. If five readers find your protagonist unlikeable in chapter two, the fact that you intended them to be sympathetic does not change what five readers experienced. At the same time, not all feedback is correct, and accepting everything uncritically leads to a book that has been averaged into mediocrity by committee. Read every piece of feedback. Sit with it. Ask whether it points to a real problem. Then decide, from your authorial position, what to do with it.
Contradictory feedback is almost always a signal, not a problem. When one reader says your opening is too slow and another says it is the strongest part of the book, they are not cancelling each other out. They are revealing that different readers bring different expectations to this type of book. Your job is to decide which reader is your reader: who is the person you wrote this book for, and what do they need? Once you know your reader clearly, contradictory feedback becomes navigable. The feedback that aligns with your reader's expectations is signal. The feedback that doesn't is noise. Useful heuristic: when multiple readers identify the same problem through different language (“the pacing drags” and “I got bored in chapter nine” and “the middle section felt slow”), that is a confirmed problem. When feedback is genuinely contradictory and not pointing at the same place, trust your vision.
A sensitivity reader is a reader with lived experience of a specific identity, background, or experience who evaluates your manuscript for authentic and respectful representation of that group. Hire a sensitivity reader when your manuscript includes characters or communities whose experiences you do not share and who are central to the story. The purpose is not to sanitize your work or remove all conflict involving marginalized groups. The purpose is to ensure that your representation is grounded in reality rather than stereotype, and that you are not inadvertently causing harm through inaccuracy or caricature. Find sensitivity readers through professional services like Salt & Sage Books or Beta Readers Inc., or through writing communities focused on the relevant identity. Pay sensitivity readers for their labor. Their expertise is professional expertise.
Not all feedback deserves action. Some feedback reflects personal preference unrelated to your book's intended audience. Some reflects a reader's unfamiliarity with your genre's conventions. Some reflects what the reader would have written rather than what your book is trying to be. The skill of knowing which feedback to ignore is as important as the skill of knowing which to act on. Ignore feedback that: comes from a reader who is not your target audience and is calibrating to a different standard; conflicts with your book's fundamental premise or voice; is expressed as absolute prescription (“you should never use flashbacks”) without reference to your specific text; and appears only once across all your readers with no pattern to support it. Trust your vision. Take in all feedback. Act on patterns. Ignore noise. Your book should be the best version of itself, not the safest version of everyone's preferences.
iWrity gives you the tools, readers, and feedback to write books that readers finish and love.
Get Started Free →Between four and eight beta readers is the effective range for most novels. Fewer than four gives you insufficient data points: one reader's idiosyncratic reaction can feel definitive when you have no way to triangulate. More than ten creates noise: you will spend more time managing conflicting feedback than understanding it. The goal is signal, not volume. Four to six beta readers who are genuine members of your target audience and who give thoughtful, specific responses will tell you everything you need to know. Recruit readers who read widely in your genre. A thriller writer whose beta readers all read literary fiction will receive feedback calibrated to the wrong standard. Match your readers to your audience as closely as possible.
A beta reader is a member of your target audience who reads your book as a reader would: start to finish, noting where they engaged and where they disengaged, flagging confusion or boredom, reporting their emotional experience. They do not need to be writers. A critique partner is a fellow writer who reads your work with craft knowledge: they can identify structural problems, analyze scene construction, and diagnose why something isn't working rather than just reporting that it isn't. The relationship is typically reciprocal: you critique their work, they critique yours. Both are valuable at different stages. Beta readers tell you how the book lands. Critique partners tell you why it does or doesn't. Use both.
Ask specific questions that cannot be answered with yes or no. Useful questions: At what point (if any) did you feel the pace dragging? Which character did you find yourself most invested in, and why? Was there a moment where you lost track of what the protagonist wanted? Were there any sections where you considered putting the book down? What did you expect to happen that didn't? Did the ending feel earned? Avoid asking: Did you like it? Was the writing good? Would you recommend it? These questions produce responses that are kind rather than useful. You want the reader's experience, not their assessment. Their experience is data. Their assessment is opinion. Data is revisable. Opinion is noise.
Act on patterns, not individual responses. If one reader flags a scene as confusing, it may be their preference. If three readers flag the same scene as confusing, it is a craft problem. If five readers flag it, revise immediately. The same logic applies to structural feedback: one reader who wanted more romance in a thriller is expressing personal preference. Four readers who say they stopped caring about the protagonist in chapter eight are identifying a craft failure. When feedback contradicts itself (one reader says cut the opening, another says it's the strongest part), go back to your own vision of what the book is and ask which reader's response is aligned with that vision. Feedback is data to inform your decisions, not instructions to execute.
Hire a developmental editor when your manuscript is structurally complete but you suspect the story-level architecture has problems you can't identify on your own. This typically comes after at least one full revision and a round of critique partner feedback. Hire a copy editor when the story is locked: you have no more structural changes planned, the character arcs are complete, and you are satisfied with the scene-level work. Copy editing a manuscript you are still structurally revising is wasteful. Hire a proofreader as the very last step before publication. Do not publish a book that has not been proofread by someone other than yourself. Your brain knows what the manuscript is supposed to say and will read it correctly even when the page says something different.
iWrity connects authors with the craft knowledge and reader feedback they need to publish with confidence.
Join iWrity →