Time blocking, honestly: what it does, what it doesn't, and how to actually do it
Time blocking is the practice of giving every hour of your work day a single, specific job before the day starts. You write “9 to 11: draft proposal” instead of writing “draft proposal” on a to-do list and hoping it happens. The idea is that decisions about when you do something are easier to make in advance, when you are calm, than in the moment, when you are not.
It works. It is also the productivity practice I have most often seen people abandon within a week, including me, three times. The reason is almost never the technique. It is the way the technique gets sold.
Where most time-blocking guides go wrong
The standard guide will tell you to map out every hour of your day, including breaks, meals, and “deep work blocks” of two and a half hours. You will look at the resulting calendar and feel virtuous. Then on day two you will get a Slack message at 9:47 that derails your 10:00 block, and the cascading rearrangement will be so annoying that by Wednesday you will have stopped opening the calendar.
This is the part that almost no productivity influencer tells you: a good time-blocked day is mostly empty.
The blocks should cover the work that only you can do, scheduled when you are most able to do it. Everything else — admin, calls you cannot avoid, the inevitable interruptions — fills the space around them. If your blocks cover seventy percent of your day, you have over-scheduled. The system is not a TV guide. It is a defended perimeter around the parts of your day that matter most.
The honest version of the technique
Three blocks. Maybe four on a good day. Each block is one task — not a category, not a project, but the specific deliverable you are working toward.
For me, the first block is always something that requires my brain to be at full power, and it is always 90 minutes, sometimes broken into two pomodoros (the Pomodoro guide explains why). The second block is usually responsive work — code review, replies, the things that are easier when I am warm but already past peak. The third is whatever is left, and it gets whatever energy is left.
If a fourth block survives, it is usually for something administrative I have been avoiding. Time blocking is unusually effective for this. Putting “do expenses, 2:00–2:30” on the calendar somehow makes me do expenses; “do expenses” on a list does not. I have never figured out exactly why, but the effect is consistent.
The 90-minute number is real
There is a body of research on ultradian rhythms — roughly 90-minute cycles of arousal and recovery that the brain runs throughout the day. After about 90 minutes of focused work, attention measurably degrades and the recovery from a short break is faster and more complete than the recovery from pushing through. The exact biology is more debated than you would think reading productivity blogs, but the practical effect is something most people who do focused work for a living have noticed independently.
So 90 minutes is the upper sensible block size. Below that, 50 minutes is the sweet spot — long enough to get into something, short enough to sustain three or four times in a day. A 50-minute timer is what I personally use most often.
What to do during the gap between blocks
Walk somewhere. Anywhere. The single most effective thing you can do between focus blocks is move, ideally outside, for between five and fifteen minutes. The next-best thing is something physical that requires no decision: dishes, a stretch routine, watering plants. The worst thing — and this took me years to admit — is checking your phone, even for “just a minute.”
The reason is that your brain uses the gap to consolidate what it just worked on, and external input crowds that out. You will know consolidation has happened when, on the way back to your desk, the next thing you should do appears in your head without effort. If the next step does not arrive, your gap was not really a gap.
When time blocking does not work
Time blocking is for output-focused work. It is excellent for writing, coding, designing, analysis, planning. It is mediocre for jobs that are mostly responsive — customer support, on-call engineering, sales calls — where the next 30 minutes is genuinely whatever the next email demands.
It is also bad for creative exploration that has no defined endpoint. If you are trying to figure out what your novel is about, a 90-minute block will not get you there in 90 minutes; it will probably take six weeks of unstructured staring at the ceiling. Time blocking will give you the discipline of showing up, which is real, but you should be honest with yourself that the block is for showing up, not for delivering something specific.
A small practical setup
I use whatever calendar I have for actual meetings, and a separate paper notebook for the day’s blocks. The reason is friction: writing the blocks by hand on paper makes me commit to them in a way that dragging events around in Google Calendar does not. The morning ritual is about ten minutes — list three things, write block sizes, put them on the page in order. The day’s structure is set before the inbox is open.
A timer on the desk, ideally a physical one or a separate browser tab, gives the block a hard edge. I have written elsewhere about why putting the timer in the same window as your work tends to mean you will dismiss it absent-mindedly; the study timer page is the version of swifttimer designed for this use.
If you want to try it
Pick one day this week. Write three blocks for it, the night before. Keep the rest of the day unscheduled. See what happens.
If even one of those three blocks survives contact with the actual day, you are doing better than most people. If two survive, you are doing well. If all three survive, you have probably over-protected your time and someone is annoyed at you, which is sometimes also fine.
Two weeks of this and you will start to feel the difference. That is how long it takes my own habits to recompile.
If you want a bit more on why this site exists or who built it, the about page covers it.