The Reader Report Approach
The reader report is a structured method for giving feedback that separates your experience as a reader from your opinions as a writer. A reader report has three parts: what you understood (your summary of the story's plot and themes, which reveals whether the writer's intentions landed), what confused you (moments where you lost the thread, questioned motivations, or re-read passages without clarity), and what you wanted more of (scenes, characters, or ideas that felt underdeveloped). This structure keeps feedback grounded in the reading experience rather than in the critiquer's preferences about how the story should have been told.
What Makes Feedback Useful vs. Useless
Useful feedback is specific, observable, and reader-based. 'I found it hard to care about the protagonist in chapter three because I didn't understand what she wanted' is useful. 'I didn't like the protagonist' is not. 'The pacing felt slow in the middle section, specifically around chapters eight through eleven' is useful. 'It was a bit slow' is not. The key distinction is between reporting your experience as a reader (useful) and expressing preferences about how the story should have been told (usually not useful). A good critiquer reports symptoms rather than prescribing cures.
Giving Feedback on Plot, Prose, and Character Separately
Mixing feedback on plot, prose, and character in a single undifferentiated response is hard to act on. Separate them deliberately. Plot feedback addresses structure, pacing, causality, and narrative logic: does each scene cause the next, do the stakes feel real, does the ending follow from what came before? Prose feedback addresses the sentence level: clarity, rhythm, voice consistency, dialogue naturalness. Character feedback addresses motivation, consistency, and distinctiveness. When you give feedback on all three at once, the writer cannot tell which layer needs attention. Label your feedback by layer.
The 48-Hour Rule for Receiving Criticism
When you receive feedback on your writing, especially harsh or unexpected feedback, wait 48 hours before responding or acting on it. This is not about being polite. It is about the fact that your first reaction to criticism is almost never your most useful reaction. The initial response is often defensive, dismissive, or overcorrecting. After 48 hours, you can usually read the feedback more neutrally and assess whether it is identifying a real problem or a mismatch of expectations. The 48-hour rule applies especially to feedback that makes you want to argue, dismiss the reader entirely, or rewrite everything immediately.
When to Take Feedback and When to Ignore It
Take feedback when multiple readers independently identify the same issue, when a reader points to something that you knew was a problem but hoped nobody would notice, or when a trusted reader with genre knowledge flags a structural issue. Ignore feedback when a single reader wants you to write a different book, when the feedback contradicts the established genre conventions you are deliberately working within, or when the feedback is about the theme or subject matter rather than the execution. You cannot revise to satisfy everyone. Your job is to make your book more fully what it is, not to make it different from what it is.
Running a Writing Group Critique Session
A well-run writing group critique session has a structure: the author is silent while the group discusses the work (no explaining, no defending), each reader gives their response using the reader report format, specific questions from the author are addressed at the end. The silent author rule is critical because explanation kills useful feedback: if the author says 'but what I was trying to do was...' the critique stops being about the reading experience and starts being about the author's intentions. Good intentions and successful execution are different things. The critique session reveals what the text actually does, not what the author hoped it would do.
