NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
The list isn't the problem (Score:1)
I highly, highly recommend that you read David Allen's Getting Things Done. Among other things, it clarifies the purpose of keeping lists (getting "stuff" out of your brain to free your brain to be productive), gives a process for managing your lists, and has useful advice on making sure your lists are actionable (keeping it granular to just the "next action").
Moreover, he describes himself as the laziest person in the world and his system as the simplest thing that could work -- in other words, it's des
Re:The list isn't the problem (Score:2)
I've read GTD and agree to the principles. I even have some GTD posters on my office walls. It's just that I still haven't gotten round to fully implementing it (so I'm still stuck in a world where I forget to do stuff).
Could you gives the rest of us some details about those 12 files? Do you split by priority, scope (home, work), size (tasks vs. projects), etc? How are those files organized?
Reply to This
Parent
Re: (Score:1)
I, too, have a lot of leakage in my system -- don't let it be a barrier. I'm not good at finding regular time for weekly reviews and emptying my head onto paper. But whenever I do, I kick myself for not doing it more often. Several of the practices work well individually, though I do think they work better collectively.
I can describe my system a bit more, but it's an evolving thing, not static, and it's based on some of the particular contexts I deal with. For example, I travel a lot to clients' offic