What is batch processing tasks for productivity?

Batch processing tasks for productivity is a concept in personal epistemology: Group similar small tasks together and process them in one dedicated block, so that setup costs are paid once instead of once per task.

Example: You check email forty-seven times per day. Each time, you open your inbox, scan for anything urgent, read a few messages, reply to one or two, switch back to whatever you were doing, and then spend several minutes reloading the context of the work you interrupted. The email itself takes three minutes. The context reload takes eight. Multiply that by forty-seven and you have spent over six hours — most of your working day — not on email and not on your real work, but on the transitions between them. Now imagine a different pattern: you check email three times per day, in dedicated thirty-minute blocks at 9 AM, 1 PM, and 5 PM. During each block, you process everything that has arrived since the last block. You reply, forward, archive, and flag. Then you close the inbox and do not reopen it until the next block. The total time spent on email is roughly the same — maybe ninety minutes. But the total time spent on context switching drops from six hours to three brief transitions. You have recovered nearly five hours of your day without answering a single email less.

This concept is part of Phase 42 (Time Systems) in the How to Think curriculum, which builds the epistemic infrastructure for time systems.