Batch small tasks to completion before starting large ones

Clear the small, quick tasks from your queue before starting a large focused task — not after.

Why it works

Switching from a large, unfinished task to handle a small task creates residue on the large task. Reversing the sequence — completing small tasks first, then entering the large task — means the large task begins with a clean slate rather than accumulated residue. This also exploits the Zeigarnik mechanism inversely: completing small tasks closes their loops, preventing them from intruding during large-task focus.

How to do it

1. At the start of a focus session, spend 10–15 minutes clearing any quick tasks (under 5 minutes) that are nagging.
2. Once cleared, enter the large focused task with nothing small outstanding.
3. If a small task arises during the large-task block, write it down and defer — don’t switch.
4. Process the deferred small tasks in a dedicated batch after the large task.

Evidence

Task-completion and closure effects (Zeigarnik, Masicampo & Baumeister) support completing small tasks before starting large ones as a residue-reduction strategy. It is a practical derivation of the core residue mechanism rather than a directly studied intervention. (mechanistic)

This strategy requires knowing which tasks are small enough to clear quickly. Misjudging a "small" task as large consumes the focus block on preamble rather than the main task.

Common mistake

Starting the large task first and then "quickly handling" small tasks that arise — each handle generates residue that degrades the rest of the large-task session.