Batch similar tasks

Group same-mode tasks together so you switch contexts less often.

Why it works

Switch cost is largest when the two tasks demand different cognitive sets (different tools, rules, or mindsets). Batching similar work keeps you in one cognitive set across many items, so you pay the reconfiguration cost once instead of repeatedly. The savings are in avoided switches, not in doing each item faster.

How to do it

1. Sort tasks by mode: writing, calls, admin, decisions.
2. Run a block dedicated to one mode rather than interleaving modes.
3. Process small same-type items (emails, approvals) in one sitting instead of as they arrive.

Evidence

Batching follows directly from switch-cost research: fewer between-mode switches means less cumulative reconfiguration cost. The principle is well-grounded mechanistically. (mechanistic)

The underlying switch-cost science is strong; the specific productivity gain from any batching scheme depends on your task mix and is not a fixed number.

Common mistake

Batching by project rather than by cognitive mode, so you still flip between writing, calculating, and deciding within the "batch" and keep paying switch costs.