The two-minute rule has a limit nobody quotes
by Andreas Tissen · · updated
Twenty two-minute jobs is forty minutes of work and about two hours of day, because each one lands in the middle of something else and the something else has to be picked back up. That is how a morning disappears while every task on it was inside the rule.
The rule itself is correct: if a thing takes less than two minutes, doing it now costs less than filing it, tracking it and returning to it. Nobody quotes the limit, so here it is: the rule is for processing, not for working.
When it applies and when it is a trap
It applies while you are emptying an inbox. You are already in switch-mode, going item by item, and doing the small thing is genuinely cheaper than routing it.
It does not apply while you are doing focused work. There, a two-minute job costs two minutes plus the re-entry, and re-entry after an interruption is measured in tens of minutes, not seconds. During deep work the correct move for a two-minute job is the opposite of the rule: write it down.
Same rule, opposite answers, decided entirely by which mode you are in.
The practical version
Two lines, and they fit in any system:
- In the inbox: do it, if under two minutes.
- Anywhere else: capture it, always.
The second line is what makes the first safe. If capture is expensive, you will do the small thing to avoid the friction of writing it down, and lose your focus two minutes at a time. If capture is one keystroke at the top of your outline, or an email to your inbox bullet, writing it down is the cheaper move every time.
The other limit: two minutes is not the real test
The honest test is not duration, it is whether it needs a decision. A two-minute job that requires choosing between two suppliers is not a two-minute job; it is a decision with a two-minute execution attached, and decisions belong in the clarify step where you are thinking rather than processing.
Which is why the inbox rule works best in this order: is this a decision? If not, and it is under two minutes, do it.
What an agent changes here
It moves the boundary. A number of the small jobs that used to be worth doing immediately are now worth handing over: look this up, draft that reply, file these four captures. The two options become three: do it, delegate it, or capture it. The delegate list fills up fastest.
This is the honest reason the inbox pattern matters more than it used to: what you can hand over has grown, so the list of things you must interrupt yourself for has shrunk.
Try the smaller version
For one week, apply the rule only while emptying your inbox, and capture everything that appears during focused work. Count how many captures you make. That number is how many interruptions you were previously calling productivity.
The week fits in three branches: an inbox where the rule applies, a capture list for focus hours, and the Friday count. Open the template, press "Show in my Pando", and start counting.