I have little trouble with dependencies in a specific project. The issue I do have with them is if I would like to do this project before I do that one. If something gets stuck that I didn't foresee in the first project I lose sight of the other one that I could be working on while I wait on someone or something. I am learning that is not a good thing to do at least until I can get regular reviews under control. It does work well though if an emergency pops up I can put that in and make everything dependent on the emergency which shortens my list very quickly until the emergency is done that is. Or if I could get my list short enough to have one active folder for work and one for personal instead of how it is below. I am a long way off from that though.
I saw something on that twitter link that I think is going to really help. Putting a closed time frame on certain contexts. That will help separate a lot of my home tasks from my tasks that can be done anytime and anywhere.
My structured list is set up pretty similar to yours:
Routines - reoccurring tasks anything from daily to yearly
System - general system maintenance like clearing my inboxes and weekly reviews etc
Work
Role 1
Active
Prioritized (hidden - someday maybe plus anything that doesn't have to be done this week) - I used to have these separate but it was too hard to review so I try to prioritize so the top is things that need to be done sooner and the bottom is maybe never things
Role 2
Active
Prioritized
...all the way to Role 9
Personal
Role 1
Active
Prioritized
...all the way to Role 8
One Times - projects that completed and go away
System - ex would be applying those closed periods to my contexts
Work
Role 1
Active
Prioritized (hidden - someday maybe plus anything that doesn't have to be done this week) - I used to have these separate but it was too hard to review so I try to prioritize so the top is things that need to be done sooner and the bottom is maybe never things
Role 2
Active
Prioritized
...all the way to Role 9
Personal
Role 1
Active
Prioritized
...all the way to Role 8
Then I have a few other main levels like procedures to copy, ideas, reference, and I actually do have a probably never at the bottom of projects that got x'd but their plan was very detailed and I didn't want to just delete b/c it could be used in different projects (all of these are hidden). For example I manage our network at work among other things so I have a procedure for setting up a new employee in my procedures to copy folder. So when we have a new employee I go copy the whole project from procedures to copy and paste it in my Network Role under work and give it the deadline of the day before the employee starts. Just that one project may have 50 tasks with a lot of dependencies especially if it includes setting up a new computer from scratch.
Another big issue I have is I don't know what is coming. I wish I had away to see down the road easily. For example b/c my routines are set to weekly, every 6 mos, annually etc sometimes they fall on the same day. That isn't a good list day even though it may be a productive day. Other times I had several things dependent on one project so when that project gets done all of these other things immediately show up on my next action list and it gets kind of overwhelming.
I think my system itself works pretty well if it has a doable number of tasks but I don't have anything that stops me from over planning the time available. Does that make sense? Does anyone have a way to see when you are over allocated?
Thanks,
Susannah