Logical, yes. But logical doesn't always make for good practices. It's logical to keep things in your head, too.
:-)
:-)
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!
|
|
FAQ | Members List | Calendar | Today's Posts | Search |
Project 1st, NA 2nd? | Thread Tools | Search this Thread | Display Modes |
|
Member
2011-12-01, 01:15 AM
Logical, yes. But logical doesn't always make for good practices. It's logical to keep things in your head, too.
:-)
Post 1
|
Member
2011-12-01, 01:59 AM
I have a related request. I would like to be able to see the project field on the left in context mode. This would make for a cleaner display when I sort NAs by project.
Post 2
|
Member
2011-12-01, 02:04 AM
One could say that the best practice would be to not use a capture tool to apply the process stage of GTD ;) Seriously though, that is what we are discussing here. In GTD the collection process occurs before the successful outcome/next action phase of the workflow, and the Quick Entry command is a collection process.
Post 3
|
Member
2011-12-01, 04:26 AM
Quote:
I agree (see, I'm not that contrarian :) This is collection, not process, and the process phase is explicitly meant to elicit successful outcome + next physical action. I do frequently hit the keyboard shortcut, enter just a few words in the first field, then Command+K it away. On the other hand, sometimes I know the successful outcome but not the next action. But then the successful outcome tends to end up in the next action field. And in my training + coaching practice I notice that depending on whether you tend towards micromanager or crazymaker, you tend to omit either successful outcome or the physical next action. What would probably work even better (for me, at least, being of the micromanagement kind) would be: 1. having a free format quick entry form (possibly enhanced with the same parsing mechanism as the Mail-to-Omnifocus thingie so that you can enter either "Mom" or "Call Mom for recipe > Make chocolate chip cookies @Calls-Private #tomorrow $1h") 2. An inbox-processing mode, whereby one by one OF would present each item on its own (I tend to get sidetracked if I see more than one) and ask me to define a successful outcome, a physical next action, and a context. Hm. Would #2 be scriptable, I wonder? // later Bleh. I just learned I can dispense with #1 headache here by using Alfred's entry box + this little script. Still looking for #2 though. Last edited by raxtor; 2011-12-01 at 04:38 AM..
Post 4
|
Looks like we have an existing request for the ability to re-order the columns; feedback from this thread has been added to that item in the development database. Thanks, folks!
Post 5
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sidebar small after switching from project to context to project | jochen | OmniFocus 1 for Mac | 3 | 2010-09-17 11:00 PM |
Stalled project when project is sequential and first action is repeating | SpiralOcean | OmniFocus 1 for Mac | 2 | 2008-01-02 03:07 PM |
Cleanup not assigning project-less action to my 'single actions' project | bongoman | OmniFocus 1 for Mac | 0 | 2007-12-11 02:04 PM |
Single tasks as project groups & context vs project group | eatmytag | OmniFocus 1 for Mac | 48 | 2007-08-17 11:07 AM |
Request: Create project in Action > Project Inspector | omnibob | OmniFocus 1 for Mac | 6 | 2007-07-21 01:02 PM |