andersons;44482 said:
Hmm. Well, maybe so, but then I guess GTD is not the only way to get things done, or even necessarily the Best Way.
Well I suppose that is a reasonable hypothesis, but it's not one I think most people on this board (all about implementing GTD) would agree with.
If you had been linking them previously, and reviewing them every other week, then of course you should be able to identify the correct project for each action, given a list of actions.
The real question is how well your brain would know your projects and actions if you had never, ever organized them with external links.
The act of organizing information by somehow visualizing relationships changes the way your brain represents and recalls the information -- even after you stop visualizing the relationships externally.
This is exactly David's point, I believe, that the act of doing the weekly review and getting it all out of your head and on to your lists is the process by which you achieve the sense of mind-like-water or creative flow or whatever. There is so much more that comes from the weekly review than embedding the project-next action link into your brain that it makes sense to focus on doing the weekly review and not spending time fiddling with software bits to embed an explicit project-next action link in your system.
Those additional benefits include:
1. Visualizing every one of your projects completed every week. This makes you much more likely to achieve those results.
2. Going down what David calls "Constructive Rabbit Trails", and by this I believe he means identifying critical next action steps that will allow you to achieve your results faster and with less effort. I find this happens much more frequently now that I'm doing my reviews at least weekly....
3. Identifying elements in the matrix (from next action to 50,000 feet) that should be either dropped or added in order to align your next actions with your total life goals.
Oh and you'll be able to instantly recall what project a next action goes with too... but that's just a side benefit.
For me, 3 seconds is a worst-case, not the typical case. And no, 3 seconds is not too much. It saves much more time during Weekly Review, when it probably takes more than 3 seconds to make sure your project has a NA.
And it's not really the 3 seconds per next action that is the real time killer, its the hours spent looking for a solution to this problem that would be better spent focused on doing the weekly review. How many hours did you spend twiddling with software before you found your current system? Does it give you all the same benefits as the weekly review? If it does, great, but I think David's point is that the systems he's seen are so over-engineered as to nullify the small benefit early on of linking next actions to projects.
Doing the weekly review is a fundamental of GTD. Work on the fundamentals first before trying to do the advanced stuff and you'll gain more benefit from it than you will if you try to bring in more complexity before you've mastered the fundamentals....
....
The main reason is that because projects and actions ARE REALLY linked -- the actions are steps to complete projects -- you will have to do the linking sometime, somehow. The GTD way is in one lengthy Weekly Review.
Actually 52 lengthly reviews a year... "You'll have to think about your stuff more than you thought you might, but not as much as you're afraid you'll have too."
More to the point, just because they are linked, why do I need an explicit link to crank the widget?
Another reason is that it is often desirable to catch projects with no NAs more often than once a week.
Why do I need a link to do this. Since I've completed my weekly review recently it is enteirely natural for me to instinctively think "what's the next action" when I complete the previous one. I simply enter it in my vanilla palm implementation without a project link and I'm good to go.
Another reason is that if you can instantly switch to a project-context view of an NA, you can sometimes more intelligently complete that NA. Or even see a better way to make progress on the project. Or get into a "flow" of progress on that project.
I've never understood this. When in the thick of quickly cranking widgets I am much less likely to "sometimes more intelligently complete that NA. Or even see a better way to make progress on the project." I'm too busy cranking widgets to do that. I'm much more likely to go down these constructive rabbit trails when I'm doing my weekly review.
As for being in a flow on progress on a project that may happen, but generally for me it only occurs in the @Office or @Home project or when I've blocked out an hour or two (Hard Landscape) to really focus on that project. In that instance, I'm really doing a mini-weekly-project-focused review; which reinforces the system and the fact that I don't really need an explicit link.
I think David's point is that doing the weekly review is fundamental. That it helps you in lots of ways that a project-next action link doesn't, and that in fact, such a link is a crutch that actually prevents you from making the kind of progress you'll need to make in order to master this stuff.
In fact I wonder if it would be a reasonable hypothesis to state that it may take less than 2 years for someone to "really get" this stuff if they didn't go down the destructive project-next action link path?