Why You Should Keep a Feedback Log

Here is a portion of an actual rejection I received recently:

Thank you for trusting me with your manuscript, and for your patience as I read. I can see immediately that this book comes from deep love and lived experience. The opening scenes are intimate and sharply rendered. Your use of etymology and linguistic framing gives the memoir an intellectual architecture that reflects your devotion to language. The braided sections are especially moving; they create a layered perspective that feels rare and generous. This is clearly a book written by someone who understands craft. The structure is intentional. The voice is steady. The relationship is examined with intelligence rather than sentimentality, which I respect. That said, after careful consideration, I’m going to pass on this project.

If you're like my best friend, you just laughed out loud. Like...what?

Feedback is a data point, not a verdict. In this case, I got nothing useful to apply because there wasn't anything wrong with my work. It just wasn't for them.

I highly recommend that you keep a feedback log for the work you send out.

When the same note shows up from multiple independent readers, that's a signal. When it shows up once, that's noise — possibly useful noise, but noise. A simple running document where you track who said what, and whether others echoed it, will save you from over-correcting on a single opinion and help you spot the patterns that actually deserve your attention.

For each piece of feedback, note the source, the specific concern, and — crucially — your gut reaction when you first read it. That reaction is data too. Then, once you've let some time pass, return and note whether your gut still holds. Did the sting fade and leave something worth considering behind? Or does the feedback feel just as off-base as it did on day one?

Before you touch a word, run this quick triage: Is the feedback pointing to a craft issue (clarity, pacing, structure) or a preference (tone, subject matter, style)? Craft issues are worth a hard look. Preferences are worth a nod and a pass. The two get conflated constantly, and conflating them will send you down revision rabbit holes that lead nowhere useful.

Over time, your log becomes a record of your own editorial instincts sharpening, not to mention some hard evidence that you can trust them.

We do need to be open to the possibility that feedback reveals something you missed in our self-editing. But less discussed is the possibility that the feedback doesn't reveal any such thing. After all, the goal isn't to write something no one can find fault with. It's to write the truest, strongest version of what you're making.

Tips