Productivity has become one of the dominant frames through which work — including writing — is discussed and understood. The language of productivity is everywhere: output, throughput, optimisation, systems, workflows, batching, time-blocking, deep work, shallow work. These terms do not just describe how work is done. They shape how work is understood — what counts as progress, what counts as waste, and what the purpose of working is.
For writers, this language presents a particular problem. Writing is not well-described by productivity vocabulary, and the attempt to describe it that way tends to produce a distorted picture of what writing is and how it happens. Understanding what the language of productivity does to the way writing is understood is the first step to resisting it.
What Productivity Language Assumes
The language of productivity is built on a set of assumptions that are reasonable for some kinds of work and poorly suited to others.
The first assumption is that output is measurable. A productive factory produces more units per hour than an unproductive one. A productive meeting produces more decisions per minute than an unproductive one. The measurement may be rough, but the principle holds: productivity is assessed by comparing output to input, and the relationship can be quantified.
Writing resists this assumption. A writer who produces two thousand words a day is not, for that reason, more productive than one who produces five hundred — unless the two thousand words are of comparable quality to the five hundred, which they often are not. The word count measures activity, not productivity, because the value of writing is in its quality rather than its quantity. A productivity frame that ignores quality and counts words is not measuring writing productivity; it is measuring typing.
The second assumption is that time spent is the primary input. A productive worker maximises valuable output per unit of time. This leads, in productivity vocabulary, to an obsession with eliminating wasted time — with filling every available unit with purposeful activity. For writing, this assumption is also poorly suited. Much of what writing requires — the incubation of an idea, the slow accumulation of thinking that precedes drafting, the distance from a piece that makes revision possible — does not look like work from the outside and does not produce immediate output. A productivity frame that cannot account for thinking that produces no visible output cannot account for most of what writing actually requires.
What the Language Does to Writers
Writers who have internalised the language of productivity tend to exhibit specific symptoms.
The first is guilt about thinking. A writer who has adopted a daily word count as their measure of productivity feels, on days when they think but do not write, that they have been unproductive — that the time has been wasted. This guilt is not just uncomfortable; it is counterproductive. The thinking that happens between drafting sessions is often the most important work the writer does, and the guilt that labels it as inactivity tends to interrupt it.
The second symptom is the equation of volume with value. The writer who has learned to measure themselves by output — by posts published, words written, pieces completed — tends to produce more and to think less carefully about each piece. The incentive structure that productivity language creates rewards frequency over quality, and the writer who is sufficiently immersed in that structure tends to produce work that reflects it.
The third symptom is the search for systems. The productivity literature promises that the right system — the right workflow, the right set of habits, the right time management technique — will unlock consistent high output. Writers who have adopted this frame spend time building and refining systems that will, in theory, make the writing happen more reliably. The irony is that the time spent optimising the system is time not spent writing, and the system, once built, does not solve the actual problem: that writing is hard and requires thinking, and thinking cannot be systematised.
What a Better Frame Looks Like
The alternative to productivity language for writing is not the absence of any frame — not a romantic idea of the writer waiting for inspiration with no regard for consistency or output. It is a frame that accounts for what writing actually involves: sustained thought, gradual development of ideas, the slow accumulation of material that eventually becomes a piece worth reading.
This frame measures differently. Not words per day, but the quality of the thinking that is happening. Not pieces published, but whether the pieces that are published say something worth saying. Not time spent at the desk, but whether the time away from the desk — the walking, the reading, the letting things sit — is producing the kind of thinking that writing requires.
It also evaluates differently. A day on which no words were written but an argument clarified is not an unproductive day — it is a day on which the necessary precondition for good writing was advanced. A day on which two thousand words were written but the argument remained unclear is not a productive one, regardless of what the word count says.
The language of productivity is useful for many kinds of work. Writing is not straightforwardly one of them. The writer who applies productivity vocabulary to their practice without examining what it assumes tends to produce more — and to think less carefully about what the more is for.
Output is not the point. The point is what the output says, and how well it says it.
