The only survivor from GTD
I tried to go full GTD once. The whole thing. Capturing, contexts, weekly reviews, the giant master list of everything I could ever care about.
I lasted about three weeks.
What survived was one tiny rule. The two-minute rule. Everything else went in the bin.
The funny part is that this one piece does more for my actual day than any fancy app, PARA system, or color-coded calendar I ever tried to force on my life.
The rule, spelled out like I actually use it
The textbook GTD version is:
If something takes less than two minutes, do it now.
My version is slightly different:
If something takes less than two minutes, and it prevents future friction for me or someone I care about, I do it now.
That extra clause matters. It keeps me from using the rule as an excuse to ping-pong through shallow work all day.
Why the rest of GTD bounced off me
I do not hate GTD. I just do not live like the person it was written for.
I have a weird stack of roles. I ship web experiences for clients. I tinker with weird side projects. I coach baseball. I track training and recovery because my body is basically a lab experiment at this point.
Context lists like @office and @computer make zero sense when the office is my laptop, my kitchen table, or the dugout, depending on the day.
Also, I found the overhead brutal. Capturing everything. Processing everything. Maintaining contexts. Weekly reviews that felt like accounting.
I would spend a whole Saturday morning "getting current" in some app instead of actually doing anything that moved life forward. My brain eventually tagged the whole GTD stack as overhead and I stopped touching it.
The two-minute rule was different. It did not require a new app, a new identity, or a Sunday ceremony. It just sat quietly in my head and made decisions easier.
Where the rule lives in my day
I do not have a timer going. I am not counting seconds. Two minutes is a feeling, not a measurement.
Here are the moments where the rule actually runs my life.
1. The inbox scan I actually tolerate
I do not live in email, but I do pass through it a few times a day.
When I open it, I flick through and mentally tag each thing.
- Under two minutes and important: reply, archive, move on.
- Under two minutes and pointless: unsubscribe, filter, or delete.
- Over two minutes: it goes on a separate list with a verb and a tiny next step.
"Verb and tiny next step" matters here. Not "Redesign client's hero section". Instead I write "Draft alt hero layout idea A".
The result is boring but powerful. My inbox is not a task manager. It is just messages. The actual work lives somewhere else, described clearly.
The two-minute rule is the thing that forces that separation. It stops me from turning every email session into accidental deep work. I respond to the quick ones, log the real work, and leave.
2. Code friction clean-up
Most of my work sits inside a code editor. That is where I notice little annoyances.
- A misnamed component.
- A CSS variable that is obviously wrong.
- A console.log I forgot three commits ago.
Old me would think: "I will refactor this properly later" and then never do it. Because "later" would require a whole mental setup and a dedicated block of time.
Two-minute rule me does this instead:
- If renaming that component and updating imports takes under two minutes, I just do it.
- If deleting the logs and running tests takes under two minutes, I just do it.
- If it clearly needs more time, I drop a quick comment or a tiny TODO and move on.
This is not about "always keep your codebase pristine". I do not live in some clean-architecture fantasy.
It is about removing small future landmines immediately, while momentum is still there. Because those landmines show up later when I am trying to actually ship something.
3. Life admin that used to rot in the corner
Everyone has a life-admin pile. Mine used to live as a stack of envelopes near the door and a few innocent looking tabs in Safari.
Things like:
- Reply to the club about training slots.
- Send a photo for some registration thing.
- Sign a document that has already been sitting there for a week.
The two-minute rule turned into a simple habit here.
Every time I notice one of these, I ask myself a blunt question.
Am I really so busy I cannot spare ninety seconds for this?
Ninety percent of the time, the honest answer is no. So I do it. Right there. Right then. No ceremony. No task manager. Just done.
This matters more than it looks. Those tiny items carry a weird cognitive load. It is not the task that drains you. It is the constant background reminder that you are the type of person who does not return simple forms.
Where I deliberately ignore the rule
The two-minute rule can wreck your focus if you apply it like a zealot. It can turn your day into a Twitch stream of micro-tasks.
I learned this the hard way. I once tried to keep a two-minute-clean desk at all times. Any stray paper, cable, or sticky note triggered the rule.
I got a tidy desk and a shattered attention span.
So now I have a few clear carve-outs.
1. Deep work blocks are a no-fly zone
When I sit down for an actual deep work block, I draw a hard line. No two-minute tasks unless something is literally blocking my current work.
If I am in the middle of building a complex animation or debugging some weird layout glitch, email does not matter. Slack does not matter. The laundry can unionize for all I care.
During those blocks, the two-minute rule is scoped only to the current task.
- Rename the variable so the next line makes sense? Yes, do it.
- Extract a tiny helper while I am here? Sure, if it is quick.
- Refactor the whole module? No. That is a different session.
This keeps the rule from expanding sideways into a productivity trap. I want it vertical. Only down into the current thing I am doing.
2. Notifications do not win just because they are short
Most notifications are technically under two minutes to respond to. That does not mean they deserve the front row of my brain.
I keep notifications aggressively trimmed. No pop-ups from email. No badges screaming in the dock. Messaging apps are pull, not push.
The two-minute rule only applies when I have chosen to look at a channel. Not when the channel waves at me from the corner like a needy Tamagotchi.
3. "Under two minutes" is about doing, not deciding
This one took me a while.
I used to burn ten minutes deciding whether something was a two-minute task. Which sort of defeats the purpose.
Now I use a simple heuristic.
- If I can see the whole task in my head, with no branches, it probably fits.
- If I catch myself thinking "and then maybe I could also" it does not fit.
That tiny distinction keeps me honest. The two-minute rule is for doing, not for planning more work while pretending I am being efficient.
Why this one rule stuck when the rest did not
Most productivity systems ask you to reorganize your whole life. New app. New tags. New review rituals. A new identity as a "system person".
The two-minute rule did not ask for any of that. It behaved more like a patch for my existing OS.
Here is why I think it survived.
1. It plays nice with chaos
My days are lumpy. Some blocks are pure maker work. Some are coaching. Some are life admin thrown in the middle because the world refuses to respect my calendar.
The two-minute rule does not care about that mix. It just waits patiently for a decision point, then offers a simple fork.
- Yes, it is small and prevents future friction, do it now.
- No, it is not small, capture it somewhere you trust.
No new UI. No fancy method. Just a mental if-statement I run on the fly.
2. It shrinks the "open loop" tax
GTD talks a lot about open loops. Stuff your brain keeps tracking because you have not parked it somewhere reliable.
For me, the worst open loops were not the big projects. Those are obvious. They get space on the calendar. They get their own notes. They get talked about.
The worst ones were stupidly small.
- "Reply to that parent about Saturday practice."
- "Book physio before that minor ache becomes a major problem."
- "Pay that annoying 23 euro invoice."
The two-minute rule kills those loops before they get a chance to become psychological clutter. It is like mental garbage collection that runs constantly in the background.
3. It respects momentum
Big systems want you to step out of your flow, capture, categorize, and then re-enter.
That works in theory. In practice it feels like stopping a good bike ride because you saw a poster about better cycling posture.
The two-minute rule respects momentum. If you are already looking at the thing, already thinking about the thing, and doing the thing would take less time than describing it, just do it.
No context switch. No ceremony. Back to real work.
How I would use it if I was starting from zero
If I somehow lost all my systems tomorrow and had to rebuild from scratch, I would start with this rule and a basic capture list. Nothing else.
The setup would look like this.
- One place to capture anything that is clearly more than two minutes. Could be a notebook, a plain text file, or a simple app. I would not overthink it.
- A conscious decision that email, messages, and admin only get attention at specific times, not all day.
- The two-minute rule running as a filter whenever I touch those channels or notice a small physical task.
No tags. No contexts. No complex review cycles yet. Just one question, asked repeatedly.
Can I end this in under two minutes?
If yes, I do it now. If no, I write a tiny, concrete next step on the list and move on.
Some concrete examples from last week
To make this less abstract, here is a tiny grab bag from a random week.
- Client asked for a small copy tweak on a landing page. Opening the CMS, changing three words, re-reading, and hitting publish took about ninety seconds. I did it during my email pass instead of creating a ticket.
- My catcher asked if we could move Saturday's bullpen by thirty minutes. I checked the calendar, replied, and immediately updated the shared schedule. Under two minutes. No "remember to update it later" note lurking in my head.
- Noticed a misleading label on a toggled state in a React component. The fix was one line of JSX and a quick test in the browser. I patched it on the spot instead of leaving a TODO.
- Got a letter that needed a signature and a photo of an ID. I used the phone, scanned it, sent the email reply immediately. Envelope went straight into recycling instead of living on the table for a week.
None of these tasks are interesting. That is the point. They are exactly the kind of low-drama stuff that accumulates and quietly drains your attention if you do not swat them early.
Keeping the rule small on purpose
People love turning simple ideas into capital-S Systems. I try very hard not to do that here.
I never track how many two-minute tasks I complete. There is no leaderboard. No automation. No fancy shortcut that pops up a timer every time I touch a keyboard.
The power is in the simplicity.
See a small task. Ask if it really is small. If yes, and if it removes future friction, kill it now. Then go back to the real work that actually matters.
The rest of GTD did not survive contact with my life. This one tiny rule did. That is good enough for me.
Top comments (0)