Bastien Guerry <b...@gnu.org> writes: > I've finally found some time to describe my Org workflow: > https://bzg.fr/en/the-zen-of-task-management-with-org/
Thank you for sharing this! It seems like reducing the amount of loose TODO tasks is an important part: > * Every week I check the TODO and WAIT tasks that do not appear in my > calendar. > This last step, processing TODO items without SCHEDULED or DEADLINE, is > particularly important: it took me a long time to realise that my discomfort > with my Org setup came from not knowing whether I could forget a task. I hear the same sentiment throughout this thread by Ihor and Bob, that it's undesirable to have many TODO items that just lay around for a long time. I was wondering how you (and others) would then look at the following scenario: I'm working on a project (master's thesis) with a clear scope and a clear (but large) list of TODOs. Some of these are actionable right now (NEXT?), but many are actionable only in the future (ie, "Work on presentation"). This means that I now have 119 TODO (or WAIT) items without a scheduled date, which seems antithetical to the workflow you described above. I find it challenging to work out a method of consolidating a big project like this with having few TODOs open. Do you have any thoughts on this?
