Categorize tasks by cognitive mode, not by topic

Group tasks by the type of thinking they require — not just by project — to minimize the mental gear-changing between batches.

Why it works

Different task types activate different prefrontal and attentional circuits: analytic writing uses sequential linguistic processing; visual design uses spatial processing; email uses social cognition and rapid shifting. Batching by topic but mixing modes (e.g., writing a report email alongside composing a proposal) still imposes switching costs. Batching by cognitive mode — all generative writing together, all reviewing together — maximizes within-batch coherence.

How to do it

1. List every task type in your week and label its primary cognitive mode: "generate" (creating from scratch), "review" (evaluating existing work), "communicate" (responding to people), "admin" (low-cognition logistics).
2. Assign each mode to a dedicated time window rather than mixing modes within a block.
3. When a new task appears, sort it into a mode category before scheduling it.
4. After two weeks, notice which mode transitions feel most costly — those are the switches worth protecting most.

Evidence

Task-switching research consistently shows that switching between tasks requiring different response sets imposes a performance cost beyond the mechanics of physical switching — a "task-set reconfiguration" process that takes time even when people feel ready. (observational)

Task-switching lab studies use simple, controlled tasks; the magnitude of switching costs in real knowledge work varies by task complexity and individual.

Sources

• Monsell (2003), task switching review, Trends in Cognitive Sciences

Common mistake

Batching by project label ("all the marketing work") while still mixing cognitive modes within the batch, which preserves most of the switching cost the batch was supposed to eliminate.