On Writing Slowly

There is a particular kind of writing that only happens slowly. Not slowly in the sense of typing with two fingers, but slowly in the sense of refusing to publish something the same week you thought of it. Letting the idea sit. Coming back to it on a Tuesday morning six weeks later and discovering that the cleverest line in the draft is the one you should cut first.

Most of the internet does not work this way. The feed is a machine for rewarding speed — the hot take, the live reaction, the thread posted before the dust has settled. There is nothing wrong with that. Some of my favorite reading is fast. But the medium bends writers toward a posture I want to resist: the perpetual sense that I have something to say right now, and that if I don’t say it now, the moment will pass.

The draft that you cannot put down for a month is almost always better than the one you finished in a weekend.

What I want is the opposite posture. To assume that I almost never have something to say right now. That the idea worth keeping is the one that survives a season of forgetfulness — the thought that, six months from now, still feels worth writing.

What “slowly” actually means

I have a few rules that I try (and often fail) to keep:

1. Never publish on the same day you finish a draft. Sleep on it at least once. The morning version is almost always shorter, and the shorter version is almost always better.
2. Cut the opening paragraph. The first paragraph of a first draft is almost always a throat-clearing exercise — a way of warming up to the actual subject. When I am brave enough to delete it, the essay gets stronger.
3. Read it aloud before publishing. This catches everything — the long sentences, the repetitions, the moments where the rhythm goes wrong. If I cannot read a sentence without running out of breath, the sentence is too long.

None of these are original. They are, in fact, advice you can find in any book about writing. The trick is not knowing them; the trick is doing them when you are tired and want to be done.

The cost

There is a real cost to writing slowly. You publish less. The algorithm forgets you. Readers drift away. The site goes quiet for weeks, and when you finally do post something, it feels like shouting into a room that has emptied out.

I have decided this is fine.

The reward is harder to measure but, I think, more durable. The slow pieces I have written — the ones I sat with for weeks before publishing — are the ones that still get read years later. They are the ones people email me about. They are the ones I am not embarrassed to see again.

The fast pieces, the ones I shipped in a hurry, are gone. Not just unread — gone, in the sense that I cannot remember writing them, and would prefer not to be reminded.

A small experiment

If you are reading this and you also write, I want to propose something small. Pick the next thing you are about to publish — the one that feels urgent, the one you are about to hit send on. Do not publish it today. Save it. Come back to it in a week.

If, after a week, it still feels worth saying, publish it. You will probably want to make small changes — a word here, a sentence there. That is the point. The week is not a delay. It is the work.

If it does not feel worth saying after a week, you have saved yourself from publishing something forgettable. Either way, you win.

Slow is not a virtue in itself. But it is, for me, a reliable signal that the thing I am about to put into the world is something I have actually thought about.