I have known a lot of people who swear by the Getting Things Done methodology. I have heard that there is even a course on how this works taught at my company! I work in tech, and the reason why so many people in this industry specifically have gravitated towards this method with such zealous dedication1 is a lot more clear after having read the book.
The method essentially requires that you gather all of your tasks in a single place and assess everything on your list with a flow chart. The first thing you wrote down is the first thing you do, then the next, then the next, without prioritization until it is all done. If it is a big task, it is a project that is broken into smaller tasks, and there’s an emphasis on figuring out what the next action is and just, well, getting things done.2
It’s a process that’s fairly standardized and explained with just enough vagueness that it could, in theory, be applied to anything. But also enough complication that I think it draws a certain type of person who is also very drawn to software development. And I think the fanbase of this methodology might be part of the reason I have a weird feeling about it.
I think it’s fine as a starting point, but it is a method that should be adapted and adjusted once you have the initial panic of needing some place to start settled. Getting all of your tasks in one place is a good thing, as is taking time to look them over and assess whether you have to do this now or if you can delegate or get rid of it all together. As a whole, it’s fine for if you have a fairly straightforward life, or if you don’t have a need to get into a flow or have interest-based attention, or even have a lot of interest in doing anything you’re working on. But life my life is a bit more complicated and nuanced, so I don’t think I’ll be taking this method on.