Batch tasks by cognitive context…
When batching similar tasks, group by cognitive context type (communication, financial, scheduling) rather than by chronological arrival order to minimize context-switching overhead.
When This Fires
- When sitting down to process a queue of accumulated tasks (email inbox, task list, to-do pile)
- When administrative processing blocks feel inefficient despite working steadily
- When you notice frequent mental gear-shifting during task processing
- Complements Flex your dispatch threshold with context (context-adaptive threshold) with the within-block processing strategy
Common Failure Mode
FIFO processing: "I'll just work through these in the order they arrived." This feels orderly but produces maximum context switching. The first-arrived task is a Slack reply, the second is an expense report, the third is another Slack reply — you switch from communication to financial to communication, loading and unloading contexts unnecessarily.
The Protocol
(1) Before processing a batch of tasks, sort them into cognitive context categories: Communication (emails, messages, calls), Financial (invoices, expenses, budgets), Scheduling (calendar, planning, coordination), Administrative (filing, organizing, updating). (2) Process all tasks within one category before moving to the next. (3) Within each category, process in any order — the context is already loaded, so sequencing doesn't matter much. (4) If a task doesn't fit neatly into a category, assign it to the closest one. The categories are for reducing context switches, not for perfect classification. (5) Notice the efficiency difference: same number of tasks, less elapsed time, less cognitive fatigue from switching.