I think GTD can be dangerous for people who like systems too much; a bit like people who play RPGs because of the rules around bookkeeping of stats and deciding

I think GTD can be dangerous for people who like systems too much; a bit like people who play RPGs because of the rules around bookkeeping of stats and deciding of battles, rather than for the imagined world the bookkeeping keeps honest. I'm highly task-oriented in my work, but mostly it's just a list of lists, maintained in a text file with infinite persistent undo. Every task starts out as a line, gets a few sub-lines when it acquires some definition, and gets broken up into multiple separate tasks if it's too big, or it only gets partially done and other tasks remain. I don't live like that much outside of work (unless there's a specific longer-lived process, like moving house or something), and my process is very light weight. I think GTD starts out too heavy; it would be better done iteratively, starting with something very simple that works 80% of the time, and then adding more if you're so busy that you need the extra process. You could then start reading the book and put it down early on with enough to get by, but still be able to pick it up if you need more.