The rule is almost embarrassing in its simplicity: if a task takes less than two minutes, do it now. Don't write it down. Don't add it to a list. Don't schedule it. Just do it, immediately, and move on.
I first encountered this in David Allen's Getting Things Done, and I dismissed it for years as too obvious to matter. Then, in a fit of experimental curiosity, I tried tracking it for 90 days. I logged every two-minute task I either did immediately or deferred, and I logged the cost of deferral. The results changed my mind about the rule entirely. It is not obvious. It is quietly powerful, and most of its power is invisible until you measure it.
The Hidden Cost of Deferral
Here's what I found by tracking. Over 90 days, I encountered an average of 11 "two-minute tasks" per day — reply to a quick email, put the dish in the dishwasher, file the receipt, answer the Slack message, pay the parking ticket. Small things. Individually trivial.
When I deferred them — added them to a list, saved them for later — each one carried a hidden cost that I'd never accounted for:
- Logging cost: ~20 seconds to write it down or add it to a system.
- Review cost: ~5 seconds each time I later saw it on the list and didn't do it.
- Switching cost: the mental residue of knowing it's still pending.
- Re-contextualizing cost: when I finally did it, I had to reload the context — remember what the email was about, find the receipt, reopen the ticket.
By my rough tracking, a deferred two-minute task actually consumed, on average, 4–5 minutes of total time when you added up all the touchpoints. The task itself took 90 seconds. The deferral added 3 minutes of overhead. I was paying a 300% tax to avoid 90 seconds of effort.
"I was paying a 300% tax to avoid 90 seconds of effort."
What Changed When I Followed the Rule
For the second half of the 90-day experiment, I committed to the rule strictly. If I noticed a sub-two-minute task, I did it immediately, no exceptions. Three things happened:
My task list shrank dramatically
Within two weeks, my active task list went from ~45 items to ~18. Most of what had been on it were small tasks I'd been deferring. Once I started doing them on contact, they stopped accumulating. The list became — for the first time — a list of things that actually required dedicated time, not a graveyard of tiny procrastinations.
My background anxiety dropped
This was the surprise. I hadn't realized how much low-level mental noise came from the accumulated weight of small undone things. The unpaid parking ticket. The unreturned text. The form I needed to fill out. Each was trivial. Together, they were a constant hum of "something's not done." When I started handling them on contact, the hum went quiet. I felt lighter in a way I couldn't attribute to any single completed task, because it wasn't any single task. It was the absence of the accumulation.
I got better at estimating "two minutes"
Early on, I frequently misjudged — a "two-minute" email turned into a 15-minute thread. By week three, my calibration improved. I learned which tasks were genuinely quick and which only felt quick because I was underestimating the reply. This calibration is itself a skill, and it only develops with practice.
The Important Boundary
The two-minute rule has one critical boundary that most people get wrong: it applies to tasks, not to projects. "Reply to the email" is a task. "Deal with the situation the email describes" might be a project. The rule says: reply now. It does not say: solve the entire problem now.
This distinction matters because the most common failure mode is using the two-minute rule as an excuse to avoid deep work. You spend an hour doing two-minute tasks and feel productive, but you've actually been avoiding the one important thing that required an hour of focused attention. The rule is for the small stuff. It exists to clear the small stuff so you can get to the big stuff, not to replace it.
The fix is sequencing: do your deep work first, when your attention is freshest. Let the two-minute rule handle the small stuff that arises during the day, in the gaps. The rule is a maintenance system, not a priority system.
The Compound Effect
Over 90 days, by my tracking, following the two-minute rule saved me roughly 45 minutes per day in deferral overhead and list maintenance. That's 67 hours over the experiment — nearly two full work weeks, reclaimed not by working harder but by not deferring things that were already quick.
The two-minute rule doesn't feel transformative because no single instance of it is. Eleven times a day, you do a small thing instead of writing it down. That's it. But the compound effect — on your list, your mental noise, your actual available time — is disproportionate to the effort. The smallest rule in productivity might also be the highest-leverage one. I wish I'd taken it seriously a decade earlier.
This article is part of DaveLog's Habit Systems series. The two-minute rule has been my default for 14 months now. The task list has stayed short.