Skip to content
← All writing
December 25, 2025 · 4 min read

Time Blocking vs Task Batching: Which Productivity Technique Works for You?

Time blocking asks you to predict the future. Task batching asks you to group the present. Only one of those is a skill an ADHD brain has, and the good news is that batching is the one with the evidence.

I have tried time blocking four times. Each attempt produced a beautiful calendar for about a week and then a calendar that documented, in colour, how far behind I was. Task batching I adopted almost by accident, when I noticed that the days I answered messages twice were better than the days I answered them constantly. One method asked me to predict how long things would take. The other only asked me to notice what kind of thing they were.

What the two methods claim #

Time blocking assigns tasks to specific slots on the calendar: the report from nine to eleven, email from eleven to half past, and so on. Its strongest advocate argues that the block is what makes deep work possible, because it pre-decides what you will do and defends it from everything else (Newport, C., 2016).

Task batching groups similar work together regardless of when: all the messages at once, all the reviews at once, all the small admin in one sweep. The claim is that switching between kinds of work is what costs you, so reducing the number of switches recovers the cost.

What the evidence supports #

Batching has the cleaner case. Switching tasks is expensive in a way that has been measured repeatedly: attention residue from the task you left degrades performance on the next (Leroy, S., 2009), and after an interruption knowledge workers took twenty-odd minutes to return to what they were doing, working faster and under more stress to compensate (Mark, G. et al., 2005) (Mark, G. et al., 2008). Every switch avoided is a cost avoided. Batching directly reduces switches.

Time blocking’s evidence is indirect. The plan-then-do part is real: deciding in advance what you will do at a given cue is among the best-supported techniques for actually doing it (Gollwitzer, P. M. & Sheeran, P., 2006). But the block also asks you to estimate duration, and duration estimates are reliably too short even for people who know about the planning fallacy (Buehler, R. et al., 1994). The block inherits the strength of the plan and the weakness of the estimate.

Why ADHD tips the balance #

Two ADHD-specific facts make blocking harder and batching more valuable.

Time estimation is worse. People with ADHD misjudge duration in both directions and experience time as now versus not-now rather than as a gradient (Ptacek, R. et al., 2019); a slot at 14:00 generates no pressure at 13:40. Blocks slip, and rigid plans fail rigidly: one missed block becomes evidence the system is broken, which becomes guilt, which is what turns the next task into one to avoid (Sirois, F. M. & Pychyl, T. A., 2013).

Switching is costlier. Inhibition - not responding to the new thing - is where adults with ADHD diverge most sharply from everyone else, across the executive-function studies in ADHD (Willcutt, E. G. et al., 2005), so interruptions capture attention more easily, and re-engaging with the abandoned task takes longer. Batching attacks exactly this.

The hybrid that works #

The answer is not one or the other. It is blocking the container and batching the contents.

  1. Two or three themed blocks per day, not a full schedule. “Deep work, morning” and “messages and admin, late afternoon” - big, forgiving, named. Inside the block you know the kind of work, not the exact task. That is a block that survives a bad estimate.
  2. Batch everything reactive into one or two windows. Messages, code reviews, small decisions. Outside the windows, notifications are off and small things go on a list; inside them, two-minute things get done on the spot.
  3. Batch by cognitive mode, not by project. Writing with writing, reviewing with reviewing, calls with calls. The residue is worst when the mode changes; two writing tasks back to back cost less than a writing task and a spreadsheet.
  4. Themed days if your week allows it. A meetings day and a building day beat every day being both. This is batching at week scale, and for me it is the single biggest reduction in switching I have found.
  5. Buffers, always. Fifteen minutes between blocks, no exceptions. Buffers are where the estimate error goes to die instead of into the next block.

Which one is yours #

If you have a job with a predictable shape and a reliable sense of time, full time blocking will work and it will feel good. If you have ADHD, or a job that interrupts, or both, start from batching and add only as many blocks as you can defend. The test is simple: does the calendar at the end of the week look like a plan that mostly happened, or like a record of failure? The method that produces the first is the right one, whatever the productivity books call it.

A small test: for one week, block nothing except two message windows a day. Write down every time you switch tasks for a reason that was not in the window. That count is what batching will save you, and it is usually higher than any calendar would have predicted.

Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the “planning fallacy”: Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366–381. https://doi.org/10.1037/0022-3514.67.3.366
Gollwitzer, P. M. & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69–119. https://doi.org/10.1016/S0065-2601(06)38002-1
Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168–181. https://doi.org/10.1016/j.obhdp.2009.04.002
Mark, G., Gonzalez, V. M., & Harris, J. (2005). No task left behind? Examining the nature of fragmented work. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI 2005), 321–330. https://doi.org/10.1145/1054972.1055017
Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI 2008), 107–110. https://doi.org/10.1145/1357054.1357072
Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing.
Ptacek, R., Weissenberger, S., Braaten, E., & et al. (2019). Clinical implications of the perception of time in attention deficit hyperactivity disorder (ADHD): A review. Medical Science Monitor, 25, 3918–3924. https://doi.org/10.12659/MSM.914225
Sirois, F. M. & Pychyl, T. A. (2013). Procrastination and the priority of short-term mood regulation: Consequences for future self. Social and Personality Psychology Compass, 7(2), 115–127. https://doi.org/10.1111/spc3.12011
Willcutt, E. G., Doyle, A. E., Nigg, J. T., Faraone, S. V., & Pennington, B. F. (2005). Validity of the executive function theory of attention-deficit/hyperactivity disorder: A meta-analytic review. Biological Psychiatry, 57(11), 1336–1346. https://doi.org/10.1016/j.biopsych.2005.06.011