A Small System for Deep Work
Deep work does not need another app. It needs a defensible block of time, a paper notebook, and a shutdown ritual that closes the loops before the day ends.
Contents
I do not have a productivity system. I have a calendar block, a paper notebook, and a shutdown ritual I follow maybe four days out of five. That has been enough. The weeks when I abandon all three are also the weeks I end with the vague feeling of having been busy without having moved anything.
The two-hour block
Two hours is the unit I protect. Four would be better and is usually a fantasy in a job with meetings. Two is long enough to load the problem into my head and short enough that I can defend it on a calendar.
The block has one rule: I write the outcome before I start. Not a task, an outcome. “Fix the upload bug” is a task. “A failing upload produces a useful error in the UI, and I have watched it happen” is an outcome. If I cannot name one, the block is for reading or thinking, not coding.
The block is not sacred because of its length. It is sacred because it ends. Knowing when it stops makes it easier to start.
Why task lists fail
A task list is an inventory, not a decision. It grows because adding is cheap and finishing is expensive. Forty open items is not a plan; it is a mood.
The failure mode is predictable. I pick the easiest item to feel progress, or I spend the first twenty minutes reorganizing the list, which feels like work and produces nothing. The list is also where anxiety accumulates, because every item is a reminder of something I am not doing right now.
What works better is one outcome per block, plus a separate list for everything else that I do not open during the block. The big list is for the weekly review. The block gets one thing.
The shutdown ritual
The end of the day matters more than the start. If I close the laptop with six open loops, my brain keeps running them at dinner. The ritual is ten minutes and it is mostly writing.
- Write tomorrow’s first action in one sentence.
- Move everything unfinished to a dated note, not back to the top of the big list.
- Close the editor and the issue tracker.
- Write one thing that went wrong and one thing I will do differently.
- Say, in a note or out loud, that the day is over.
The phrase sounds ridiculous until you try it. Open loops are what keep you awake; the note is a contract with tomorrow-you.
Deep work ends at a time, not when the problem is solved.
A daily checklist
- One outcome written before the block.
- The block is on the calendar and I have not scheduled over it.
- Notifications off, phone out of reach rather than face down.
- One tab for the task; everything else closed.
- Shutdown note with tomorrow’s first action.
- One sentence about what I learned.
The weekly review
Thirty minutes on Friday. I do not use an app for this; a text file is enough and it opens faster than anything with a login screen.
Week of:
Shipped:
- ...
Still open:
- ... (next action, owner)
Learned:
- ...
Next week:
- Protected blocks: Tue 09:00-11:00, Thu 09:00-11:00
- Meetings I can decline:
- One thing to stop doing:
The review is not a report. Nobody reads it. Its job is to move the open loops out of my head and into a place where they still make sense on Monday. If I skip it for two weeks, the third week is recognizable by the number of things I have started and not finished.
Protecting time on a team
Protecting a block is a social problem before it is a calendar problem. A few things have worked for me.
- Put the block on the calendar with a plain title. “Focus” is fine; “deep work” invites comments.
- Publish office hours for questions and direct people there. Being always available is not a virtue; it is a routing policy.
- Agree on response expectations. Most messages do not need an answer in five minutes, and saying so out loud makes it true.
- Make the trade explicit: “I can do that today or the review, not both.” People respect a choice; they do not respect a vague yes.
- Protect other people’s blocks too. Do not schedule over a focus block because your meeting is urgent.
A calendar with no blank space is not a sign of importance. It is a sign that someone else is doing your prioritization.
When the day is fragmented
Some days are twenty-minute gaps between meetings, and pretending otherwise makes them worse. I keep a short list for those days: review a pull request, write a decision note, update an issue, read one section of documentation. None of it requires loading a large problem into my head.
What I try not to do is start a deep task I cannot finish. Leaving a half-loaded problem costs more than it saves, because tomorrow I have to load it again and re-derive the context I dropped. If I get forty-five uninterrupted minutes, I take them and call it a win. If I get twenty, I do correspondence and stop pretending.
The system is small on purpose. A system you can follow on a bad day is worth more than one that works only on a good one. The tools promising to organize all of this are their own kind of convenience, and the same instinct applies to the feedback loops you build at work: a pipeline nobody has to think about is a pipeline that respects your attention, which is the argument in Your Build Pipeline Is a Product.
Further reading
The irregular letter
New essays, every other Tuesday.
One thoughtful piece on building software, written for humans. No links roundups, no growth hacks, no tracking.
Email capture is configured at launch. Until then, write to hello@blog.waystoneai.online.
Every other Tuesday · No tracking pixels, no resale, one-click unsubscribe.