There is a version of peer review preparation that looks more like fortification. You revise and revise, patch every gap you can anticipate, and submit hoping that reviewers will find nothing to critique.
And, believe me, I understand that impulse completely. When your book is bound up with tenure, promotion, years of accumulated work, and your sense of whether you actually belong in this field, critique can stop feeling like feedback and start feeling like a verdict.
But peer review was never designed to tell you whether you are a real scholar or whether your project deserved to exist. It is diagnostic. It shows what is working, what has not yet come clear on the page, and what the project might need in order to become what it is trying to be.
In this episode, I also get into something harder: how to work with feedback that feels frustrating, unfair, or even hostile, without either collapsing under it or dismissing it out of hand. Not every reviewer is right. Not every suggestion should be followed.
But even a poorly framed or seemingly off-base comment can sometimes be pointing at something real—a problem of scope, audience, framing, or significance that the reviewer couldn’t quite name, but you, once you stop wincing, might be able to see.
The approach I want to emphasize here is about treating reviewer feedback as information rather than punishment, so you can sort through it with more steadiness and judgment than the first raw read usually allows. In the end, the goal of peer review is to come through it with a clearer, stronger, more intentional book—and with a little more trust in your own capacity to receive hard things and keep writing anyway.
