Agree with this so much. So many people view Getting Things Done as an infomercially, buzzwordy system when it's really just a set of "best practices" for every

Agree with this so much. So many people view Getting Things Done as an infomercially, buzzwordy system when it's really just a set of "best practices" for everyday thinking. You can consider it and take away whatever works for you, and it's almost guaranteed that you'll find at least one thing that improves the way you think and work every day. In contrast, Jeff's advice is the only way he found to work effectively and, he reasons, the only way anyone in a similar profession can work effectively. In reality, you may think that having next action lists and reviews are "productivity porn" and wasted time, while others may think that they help keep your mind clear and focused. You're going to do that work of evaluating priorities and deciding what to work on anyway, so there's no harm in being honest about it, isolating it, and minimizing the context switches. There's also no harm in going Jeff's route and doing "lazy evaluation" on that meta-work, only deciding when you need to. We all think and remember differently, so the debate will never truly end. Personally, I'm in favor of advocating the best hacks and systems that people have found, preferably with grains of salt and low buzzword count, and letting people figure out what works best for them. As coders, we're used to the luxury of strong opinions and relatively hard evidence, but that's not something that will happen here.