I keep a separate list called Projects - Aware. This includes projects that I don't have any direct responsibility for, or involvement with, but I may be involved in later or will be impacted by later. In my industry, there are often a lot of franchise-directed projects that may or may not involve me at some point.
For example: our company is launching a new appointment scheduler. I am not part of the roll-out team, so don't have any direct responsibilities or involvement. The timeline for launch is not firm as it hinges on team training and the actual technical integration between multiple companies involved. HOWEVER - as soon as it does go live, I will need to update the appointment scheduling forms on our website, and complete some testing to ensure leads are routing into our CRM as intended. I do periodically get forwarded status update emails, but am not "officially" in the loop, and I do not work at the same location as the folks rolling it out, so there's little likelihood of serendipitous updates.
Since there's no specific timeline, I can't put a tickler/calendar notification. There are numerous people involved, so an Agenda item may work, but most of these people are not folks I work with regularly 1:1, so isn't ideal. The person ultimately overseeing the project is at the executive level and is responsible for a huge amount of things, so a waiting for may work, but may also lead to an "oh no, that launched a week ago and the leads are now going nowhere" situation. For me, the best case scenario is keeping this on my Projects - Aware list, so that I can keep it in my periphery. If it's been a while since I've seen an update or heard one, I can decide what to do next - add it as an Agenda item for the next time we talk, add a next action to follow-up and see if we have a timeframe moving forward, or check my exec's calendar to see if training meetings are still happening.
Observation/caveat: I will note that I deep down personally HATE being blindsided by things or spending time fixing things that don't need to be. I recognize that others may feel perfectly comfortable with a Waiting For item on this, and addressing it if it turns into an "oh no, it launched a week ago" scenario. It's my own preference (neurosis?) to be as proactive as possible so as not to have to put out fires or scramble to do things last minute because other folks are NOT GTDers.
Other examples where I've used this to keep peripheral items within view:
- We have a franchise directive that will require an action item from me if it's implemented, but our exec team is applying for an exception to postpone the directive, which means I will not have an action item.
- A department is being restructured, which may require updates to customer-facing materials and websites, depending on what decisions are made.
- My mother is working on some landscaping projects, which may or may not require help due to some post-surgical limitations, but she is beautifully stubborn and won't ask for help, but will accept if it's offered. It helps keep it top of mind for me to ask about in conversation, check out when I'm at her house, or mention it to my brother to check out the next time he's there, without it being a "checkbox" to talk to her about.