Workflows

The Two-Minute Rule in GTD: Why It Works and When It Fails

The two-minute rule in GTD says do it now if it takes under two minutes. Where the rule came from, the friction math behind it, and when it backfires.

By Ege Beşe8 min read

The two-minute rule in GTD is the simplest instruction in David Allen's whole method: if a next action takes under two minutes, do it the moment you clarify it instead of filing it. It survives twenty-five years of productivity-fashion cycles because the math behind it is unglamorous and correct. It also wrecks more mornings than any other rule in the system, because people apply it in the wrong context.

This explainer covers where the rule came from, why the friction math holds, where it backfires, and the voice-capture twist that makes deferring almost as cheap as doing. For the full method the rule lives inside, see Getting Things Done digital.

Overhead flat-lay of a warm-paper desk with a small vintage analog kitchen timer, a single blank index card and a fountain pen, generous empty space.
Two minutes is the line between doing and filing.

Where did the two-minute rule come from?

David Allen introduced the two-minute rule in Getting Things Done in 2001, as part of the clarify step of his five-stage workflow. When you process an inbox item and decide it is actionable, you ask how long the next action takes. If the answer is under two minutes, you do it right there. No filing, no deferring, no list entry.

The context matters. Allen wrote the rule for a bounded pile: a physical inbox tray you sit down to process in a session. Inside that session, doing beats filing for small items, full stop. The rule was never written for an unbounded stream of incoming requests, and most of the confusion about it comes from applying a bounded-pile rule to an unbounded stream.

Why does the two-minute rule work?

The rule works because tracking a task is not free. Every deferred item pays an ongoing tax: the seconds to write it down, the attention to re-read it in every review, the friction of reloading the context when you finally do it. For a 90-second task, the lifetime tracking cost routinely exceeds the cost of doing the thing the moment it shows up.

The friction math, roughly:

  • Doing now: about 90 seconds, once, with full context already loaded.
  • Deferring: 10 to 30 seconds to capture, 5 to 10 seconds per weekly review touch, 20 to 60 seconds to reload context later, plus the 90 seconds you still owe. Total: easily three to five minutes spread across days.

That is the whole argument. The two-minute rule is not a productivity hack; it is an accounting decision. Below the threshold, the ledger favors doing. Above it, deferring wins, because big tasks genuinely need scheduling, preparation, and the right context.

When does the two-minute rule backfire?

The rule backfires when it meets an unbounded stream. Email, chat, and notifications serve plausible two-minute items all day long. A literal reading of the rule means answering every small ping the moment it arrives, which turns the morning reactive: you spend your sharpest hours clearing other people's small items and start your own real work at noon with a depleted attention budget.

The other failure mode is stealth procrastination. Doing two-minute items feels productive, and that feeling makes the rule a comfortable hiding place from the one hard thing on the list. An hour of busywork later, the inbox is cleaner and the important project is untouched. If you recognize that pattern, a structured focus block is the corrective: our guide on the focus timer for knowledge workers covers the drift-free version of that ritual.

What is the voice-capture twist on the two-minute rule?

Voice capture changes the deferral side of the equation. Deferring a task used to cost 30 seconds or more: unlock the phone, find the app, type the item, file it. Speaking the same item into a capture tool takes under ten seconds, hands-free, and modern AI task managers file it into the right project with the next step written. The deferral cost drops low enough that the two-minute rule almost never needs to interrupt anything.

That reframes the rule's role in 2026. You can be strict about context: during a focus block, capture everything and do nothing, because capture costs seconds. During triage, run the rule aggressively, because the pile is bounded and throughput is the goal. The rule gets both safer and more useful when the capture side is nearly free. Our pillar on AI task managers covers how different tools handle that capture-to-clarify loop.

How does the two-minute rule fit the weekly review?

The weekly review is where the two-minute rule earns its keep at scale. The review's clear phase is a bounded processing session by definition: every capture point, emptied top to bottom, with the rule applied to each small item. A practiced reviewer clears 15 to 25 small items in under ten minutes this way, items that would otherwise have spent the week taxing attention.

The full walkthrough is in our GTD weekly review guide. The short version: clear phase first, rule on, then the slower current and creative phases with the rule off. Sequence is the difference between a review that finishes in 40 minutes and one that sprawls across an afternoon.

FAQ

What is the two-minute rule in GTD?

The two-minute rule is David Allen's instruction from Getting Things Done: when you are clarifying an item and the next action takes less than two minutes, do it immediately instead of filing it onto a list. The rule exists because the overhead of tracking a task exceeds the cost of doing it when the task is that small.

Where did the two-minute rule come from?

David Allen introduced it in the 2001 book Getting Things Done as part of the clarify step of his five-stage workflow. James Clear later popularized a different two-minute rule in Atomic Habits, where you scale a new habit down to a two-minute starting version. Same name, different mechanics: Allen's rule is about throughput, Clear's is about starting.

Does the two-minute rule actually work?

Yes, inside a processing session. Doing a 90-second task on the spot costs 90 seconds. Filing it costs more: capture, track, review weekly, re-read, and eventually do it anyway. The rule fails when people apply it outside processing, answering every small ping the moment it arrives, which turns the day reactive instead of deliberate.

When does the two-minute rule backfire?

When it meets an unbounded stream. Email and chat serve two-minute items all day, so a literal reading of the rule keeps you in permanent reaction mode. The rule was written for a bounded pile, a physical inbox you process in a session. Apply it during scheduled triage windows and capture everything else for later instead of doing it on arrival.

Should I use the two-minute rule during deep work?

No. During a focus block, the correct move for any incoming thought is capture, not action. Deferring a task by voice takes under ten seconds, which is cheap enough that the two-minute rule never needs to interrupt a Pomodoro. Save the rule for your triage windows, where throughput is the goal and interruption is free.

References

ShareShare on X

Keep reading