Batch tasks by cognitive context (communication, financial, scheduling), not by arrival order — minimize context-switching within processing blocks

Why This Is a Rule

Processing tasks in chronological order (first in, first out) seems fair and simple but maximizes context-switching: email reply, then expense report, then calendar invite, then Slack message, then invoice review, then another email. Each task requires loading a different cognitive context — communication mode, financial mode, scheduling mode, communication again, financial again. Six context switches for six tasks.

Grouping by cognitive context type — all communication tasks together, all financial tasks together, all scheduling tasks together — reduces context switches from one-per-task to one-per-category. Process all emails and messages in one batch (communication context loaded once), then all expense and invoice items (financial context loaded once), then all scheduling and calendar tasks (scheduling context loaded once). Six tasks, three context switches instead of six.

The efficiency gain comes from context-loading being expensive relative to within-context task completion. Loading the "communication" context (opening email, getting into response mode, calibrating tone) takes 2-3 minutes. Once loaded, each additional communication task takes only its execution time. Processing five emails sequentially within one communication batch takes 15 minutes. Processing five emails interleaved with other task types takes 25 minutes because the communication context is loaded and unloaded five times instead of once.

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: ~1 minute during fragmented days, ~5 minutes during dedicated admin blocks (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.