The two-minute rule for email, adapted from GTD

David Allen's Getting Things Done gives one rule that has outlived the rest of the system: if a task takes less than two minutes, do it immediately instead of writing it down.

Applied to email, this is one of the highest-leverage habits you can build. It is also one of the most misapplied, because email has a scale problem that a paper to-do list never had.

Why the rule works for email specifically

GTD's two-minute rule exists to avoid a specific waste: the overhead of tracking a task is often larger than the task itself. Writing “reply yes to Sarah” on a list, reviewing the list, finding the item, and doing it later costs more total time than just replying now.

Email is the purest case for this. Most messages that land in your inbox are not projects. They are a yes, a no, a confirmation, a forward, a one-line answer. The task and the medium are the same object: the email is both the request and the place you answer it.

So the two-minute rule maps almost exactly:

• Can you answer in two minutes? Answer now, in the inbox, and archive.
• Can you not? Get it out of the inbox with a plan (snooze, delegate, or move to a real task list). Do not leave it sitting.

Where it breaks down for email

GTD was built around a stable stream of discrete tasks. Email is not that. Three ways the rule breaks if you apply it without adjustment.

Volume distorts the two minutes. If you get 150 emails a day and 40 percent qualify as “two minutes,” that is still nearly an hour of two-minute tasks. The rule tells you to do them immediately, which means your whole day becomes reactive. At scale, you need to batch the two-minute replies into a block, not respond to each one as it lands.

Two minutes to read is not two minutes to answer well. A short question can still deserve a considered answer. “Are you free to talk pricing?” reads in five seconds but might need you to check your calendar and think about how to frame the conversation. Treating every short email as a two-minute task produces worse replies, not faster ones.

Threads change category mid-conversation. An email that started as a two-minute yes/no can turn into a real negotiation three replies later. The rule has no mechanism for re-evaluating a thread once it is in motion. You have to notice the shift yourself.

The adapted version

Use the two-minute rule as a filter, not a trigger. At triage time, ask: is this genuinely two minutes of typing, with no research and no decision required? If yes, answer it in that triage block. If it only looks short, treat it like real work and give it a real slot.

This is the version that scales:

1. Sort your inbox before reading anything closely (subject line and sender only).
2. Batch the true two-minute replies into one block, not scattered through the day.
3. Anything that needs thought, even if it reads short, gets snoozed to a dedicated slot with a note on what decision it actually needs.
4. Re-check threads that escalate. If reply three turns a yes/no into a negotiation, pull it out of the fast lane.

How STAMP supports this

STAMP tags each thread with the kind of response it needs before you open it, so you are not guessing whether something is a real two-minute item or a disguised project. Urgency scoring separates the threads that need attention today from the ones that can wait, which makes batching the quick replies practical instead of a hope.

Snooze then handles the escalated threads: you push a thread to a dedicated slot with a note on the actual decision required, so it does not get answered half-thought-out just because it originally looked short.

What to try this week

For one day, before answering anything, ask “is this actually two minutes, or does it just look like it.” Answer the true two-minute ones in a batch at a fixed time. Snooze the rest with a note. See how much of your “quick reply” time was really quick.

Fast when it should be, slow when it should be. hello@stamp.email