emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Jones <mlists@pmade.com>
To: emacs-orgmode@gnu.org
Subject: Re: Workflow Ideas/questions
Date: Wed, 25 Mar 2009 20:42:33 -0600	[thread overview]
Message-ID: <m2iqlxxaw6.fsf@pmade.com> (raw)
In-Reply-To: 278452667f8c27630c57917c33690e13.squirrel@mail.thedarktrumpet.com

"David Thole" <dthole@gmail.com> writes:
> I was thinking a bit about my workflow with org-mode, and I'm thinking
> that I should change up a bit of how I'm doing stuff.  Basically what I do
> now is use org-mode for my GTD stuff (that is, ticket management, notes
> about tickets, etc), and then use muse mode for other stuff.

I'm not sure I have any specific recommendations for you, but thought
I'd share my setup, and maybe it will help somehow.

I use Muse for writing documents and blog articles, and Org to manage my
entire life a la GTD.  I have my workflow split into the following

| File           | Purpose                                              |
| checklists.org | Recuring tasks (pay phone bill), trigger lists, etc. |
| projects.org   | Projects with concrete action lists                  |
| review.org     | Information that I may need to review later, notes   |
| someday.org    | Projects that I might do someday, but not right now  |

I use top-level headings in the projects.org file to split my projects
into categories:

* Personal
** Some Personal Project
*** NEXT Next action
* Business
** Some Business Project
*** NEXT Next action

I also have one org file for each one of my clients.  These client files
have top-level headings that mirror my main files, for example:

* Notes / Review
* Checklists
* Someday / Maybe
* Projects

There is a file-level tag of :project: in the projects.org file, and in
the client files I tag the Projects heading with :project:.

Relevant org variables:

 org-stuck-projects '("+LEVEL=2+project|+LEVEL=3+subproject" ("NEXT" "PENDING") ("single") "")

 '(("d" "Daily Agenda"
    ((agenda ""
             ((org-agenda-todo-keyword-format "")
              (org-agenda-remove-tags t)))
     (tags "LEVEL=2+goals"
           ((org-agenda-remove-tags t)
            (org-agenda-prefix-format "  ")
           (org-agenda-todo-keyword-format "")))
     (todo "NEXT" 
           ((org-agenda-sorting-strategy '(tag-up))
            (org-agenda-show-inherited-tags nil)
            (org-agenda-todo-keyword-format "")))
     (todo "PENDING"
           ((org-agenda-todo-keyword-format "")))
     (stuck ""
            ((org-agenda-remove-tags t))))))

I look at the above agenda view several times a day (probably hundreds).
I narrow and widen the focus to specific contexts, and to client tasks
via tags throughout the day to keep from procrastinating.

Honestly, Org is the most import tool in my life.  After years of
playing with GTD and trying to make it work for me, Org finally put
everything into place.


Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US

      parent reply	other threads:[~2009-03-26  2:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 20:51 Workflow Ideas/questions David Thole
2009-03-25 21:18 ` Manish
2009-03-26  2:42 ` Peter Jones [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=m2iqlxxaw6.fsf@pmade.com \
    --to=mlists@pmade.com \
    --cc=emacs-orgmode@gnu.org \


* 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).