GTD

The two-minute rule: small tasks, done at the door.

The most portable idea in GTD. Why two minutes is the threshold, where the rule shines in email, and the one way people misuse it.

By Mathias CelisJanuary 6, 20264 min readLast updated July 2026
TL;DR

David Allen's two-minute rule: if an action takes less than two minutes, do it the moment you clarify it, because tracking it would cost more than doing it. It shines during email processing, where quick confirmations and answers get handled on the spot. The misuse: letting two-minute tasks interrupt deep work, where the 23-minute refocus cost dwarfs the task.

Of everything in Getting Things Done, one rule escaped the book and entered general circulation: if it takes less than two minutes, do it now. It's quoted in kitchens and boardrooms by people who couldn't name David Allen. The rule deserves its fame, and it also gets misused in one specific, expensive way worth naming.

The logic of the threshold

Two minutes isn't magic; it's an estimate of overhead. Tracking a task through any system has a cost: writing it down, seeing it on the list repeatedly, re-loading the context later. For a tiny action, that bookkeeping exceeds the action. Below the threshold, deferring is pure waste; above it, deferring pays because the work deserves scheduling. Allen himself says the exact number matters less than having a consistent line.

Where it shines: inside email processing

The rule was born for the clarify step. You're in a processing window, already in deciding mode, and the email asks something answerable in ninety seconds: answer it, archive, next. This is what keeps quick confirmations and short answers from clogging a task list with entries that cost more to track than to do. Applied this way, the rule is a filter that keeps your next-actions list reserved for real work.

The misuse: as an interruption license

Ripped out of processing sessions and applied to every arriving ping, the rule inverts into an interruption engine: "it's only two minutes" becomes the reason to break focus a dozen times a morning. But the two minutes were never the cost; the refocus is, and UC Irvine's research prices that at roughly 23 minutes per interruption. A two-minute task that interrupts deep work is a 25-minute task wearing a disguise.

Inside a processing window, the rule is a filter. Outside one, it's an interruption engine.

The boundary, stated once

Use the rule when you're already in deciding mode: processing email, clearing a note inbox, ending a meeting. Never let it justify entering deciding mode. Batching (the case here) supplies the sessions; the rule makes them fast. And if the tiny-reply category is most of what your two-minute rule handles, that's the category Pidgy drafts automatically, which makes the rule's territory smaller still.

Frequently asked questions

What is the two-minute rule?

From David Allen's Getting Things Done: if an action will take less than two minutes, do it immediately upon deciding what it is. The logic is bookkeeping cost: capturing, tracking, and re-finding a tiny task costs more than the task itself.

Why two minutes and not five or ten?

Two minutes approximates the overhead of tracking a task through a system. Above that, deferring pays; below it, deferring is pure waste. Allen himself notes the exact number matters less than having a consistent threshold.

When should I not use the two-minute rule?

During focused work. The rule belongs inside processing sessions, when you're already in deciding mode. Applied to every ping mid-focus, it becomes an interruption engine, and each interruption costs roughly 23 minutes of refocus (UC Irvine).

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works