The Virtue of Slow Work
Against the idea that speed is always a virtue. Some things need to take the time they take.
Speed is seductive because it looks like virtue. To work quickly is to be efficient, productive, decisive. To work slowly is to be stuck, indecisive, behind.
But there are kinds of work where speed is not a virtue at all. Where the slowness is the work.
Writing is like this, for me. I can produce words quickly. I cannot produce good sentences quickly. A sentence that reads as effortless usually took a long time to become effortless. The ease is deceptive; it is the residue of labor, not the absence of it.
What slow work actually is
Slow work is not procrastination. Procrastination is avoidance — not doing the work. Slow work is doing the work at the pace the work actually requires.
The difference matters because the internal experience is different. Procrastination involves anxiety, avoidance, the nagging sense of something undone. Slow work, when you’re actually in it, can feel spacious. You are in contact with the thing. You are attending to it. Time moves differently.
I think of the ceramicist who takes months to complete a piece that another craftsperson might complete in days. Not because she is less skilled, but because she is doing something different — attending to subtleties that require multiple sessions, living with the piece across time, letting her sense of it evolve.
Or the scientist who has been thinking about the same problem for decades. Not because he hasn’t found the answer, but because the question keeps deepening. Each thing he learns opens new questions. The work is the thinking, and the thinking takes as long as it takes.
The tyranny of throughput
We have become very good at measuring throughput — units of output per unit of time — and very bad at measuring quality that doesn’t reduce to throughput.
How many lines of code written? How many articles published? How many tickets closed? These are easy to track. How deep was the thinking? How lasting will it be? How much will it teach the person who encounters it? These are much harder, and so we often stop asking.
This creates pressure toward work that can be done quickly, that can be measured, that can be seen to be done. Slow work that lives mostly in the mind, that has nothing to show for long stretches, that resists easy accounting — this kind of work is structurally disadvantaged.
A defense of the necessary
I am not arguing for slowness for its own sake. Slow work done badly is just slow. The question is what the work requires, and whether you are willing to give it that.
Some things cannot be rushed without being ruined. A relationship that has depth cannot be accelerated. An understanding that is genuinely your own cannot be outsourced. A piece of writing that sounds like a person cannot be generated.
This is not nostalgia for the pre-digital. It is an observation about what certain things require. The time is part of the process. Removing it removes the thing.