emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Rogers <davidandrewrogers@gmail.com>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Overall organization/setup for org mode: Projects and Tasks
Date: Sat, 17 Sep 2011 19:40:55 -0700	[thread overview]
Message-ID: <87wrd6lgi0.fsf@gmail.com> (raw)
In-Reply-To: <CAF-1L2RL8mgMVz4bSmO7vvPYOd5fQ-aWBC2-Gp3b8TygZKb1MQ@mail.gmail.com> (Alan E. Davis's message of "Wed, 14 Sep 2011 10:43:28 -0700")

"Alan E. Davis" <lngndvs@gmail.com> writes:

> --0016364d213773a53a04acea4da9 Content-Type: text/plain; 
> charset=ISO-8859-1 
> I've been using org-mode for a few years.  My agenda is 
> cluttered with tasks that are weeks and even months past due.  I 
> am "this close" to declaring "orgmode bankruptcy" and starting 
> from scratch, except my current setup works so well for other 
> things.   Might still do that, but I want to ask for ideas.

Re. "orgmode bankruptcy":
Don't start your list from scratch; this problem will just happen 
This is not the fault of any agenda system, and would have 
happened anyway. I think the problem likely comes from having a 
significant number of tasks that are mis-categorized and/or 
mis-judged. There are several possible ways that can happen:

(I'm sure I'm not seeing some of the possibilities here... my main 
point is that with these "problem tasks" there's something wrong 
with the task itself, not your reminder system; and furthermore 
that the defective tasks can probably be repaired or rehabilitated 
so that they get done.)

(And clearly, nothing I can say here is unique. It's all been done 
and all been said before, in different ways.)

- Tasks that were never worth doing; toss those ones out 

- Tasks that should never have been yours; either negotiate a way 
  to get 
  them to the proper person, or else decide to do them anyway (and 
  then actually do them!).

- Tasks that were important in the past, but now it's too late 
  (i.e. you 
  judge them to be un-salvageable); toss them out too (but make 
  sure it's REALLY too late before doing so). Failure happens 
  sometimes, and keeping an item on the agenda after it has failed 
  isn't helping anyone.

- Tasks that are turning out to be more difficult than they 
  break them down into parts to be done one at a time, share them, 
  or get someone else to do them.

- Just because a task looks/sounds/feels important, doesn't mean 
  that it 
  is. "What if I simply decided not to do it?" is always a valid 

- Any task that can safely be dropped should be dropped. There 
  always be enough real work to do without inventing more.

The truth is, you have to either do a task or else not do it; and the truth
is, you always have a choice about that.

      parent reply	other threads:[~2011-09-18  2:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 17:43 Alan E. Davis
2011-09-14 18:26 ` Thomas S. Dye
2011-09-14 18:40 ` Russell Adams
2011-09-14 20:00   ` Martyn Jago
2011-09-14 22:50     ` Russell Adams
2011-09-14 18:59 ` Olaf Dietsche
2011-09-14 21:04   ` Christian Moe
2011-09-14 21:49   ` Darlan Cavalcante Moreira
2011-09-17 19:32 ` Max Mikhanosha
2011-09-18 19:22   ` Alan E. Davis
2011-09-18  2:40 ` David Rogers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrd6lgi0.fsf@gmail.com \
    --to=davidandrewrogers@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lngndvs@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).