The to-do list on my desk this morning, written in pencil on the back of a postcard from a friend in Kyoto, contained six items. Four of them carried over from yesterday. Two were new. By the end of the day I had done three. The other three I rewrote, slightly modified, on a fresh card for tomorrow. The pencil tip is dull. The card is creased at one corner. This is, by every standard the contemporary productivity literature endorses, a failure of system design. It is also, after fifteen years of trying more elaborate systems, the only way of working that has lasted.
This essay is about the wabi-sabi reading of productivity — what "good enough" looks like when the goal is not optimisation but sufficiency, and how the major Western productivity frameworks look when placed against that standard. I will say in advance that I do not think the wabi-sabi reading dissolves the productivity literature. It locates it. The frameworks are useful; they are simply not the thing itself.
The optimisation premise
Most contemporary productivity writing — David Allen's Getting Things Done, Cal Newport's Deep Work, Tiago Forte's Building a Second Brain, the constellation of newer frameworks around them — shares a premise that often goes unstated. The premise is that the human worker is a system that can be tuned, and that the tuning, done well, produces meaningfully better outputs over time. The labour of the productivity practitioner is, in part, the labour of designing and refining the tuning.
This premise is not wrong. Allen's capture-clarify-organise-reflect-engage cycle does, in fact, reduce the cognitive overhead of holding open commitments in working memory. Newport's deep-work argument does, in fact, identify a real and valuable mode of attention that is being eroded by always-on communication. The frameworks describe real phenomena and offer real tools. People who use them well genuinely do produce more, and often better, work.
The wabi-sabi question is not whether the optimisation premise is correct. It is whether the optimisation premise is sufficient — whether a life organised entirely around it produces a good life, or only a productive one.
Sufficiency as an alternative frame
The wabi-sabi sensibility, drawn from medieval Japanese tea-ceremony culture and the broader Sōtō Zen tradition, treats sufficiency rather than optimisation as the appropriate measure. The tea master Sen no Rikyū, asked what was essential to the tea ceremony, is said to have answered: a kettle that boils water, a bowl that holds tea, a person who drinks it. The answer is not a minimalist provocation. It is a precise statement of what the practice requires. Anything beyond is permitted but not required.
Applied to work, the sufficiency frame asks a different opening question. The optimisation frame asks: how can I do more, better, faster? The sufficiency frame asks: what is enough? What does the work, today, actually require? What would constitute a successful day if "successful" did not mean "maximally productive"?
These questions are not in opposition. A person can ask both. But they produce different days. The optimisation frame produces a day in which the worker is constantly comparing actual output to potential output, and finding the gap unsatisfying. The sufficiency frame produces a day in which the worker has, at some point in the afternoon, the experience of having done enough — a state that the optimisation frame structurally cannot reach, because the potential ceiling is always higher than the actual.
Reading GTD on the wabi-sabi axis
David Allen's Getting Things Done, which I have read three times over the years and used in various forms, holds up surprisingly well to wabi-sabi reading.
The capture step — the practice of writing down every open commitment as soon as it enters the mind — is fundamentally a sufficiency practice, not an optimisation one. The argument is not that captured commitments produce more output; it is that they release the mind from the low-grade labour of remembering. This is closer to the wabi-sabi instinct than the productivity-influencer reading of GTD often acknowledges. The point of the practice is not to do more. It is to be less occupied by what is not yet being done.
Where GTD drifts away from wabi-sabi is in its more elaborate organisational architecture — the contexts, the projects-and-next-actions distinction, the weekly review. These are useful tools, and they work. They also tend to expand. The practitioner who starts with a notebook and a few lists ends, often, with a multi-tier digital system that requires its own maintenance. The system becomes a thing to tend rather than a thing to use. The wabi-sabi reading would suggest stopping earlier — using the capture instinct, perhaps a single weekly review, and resisting the rest until it becomes obviously necessary.
I have, over the years, settled into a version of GTD that fits on a single sheet of paper: capture into a notebook, sort weekly into "do this week" and "later," review each Sunday morning over tea. This is less than Allen recommends. It is more than enough.
Reading Deep Work on the wabi-sabi axis
Cal Newport's Deep Work is harder to place. Its central claim — that sustained, undistracted attention on cognitively demanding tasks produces work of higher value — is straightforwardly compatible with the wabi-sabi instinct. The medieval tea master would have recognised the description of focused attention immediately. The practice of shoshin (初心), beginner's mind, depends on the same kind of single-pointed attention Newport is describing.
Where the wabi-sabi reading parts company with Newport is in the implicit metric. Newport's argument, especially in his more recent work, increasingly treats deep work as an instrument for high-value output: writing books, producing research, building careers. The deep work is in the service of an output that justifies it.
The wabi-sabi reading would treat deep work as valuable in itself, regardless of whether the output is impressive. Two hours of focused attention on a difficult sentence is a wabi-sabi practice whether the sentence ends up in a published book or in a notebook no one reads. The attention is the work. The output is downstream and uncertain. The optimisation frame finds this hard to accept; the sufficiency frame finds it natural.
This is not a critique of Newport, who is a careful thinker. It is a noticing of where the frameworks point. Deep work plus optimisation produces a writer with seven books. Deep work plus sufficiency produces a writer with three books and a quieter relationship to the work. Both lives are coherent. They are not the same life.
The wabi-sabi reading of templates
I want to say something, briefly, about templates, because they are where the optimisation instinct most often colonises the actual work.
The contemporary productivity ecosystem — Notion in particular — has produced an enormous body of templates: aesthetic, elaborate, often beautiful, designed to make a particular kind of organised life turnkey. I have used and built and abandoned a number of them. The wabi-sabi reading of templates, after years of this, is that the best ones are the ones that are obviously imperfect — that have visible empty fields, ad-hoc sections, places where the original designer evidently gave up and left the structure incomplete.
A template that is too polished is a template that is hiding the work. A template that has been used by a real person, with real edits and real abandoned sections, is a template that admits what the work is actually like. My own kakeibo template on Notion — the one I link in the budgeting essays — is deliberately rough at the edges, because the budget I keep in my own copy is rough at the edges, and a template that does not admit roughness is teaching the wrong thing.
The wabi-sabi instinct, applied to template design, is to leave the seams visible. The user who arrives at a polished template often spends months trying to live up to it. The user who arrives at a template that admits its own incompleteness can begin using it the same day.
The day, instead
I would like to describe a wabi-sabi-shaped working day, briefly, because the abstraction is easier when grounded in a shape.
A wabi-sabi day begins with a small, written list of the day's intended work. The list is short — three or four items, occasionally six — and is written in the morning, by hand, on whatever paper is to hand. The list is provisional. It is allowed to change.
The work happens in two or three blocks. Each block is bounded by a small ritual — a cup of tea, a short walk, a stretch — that marks the transition. Within the block, the worker attends to one thing. Notifications are off. The block ends when the work is at a natural stopping point, or when the worker's attention has clearly drifted, whichever comes first. The block is not extended past the point of usefulness; the wabi-sabi instinct is suspicious of pushing through.
At some point in the afternoon, the worker stops. The list is reviewed. Items completed are crossed off. Items not completed are either rewritten on tomorrow's list or removed. The day is closed. There is no second wave of evening work, no additional optimisation pass, no reflection on what could have been done better. The work that was done is the work that was done.
This day produces less than an optimised day. It produces enough. Over a year, the difference in output is smaller than the optimisation literature would predict, because the optimised days are almost always followed by partial days of recovery, while the sufficient days produce a more even line. Over a decade, the difference in the worker is large. The optimised worker is more accomplished and more tired. The sufficient worker has done less and is still doing it.
The point of working
The deepest divergence between the two frames is in what the work is for.
The optimisation frame treats work as the means to an output that justifies the work. The output is the point; the work is the cost. A more efficient worker is one who pays less cost for the same output, or extracts more output from the same cost.
The wabi-sabi frame treats the work, when it is done well, as part of what makes a life. The output matters — it would be sentimental to claim otherwise — but the quality of the hours spent on the work is also the point. A life of beautiful work that produces moderately good outputs is, on this view, not worse than a life of efficient work that produces excellent outputs. It may be better. The medieval tea master would not have thought this controversial.
This is, in the end, what the wabi-sabi tradition has to offer the contemporary productivity conversation. Not a rejection of the tools. Not even a rejection of the optimisation premise. Only a quiet question, asked at the end of a day in which the list is half-crossed and the next day's list is already written: what would it mean to have done enough? And: have I, perhaps, already done it?
If you would like a quieter weekly letter on this — slow work, slow money, slow Tokyo — it lives on Substack.