3 ms·

Whenever I try this approach, I end up spending most of the day on meaningless 5 minute tasks and replies to communications. No real work ever gets done. My mo

by Swizec 10y ago

Whenever I try this approach, I end up spending most of the day on meaningless 5 minute tasks and replies to communications. No real work ever gets done. My most productive days are when all 5min tasks are ignored until the last possible moment when their importance grows so much that they must be done. 90% of them turn out to not need doing at all. As a result many say I'm among the most prolific people they know, and I am nobody's idea of "who to call in emergency". ymmv

Jtsummers 10y ago
You still need to put the "5 minute tasks" into a priority queue. Of course if you only prioritize by time to completion long running tasks will rarely, if ever, get done. If it takes 5 minutes, but doesn't need to be done for a month, record the actual deadline and put it in a queue. When you need a break from more laborious or longer running tasks, check that queue of short tasks (prioritized by deadline) for things you can do right now to fill out the next few minutes before ducking out for lunch or whatever. I mean, we don't do this with our OS schedulers? Why would we use a dogmatic "shortest task first" approach for everything else?
- Swizec 10y ago
  > Why would we use a dogmatic "shortest task first" approach for everything else? Because that's what the GTD mantra says? "If it takes less than 5 minutes, just do it immediately" I'm pointing out why in my experience that mantra doesn't work. And I've never read the actual book, so it's very likely I'm taking the mantra too literally and that's why it doesn't work.
  - Jtsummers 10y ago
    Having read the book recently (within the past couple years) it also has a portion near the beginning describing GTD as a toolkit more than a system proper (probably me paraphrasing, but not treating it as dogma is part of it). Take what works and mold it for your own practice. It's not dogma, mistaking the text for dogma is how we ended up with Agile consultants. Even if you do treat that as a mantra, another part of GTD is prioritization. If you aren't getting your real obligations done because of all these 5-minute tasks, then you're not prioritizing properly. http://gettingthingsdone.com/fivesteps/ http://gettingthingsdone.com/fivesteps/ That's a good distillation of the concept. The idea of doing the quick stuff immediately is to prevent a massive backlog later that drains you even more. Even things like checking your email can be done less frequently to prevent unnecessary context switches. Check your email 2-5 times a day instead of leaving it open all the time. When you open it and see a bunch of short tasks, do them or schedule them (with a preference to doing to prevent that accidental backlog), then resume your work. If it's taken you 30 minutes (or some arbitrary, personal limit), switch back to your main tasks and get back to the email again later.

by Swizec 10y ago

Jtsummers 10y ago

You still need to put the "5 minute tasks" into a priority queue. Of course if you only prioritize by time to completion long running tasks will rarely, if ever, get done. If it takes 5 minutes, but doesn't need to be done for a month, record the actual deadline and put it in a queue. When you need a break from more laborious or longer running tasks, check that queue of short tasks (prioritized by deadline) for things you can do right now to fill out the next few minutes before ducking out for lunch or whatever. I mean, we don't do this with our OS schedulers? Why would we use a dogmatic "shortest task first" approach for everything else?

Swizec 10y ago
> Why would we use a dogmatic "shortest task first" approach for everything else? Because that's what the GTD mantra says? "If it takes less than 5 minutes, just do it immediately" I'm pointing out why in my experience that mantra doesn't work. And I've never read the actual book, so it's very likely I'm taking the mantra too literally and that's why it doesn't work.
- Jtsummers 10y ago
  Having read the book recently (within the past couple years) it also has a portion near the beginning describing GTD as a toolkit more than a system proper (probably me paraphrasing, but not treating it as dogma is part of it). Take what works and mold it for your own practice. It's not dogma, mistaking the text for dogma is how we ended up with Agile consultants. Even if you do treat that as a mantra, another part of GTD is prioritization. If you aren't getting your real obligations done because of all these 5-minute tasks, then you're not prioritizing properly. http://gettingthingsdone.com/fivesteps/ http://gettingthingsdone.com/fivesteps/ That's a good distillation of the concept. The idea of doing the quick stuff immediately is to prevent a massive backlog later that drains you even more. Even things like checking your email can be done less frequently to prevent unnecessary context switches. Check your email 2-5 times a day instead of leaving it open all the time. When you open it and see a bunch of short tasks, do them or schedule them (with a preference to doing to prevent that accidental backlog), then resume your work. If it's taken you 30 minutes (or some arbitrary, personal limit), switch back to your main tasks and get back to the email again later.