43 Folders

43 Folders feed subscription icon - Shiny!Time, Attention, and Creative Work. After 4 years and a lot of productivity pr0n, we’re shifting gears. Re-learn how to use 43 Folders. Then back to work. [»]

”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.

Gantt meets kGTD ?

Hi guys,

I have a question, that maybe someone with more GTD experience can answer. Here's the problem that I have that seems to occur with some mild frequency. I'll try and explain my issue, suggest a weird hybrid solution, and see what you guys think.

Essentially, what I find is that I often have tasks which are important to be accomplished before other tasks are accomplished. They are linked up, perhaps even across various "projects" in the kGTD type thought. One obviously needs to come before the other, they are not really subprojects of each other, but they are say, "siblings". But, they are linked siblings.

I tend to often think about tasks in a semi-Gantt type view. At least, I find it *sometimes* helps to think about larger projects in this mode, as it tells me what is holding up the rest of the ball-game, and what can be worked on without waiting around for other things to be done. BUT- I often find that the Gantt view is pretty crazy for full implementation. People rarely use Gantt project views to get things done, unless they've been required to use them, perhaps to show the course of events to "completion" for those higher-up (at least that's my guess- that's been one of the few uses I've had for Gaant views).

What I'm finding however, is some interest in a Semi-Gaant like view *inside* my GTD lists. Something like drawing a line down the page connecting the two tasks which are related to each other, and a number beside them indicating their order of importance. I have not implemented this at all yet. But, something like a visual indication of first and second related tasks would be useful for me.

The only way I can think of showing a relationship like this in kGTD is to make one task the child of the other task... or perhaps small sub-projects, that type of thing encompassing two tasks which are siblings. Is this the GTD way to think about it? What would David Allen say about these types of related tasks? To me the sub-projects look like they may become a bit schizophrenic... do we really need projects subprojects etc.? Wouldn't it be a bit easier to just have lines connecting up siblings and have them placed side by side in the lists in the proper order?

Any and all thoughts on how you handle sibling tasks which are dependent on each other in your to do lists are greatly appreciated!!

Cheers!
-Allen

ps- for those who don't know what the heck I mean when I talk about Gaant, here's a sample: Gantt Chart on Wikipedia

pps- some of this is motivated by my super-long lists which are getting to be a bit out of hand. There must be a bit better way of visualizing related and dependent tasks than just the next item on the list. I often find this is one of the weak points in my system... the recognition or visualization of the critical and dependent tasks and their subsequent relationship to next action.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
GH's picture

Gantt lite

Spend $13 at Home Depot on a 4' X 8' melamine shower board (same material as plastic whiteboards).

http://www.kk.org/cooltools/archives/000679.php

Use post-its and dry-erase markers to rough out task dependencies and timelines.

SteveC's picture

Flip the chart!

Have you met the PERT chart? It's another way of looking at the information on a Gantt, but it's easier to construct. (In MS project, they're linked so you can switch from one view to the other).

What you do is work out the 'deliverables' (what I need to have produced so I know that the job's done -- in GTD speak it might be a completed NA or more likely a (sub-)project). Draw a box for each deliverable and record how long you think its going to take. Then work out what needs to have been done before you can start the NA which finally produces that deliverable. That goes in its own box with an arrow to the next. If you put times on you can work out critical paths an so on as well. The information can then be turned into a Gantt.

I find them easier to work with as they're more free form. You're not tied to any specific dates or ordering until you've got all the information.

Hope that helps a bit.

Steve

Lachia's picture

white board

I have always wished I could have a larger white board!!! You sir are a genius!!!

appelq's picture

This is the same problem...

This is the same problem I've been working with.
My solution is to keep "Projects" separate from my GTD Lists.
See my recent post on Projects and GTD

If I read your post correctly though, you may have related (interdependant) tasks form separate projects?

Claire's picture

I have a similar Project...

I have a similar Project system to appelq, so thought I'd throw in my method. As well as marking actions as "NA" in my project lists (kept in Evernote, but I like the idea of using OneNote, might try that out...), I also mark them "Calendar" if they've been assigned to a particular time in my calendar (e.g. actually going to the doctor, if the project is making and attending a doctor's appointment). Finally, and most relevently, I mark some of them as "Waiting for... such and such to be completed" so that when I review my projects I can just skip over that one without having to think about why I can't make a next action for them. It also focuses my mind on finishing the other task(s).

Btw I used to put these on my Waiting for list, but I found it was too irritating looking at them every day, and left the Waiting for list for people who I need to chase for answers, rather than trying to use it as a reminder system for myself as well.

a11en's picture

Hey guys, these are all...

Hey guys, these are all great discussions. I'll check them all out! :) I'm slowly understanding the systems a bit more deeply now. My real bane is that I'm a very visual-thinker. I tend to want to see things in space rather than written word etc. So, I tend to think with graphs. I think that's why the Gaant is so excellent for me... I can visually identify related/required tasks for larger goals.

I'll check these all out, guys! Thanks a ton!! :)

[If I make any break-throughs, I'll be back to post!]

AlanY's picture

You may consider sending OmniGroup...

You may consider sending OmniGroup a feature request to add a Gantt column type to OmniOutliner. Ecco, a columnar outliner for Windows that rarely gets the love it deserves, has a Gantt column type that's pretty useful for visual folks. It's useful for more than just scheduling too... for instance, it's nice to be able to look at a list of employees and view the days they've booked off for vacations as stacked Gantt rows.

Note that Ecco doesn't support vertical bars of the type you describe; it depends on you using the outliner to represent dependencies. That's usually the best way to do project management with an outliner. It's not as general as a full-scale project management tool, where subitems from different parent items may have interlinked dependencies, but those programs end up being overkill most of the time, and outlining is a much more elegant metaphor that suffices for the vast majority of projects with dependencies.

 
EXPLORE 43Folders THE GOOD STUFF

An Oblique Strategy:
Not building a wall; making a brick


STAY IN THE LOOP:

Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed

Inbox Zero

The original 43 Folders series looking at the skills, tools, and attitude needed to empty your email inbox — and then keep it that way. Don’t miss the free video of Merlin’s Inbox Zero presentation.

Making Time

3-part series on attention management for artists and makers. Read Bad Correspondence, The Job You Think You Have, and One Clear Line.