So, it intrigues me that OmniGroup chose a task-list and a Gantt project view for their OmniPlan application. It’s very easy to see sibling/child/parent relationships in Gantt views. In some ways, producing even a Gantt-Chart fake (structured todo list with fake times), you can see/walk through a project’s progression to completion more clearly. Even though they are painfully structured (not loose in scheduling or linking etc.)- they do allow you to very quickly see the tasks required to complete a project. In the project view, usually I have things organized in such a way that I can see this natural parent/child relationship, but when contexts are used, my brain must remember these things- which seems to go against the basic tenant of GTD. In my current mode of organization, I seem to lose this information, or am required to remember it. I’m just wondering if we’re missing another level of mind-stuffing information here: namely the proper order and relation of tasks. So, I am grateful to D.Allen for his work. I highly value GTD for freeing up my mind (I’ve slacked a bit lately, but I’m getting back on the horse with organization). In GTD words, the context lists would include only “next actions”… not all actions, as kGTD currently is setup. Perhaps context lists should be only current actionable items and not include any of these parent-pending tasks.
I strongly suspect some sort of pending task indication in kGTD or other GTD implementations is needed. So, when moving between context lists, I tend to loose some serious information- the order and pre-requisites or parent tasks. So, technically, that task of “grow bicrystal shouldn’t be in my task-list yet- as the library research hasn’t been completed.
BUT- what it doesn’t show me, is the fact that in the real-world, I need to do my research first before going into the lab. Now, the good thing about GTD is having a task list based on context- i.e., So, I page over to my task list. All these may lay under a project tab- like “Determine 3D plane of grain-boundary 1.” Nice- it’s in a project, so they’re related, and it’s in a subproject (my thesis), etc. In other words, in one project I may have work, on a microscope, and finally in regards to the research done. I find that in my simple task or project view, in kGTD and surely other apps- it can be somewhat difficult to understand children/sibling tasks when viewed all in a single context.
I love the flexibility of 3×5’s, and the ability to take my hi-Fi to my lo-Fi world is nice. Currently I’ve been using Kinkless’s kGTD to do my sorting etc., of my tasks, and printing them out onto 3×5 cards for use in my Levenger‘s Ballistic Shirtpocket Briefcase.
Omniplan scheduling how to#
For nuts and bolts of how to organize and think properly about tasks, GTD is where it’s at. Now, don’t get me wrong, GTD is absolutely fantastic, and it’s changing the way I deal with my work and projects. One of the things about David Allen’s Getting Things Done which has been slightly off-beat for me, is that it’s somewhat difficult for me to determine related tasks (especially when resorted into context views). Sibling/Children Tasks in GTD (a difficulty?) But first, some discussion of one of the difficulties in GTD the way I implement it…
Omniplan scheduling software#
Posted in FountainPens, GTD, Mac Software, Procrastination at 5:31 pm by a11enĪ quick tip of the hat to the OsX software producers OmniGroup for tackling the Gantt chart project planning in their new beta-product OmniPlan.
0 kommentar(er)
