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
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
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: (Score:2)
One other comment: I believe the common wisdom is not to select tasks based on duration (quick tasks) although it's tempting. The recommendation I've heard is to keep your list pri
Re:The list isn't the problem (Score:1)
The subtlety I've found is that once tasks are on a list, then importance and urgency is relevant, but when a new task comes up, if the time to just do it is not much longer than the time to put it into the "system", then it's worth just doing it then. A couple minutes seems to be the rule.
The problem I've found with prioritization is that my priorities shift too rapidly due to external, client factors and therefore the energy to update priorities on a list is just a frictional loss. People with more stability in their priorities might feel otherwise, of course.
Reply to This
Parent