Last week I talked about the hidden curriculum of academic book writing: the professional knowledge scholars are expected to have but are rarely taught directly.
We covered why a book is a different genre than a dissertation, how to think about press selection as a question of fit rather than only prestige, and what a book proposal actually needs to do for the editor who receives it.
You can listen to that episode here:
This week I turn to what happens after the book enters the publishing system, which is often where even very accomplished scholars start to feel unsteady.
An editor expresses interest, and then things go quiet. Reader reports come back contradicting each other. You are asked to revise, but it is not always clear which feedback deserves your full attention and which reflects one reader’s preference for a different book entirely.
A lot of what I want to do in this episode is slow the process down so it becomes legible. Academic publishing timelines are genuinely long, and without a basic understanding of why, ordinary delays can start to feel like evidence of something: that the project is wrong, that you misjudged your readiness, that you are not really a book writer. Part of what the hidden curriculum costs people is the psychological load of interpreting silence without any framework for what silence normally means.
The other thing I spend time on is peer review, and specifically the skill of reading feedback rather than simply surviving it. Reader reports are not verdicts. They are one or two people’s encounters with your manuscript from their own location in the field, and your job as the author is to interpret them strategically: to find what is genuinely pointing to a problem in the manuscript; to distinguish that from a reviewer asking for a different book; and to make revision decisions that strengthen your project rather than dissolve it into someone else’s.
Revision, I argue, is less about fixing and more about design—the work of shaping the reader’s experience across the whole manuscript, which requires you to hold onto your own authority over the project even while taking feedback seriously.
The overarching theme running through both episodes is that when professional knowledge is distributed unevenly, confusion is perceived as inadequacy.
The goal of these two episodes is to give you a little more of the map — not so that publishing becomes easy, but so that you can stop experiencing its difficulties as proof that you were never ready.
