What does it mean that the two-minute rule for small tasks?

If a task takes less than two minutes do it immediately rather than scheduling it — because the overhead of capturing, organizing, and tracking it exceeds the cost of doing it now.

Example: You finish a deep work block and switch to your administrative window. Your task list has twenty-three items. Fourteen of them are genuinely small: confirm a meeting time, rename a file, approve a pull request, reply to a one-line question, update a spreadsheet cell, forward a document. You could review, prioritize, and schedule each of these fourteen items across the week. But the act of scheduling each one — deciding when to do it, tagging it with a context, adding it to a time block, re-reading it when the time block arrives — costs more cognitive overhead than simply doing the thing. You spend forty minutes dispatching all fourteen. Your task list drops to nine items, all of which genuinely require thought. The administrative weight you have been carrying for days evaporates in less than an hour, and you enter your next deep work block with a mind that is noticeably quieter.

Try this: Open your current task list, project board, or backlog. Go through every item and estimate — honestly, without rounding up — how long each one would actually take to complete. Mark every item that falls under two minutes. Now set a timer and dispatch them all, one after another, without pausing to reorder or deliberate. When the timer stops, count how many items you completed and how much total time elapsed. Most people find that twenty to forty percent of their tracked items are sub-two-minute tasks that they have been carrying for days. Notice the cognitive shift after clearing them: the list feels lighter not because fewer things remain, but because the things that remain are the ones that actually deserve your attention.