What should one do with projects that are dependent on the completion of other projects?

Justin J

Justin J

Registered
I have a few projects that I plan to complete within the next year, however, I cannot begin working on them until other related projects have been completed. What should I do with projects like these? Should I keep them on a Someday/Maybe list until I can make progress on them, or should I just keep them in my active projects list since I plan to start and complete them within the next year?

Let me know how you handle these types of projects in your own system. Also, any tips and suggestions re: this issue will be greatly appreciated!

Thanks in advance!

P.S. To give an example, one of the projects I have in limbo right now is "retake GRE test", but I can't start this project until after my "study for GRE test" project is completed.
 
I would rethink that project into two options..... Is the project really take GRE test and study for GRE test or is it to "Get XX score or higher on GRE test".

  • Option 1
    • If you can accomplish this within a year (or so) I would make it a sequential project. Study might be broken down into 10, 20, or 30 next actions on studying X material etc.
    • Taking the test might be a next action after that
    • and last review score is the next action. If happy, complete project. If not create actions for more studying, registering for test, taking it, etc.
  • Option 2
    • This might be a goal if it is longer term.
    • Within the goal definition you can create reminders for yourself of the steps and activate them to your project list when appropriate.
 
If it is within a year, I would have one project called "Pass GRE test by X date." The very next action in a context next action list. I don't put all next actions together (usually) but in this case I might make a checklist of things that I need to do.
1 What sections did i miss last time
2 Register for test by x
3 Etc
I would assume you would want to treat this like another job. So once you sit down every day the next actions will become clearer. When you finish at the end of the day, put your very next action down on a next action list.
But I would make it as simple as possible. Again, I'm not one who would sit and for every project plan every next step for every project. I put the project on a project list and the next action on a context list.
 
Assuming you really want two projects and not one larger project, you have lots of options: trust that completion of one project will trigger the initiation of the next; put a note in the project support for the first project reminding you to start the next upon completion; put it in someday maybe or perhaps a tickle file; make the final result a Level 3 goal. I think these are all viable, and you don’t have to restrict yourself to one strategy. I wouldn’t put the second project on an active project list because it’s a distraction.
 
In general, projects that I can't start yet go on my Someday/Maybe list. My rationale is that by the time the prerequisite is met, my priorities may have changed.

If they have a deadline, I also create a tickler to remind me of the deadline a couple of weeks in advance.
 
mcogilvie said:
Assuming you really want two projects and not one larger project, you have lots of options: trust that completion of one project will trigger the initiation of the next; put a note in the project support for the first project reminding you to start the next upon completion; put it in someday maybe or perhaps a tickle file; make the final result a Level 3 goal. I think these are all viable, and you don’t have to restrict yourself to one strategy. I wouldn’t put the second project on an active project list because it’s a distraction.
Click to expand...
Can you please tell me how can I manage two related projects so that I stay focused on the first one but still ensure the second project gets started at the right time?

Mike Taku
 
Mike Taku said:
Can you please tell me how can I manage two related projects so that I stay focused on the first one but still ensure the second project gets started at the right time?

Mike Taku
Click to expand...
Make a next action at the end of the first one to activate the second. I do that all the time, points me in the right direction!
 
In the short term, say a week or two, I just put a WF on a project that's waiting for another project to finish. "WF Project A to finish".

Longer term I do the same but also defer the project so I don't keep seeing it week after week before I can action it. (Deferring it in the tool I use won't show the project unless you press a button asking to show deferred projects.)

With more complex dependencies for longer term projects with many sub-projects, I usually use a kanban board.
 
ivanjay205 said:
I would rethink that project into two options..... Is the project really take GRE test and study for GRE test or is it to "Get XX score or higher on GRE test".

  • Option 1
    • If you can accomplish this within a year (or so) I would make it a sequential project. Study might be broken down into 10, 20, or 30 next actions on studying X material etc.
    • Taking the test might be a next action after that
    • and last review score is the next action. If happy, complete project. If not create actions for more studying, registering for test, taking it, etc.
  • Option 2
    • This might be a goal if it is longer term.
    • Within the goal definition you can create reminders for yourself of the steps and activate them to your project list when appropriate.
Click to expand...
Thank you for your suggestions @ivanjay205! I'm leaning more toward combining the two projects into one, but I understand the use and value of option 2 as well.
 
mcogilvie said:
Assuming you really want two projects and not one larger project, you have lots of options: trust that completion of one project will trigger the initiation of the next; put a note in the project support for the first project reminding you to start the next upon completion; put it in someday maybe or perhaps a tickle file; make the final result a Level 3 goal. I think these are all viable, and you don’t have to restrict yourself to one strategy. I wouldn’t put the second project on an active project list because it’s a distraction.
Click to expand...
Thank you for your advice and wisdom @mcogilvie! I understand how each of the options you relayed are viable and I will consider which ones work best for each circumstance. I value your emphasis on "trust". As a neophyte to the GTD method, I am still learning to trust my external system/capturing tools instead of relying on my brain to consciously remember everything on my plate. Thanks again!
 
Justin J said:
I have a few projects that I plan to complete within the next year, however, I cannot begin working on them until other related projects have been completed. What should I do with projects like these? Should I keep them on a Someday/Maybe list until I can make progress on them, or should I just keep them in my active projects list since I plan to start and complete them within the next year?

Let me know how you handle these types of projects in your own system. Also, any tips and suggestions re: this issue will be greatly appreciated!

Thanks in advance!

P.S. To give an example, one of the projects I have in limbo right now is "retake GRE test", but I can't start this project until after my "study for GRE test" project is completed.
Click to expand...
@Justin J

Projects can remain as one Project or divided into Sub-Projects

Unfortunately, full-integrity can be very demanding and seems to shun short-cuts ?

Aside from your expressed GRE concern; full-integrity can be a very good reminder why, especially when it comes to the External-Sphere, all optional Projects should be 'absolutely' necessary with full-integrity unless one desires more unintended consequential Projects ? Fun, fun, fun. . .

When it comes to Project(s) completions, GTD practice/professionalism has its own way of teaching one that Projects, especially in the External-Sphere, Projects can often be an all-in game and takes no prisoners . . . perhaps why so many seem to try to run to greener pastures prior to completion ?

The only way out is through

As you see GTD fit. . . .
 
Last edited:
Mike Taku said:
Can you please tell me how can I manage two related projects so that I stay focused on the first one but still ensure the second project gets started at the right time?

Mike Taku
Click to expand...
Sure: the simple-not simple answer is that what exactly you do depends specifically on you and the tools you use. I use Things, which is a sophisticated task manager, but as you will see, that’s not what is important. I can put a task in a project that says “Project A done? Start Project B”, set it a to future start date or as a Someday/Maybe. I will see this task every weekly review, and I will see it when I check off the project. Or I could put it outside Project A. I will still see it every weekly review. If I put the sequence of projects as a level three goal (more than one project, 1-2 year horizon), I will see it on the first Saturday of every month when I am reminded to review level 3 goals (30,000 feet to GTD old timers). If it’s level 4, I will see it every quarter. I could do all of these things with paper lists and a paper calendar. It’s not the tool, it’s you doing the work of what David Allen calls “cycles of review.” It’s also part of what Robert Peak calls “being kind to your future self.” Notice that the habit of review starts with the weekly review. You have to maintain your system the way a prize-winning gardener maintains their garden.
 
mcogilvie said:
Sure: the simple-not simple answer is that what exactly you do depends specifically on you and the tools you use. I use Things, which is a sophisticated task manager, but as you will see, that’s not what is important. I can put a task in a project that says “Project A done? Start Project B”, set it a to future start date or as a Someday/Maybe. I will see this task every weekly review, and I will see it when I check off the project. Or I could put it outside Project A. I will still see it every weekly review. If I put the sequence of projects as a level three goal (more than one project, 1-2 year horizon), I will see it on the first Saturday of every month when I am reminded to review level 3 goals (30,000 feet to GTD old timers). If it’s level 4, I will see it every quarter. I could do all of these things with paper lists and a paper calendar. It’s not the tool, it’s you doing the work of what David Allen calls “cycles of review.” It’s also part of what Robert Peak calls “being kind to your future self.” Notice that the habit of review starts with the weekly review. You have to maintain your system the way a prize-winning gardener maintains their garden.
Click to expand...
Hi there, I hope you are doing great.

I agree! It’s all about having a consistent review process, whether using a tool like things or just paper lists. Regularly checking in on your tasks helps keep everything moving forward and ensures you’re staying on track with your goals.

Mike Taku
 
You must log in or register to reply here.
Top