2 ms·
Something I've found with GTD is something that's somewhat alluded to in the book. Granted I don't remember the book outright (perhaps I could do with another r
by Karunamon 14y ago
Something I've found with GTD is something that's somewhat alluded to in the book. Granted I don't remember the book outright (perhaps I could do with another reread...), but the gist is that if you're having trouble with a "thing" on your list, you just need to reduce that "thing" down more because it's too broadly scoped as stated.
Instead of "work singlemindedly and with complete focus on MyNewWebApp", perhaps "Write user authentication module for MyNewWebApp" or even "Get basic username/password authentication working for etc."
Just about anything and everything can be broken down this way; in fact I struggle to imagine something that is incompatible with this! The author of this piece even fails to give any examples of what he means by something that couldn't be broken down.
The other thing is that GTD is a framework. You can follow the way the book tells you to do it to the letter, but then you're missing out. Start with the book, add a little, take a little, mix in whatever works for you. Once you've got the foundation, improvements will come naturally. I'm doing a little GTD mixed in with pomodoro right now and it works incredibly well for keeping my ADD-addled mind in check.
- SatvikBeri 14y agoJust about anything and everything can be broken down this way; in fact I struggle to imagine something that is incompatible with this! The author of this piece even fails to give any examples of what he means by something that couldn't be broken down. Any chunk of work that pushes the limits of your brainpower is hard to break down into pieces. For example, coming up with a Mathematical proof. You might be able to break the problem down to some extent, but there's a lot of time spent just thinking, and it's very difficult to predict how long solving a problem will take.