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
- 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).
- Assign each mode to a dedicated time window rather than mixing modes within a block.
- When a new task appears, sort it into a mode category before scheduling it.
- 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.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Task Batching: Grouping Similar Work to Cut Switching Costs
- Batch email into 2–3 fixed windows per day
Process email in dedicated 20–30 minute windows rather than responding whenever a notification arrives.
- Batch low-stakes decisions to reduce decision fatigue
Group routine decisions into a single weekly slot rather than making each one as it appears.
- Sequence creative tasks before reactive tasks each day
Do generative (creating) work before reactive (responding) work — never the other way around.
- Save admin tasks for your cognitive trough
Assign low-cognition administrative tasks to the time of day when your focus is naturally lowest.
- Create a communication batch protocol for your team
Agree with collaborators on expected response windows so batching doesn’t create perceived unavailability.
- Batch weekly planning into a single review session
Consolidate all task review, prioritization, and scheduling into one weekly session rather than planning continuously throughout the week.
Related concepts
- Deep Work, Made Practical
Focus blocks, attention residue, and the shutdown ritual — with the evidence
- Getting Things Done (GTD), Made Practical
The five steps, the next-action habit, and the science of offloading your mind
- Monotasking, Made Practical
The real cost of task-switching, and how to work one thing at a time