← Back to Essays  ·  12X EDU
Craft  ·  7 min read

Why Every Writer Should Read Like an Editor

The standard advice given to anyone who wants to write better is to write more. It is not wrong, exactly, but it is incomplete in a way that sends a lot of writers down a long, inefficient path. Volume alone does not sharpen judgement; it mostly reinforces whatever habits — good or bad — a writer already has. What actually accelerates improvement is a different kind of reading: reading the way someone reads when they must decide, professionally, whether a manuscript deserves a yes or a no.

How an editor reads

An editor reading a submission is not reading for pleasure, and this changes everything about the activity. They are reading for structure — where does the piece actually begin, and is that different from where it starts. They are reading for economy — which sentences are doing work, and which are simply occupying space because the writer liked the sound of them. They are reading, most uncomfortably, for the moment where their attention first starts to drift, because that moment marks exactly where the piece has failed to earn its next paragraph.

Does this earn its place, and if it were cut, would anything actually be lost?

Most writers never read this way, even about their own work, let alone anyone else's. They read for meaning, for enjoyment, for the pleasure of a good sentence — all legitimate reasons to read, but none of them teach craft directly. Craft is taught by the much colder question an editor asks by default.

Reading favourites with clinical distance

Learning to ask that question is uncomfortable at first, because it requires reading favourite books with a slightly clinical distance — noticing, for instance, that a beloved novelist regularly opens chapters with weather, and asking why that choice works there and would fail in your own draft. It means noticing where a paragraph you admired could lose its middle third with no damage to the argument, and sitting with the fact that most writing, including your own, is carrying more weight than it needs to.

There is a second, less obvious benefit to reading like an editor: it recalibrates your relationship to rejection and revision. Someone who has spent time evaluating other people's manuscripts with a critical but fair eye develops a much more accurate sense of where their own work actually stands, rather than the two extremes most writers oscillate between — private certainty that a draft is brilliant, or private conviction that it is worthless. An editor's eye tends to land somewhere more useful: specific, correctable, unemotional.

Read for pleasure too

None of this argues against reading purely for pleasure. That kind of reading is where the love of language comes from in the first place, and craft built without it tends to be technically competent and lifeless. But a writer who reads only for pleasure, and never learns to read the way a gatekeeper reads, will keep making the same structural mistakes indefinitely, because pleasure-reading rarely interrogates why a piece works. It only registers that it does.

The next time you finish something you loved, go back through it once more — looking for the moment your attention would have wandered if you had been reading it as a stranger's submission.

That single pass, repeated across enough books, will teach you more about your own writing than another hundred thousand words of first drafts.