For dependent tasks that are part of a project, the general advice seems to be that they should go in project support materials until it's time for them to become next actions. But what about dependent tasks that aren't part of projects? For example, let's say I've just signed up for LinkedIn, and I have a next action to fill out my profile. However, I've also just gotten a job offer and I need to decide whether I'm taking it. It would be silly for me to fill out my profile if I'm about to switch jobs, so I decide to wait until I've figured out whether I'm taking the job to do the profile. Thus, filling in my profile is no longer actually a next action. But it's also not related to the job decision from a project perspective (say it's under the project "Sign up for LinkedIn" or something). I need to note that the latter is dependent on the former without losing track of it. I've considered using the Waiting For list, but I like keeping that purely for people dependencies. I'd like to figure something out that doesn't depend on me just hoping to catch it in Weekly Reviews. Thoughts?