Understanding "waiting for" list (vs. calendar)

Andrea! said:
What do you do, if an item on your "waiting for" list turns into "actionable"? Will you move it to "next actions"?
Click to expand...

Most of the time, I would add an action to contact whoever I was waiting for. I would still be waiting, so I would leave it on my list.

The exception would be if I was giving up on waiting, in which case I would remove it from my list and think about how else the project could be achieved.
 
Andrea! said:
What do you do, if an item on your "waiting for" list turns into "actionable"? Will you move it to "next actions"?
Click to expand...
Do you mind clarifying? Waiting for is the very next action. And waiting for with another next action for me to do is the only time I might have another next action for one project on my list.
 
fooddude said:
Do you mind clarifying? Waiting for is the very next action. And waiting for with another next action for me to do is the only time I might have another next action for one project on my list.
Click to expand...
Let's say the item on "waiting for" is: "Did Jimbob return the $ 20?"

During my weekly review, I decide, that I want to ask Jimbob to return to money. So I could create a next action "Ask Jimbob to return to money i gave gim on 20th of November 2024." At the same time, of course, I shall remove this item from "waiting for."

This is what I meant with "move it to next actions."

Andrea
 
Andrea! said:
Let's say the item on "waiting for" is: "Did Jimbob return the $ 20?"

During my weekly review, I decide, that I want to ask Jimbob to return to money. So I could create a next action "Ask Jimbob to return to money i gave gim on 20th of November 2024." At the same time, of course, I shall remove this item from "waiting for."

This is what I meant with "move it to next actions."

Andrea
Click to expand...
Again, That is about the only time I might have two next actions for one project. I am still waiting for the $20 but I would put call JimBob about $20 on my @Phone list.
 
Andrea! said:
Let's say the item on "waiting for" is: "Did Jimbob return the $ 20?"

During my weekly review, I decide, that I want to ask Jimbob to return to money. So I could create a next action "Ask Jimbob to return to money i gave gim on 20th of November 2024." At the same time, of course, I shall remove this item from "waiting for."

This is what I meant with "move it to next actions."

Andrea
Click to expand...
I think this depends on your system/software.

On OmniFocus, both the Waiting For and the post-waiting-for action would already be in the project. So I wouldn't remove the Waiting For item, or remove it, or move it to the project--it's already in the project. I would check it off as done, and then the next action would appear.
 
Gardener said:
I think this depends on your system/software.

On OmniFocus, both the Waiting For and the post-waiting-for action would already be in the project. So I wouldn't remove the Waiting For item, or remove it, or move it to the project--it's already in the project. I would check it off as done, and then the next action would appear.
Click to expand...
Yeah I use Apple notes. I have a note for projects with every project written in a list. Each context is a note with the very next action for a project on the correct context. I don’t have projects listed in separate notes with all the next actions listed.
 
I don't personally bother with chasing people via my WF list. I mainly use WFs so that when I look at a project it isnt just blank, which might confuse me about what's next. In practice I run through all my projects anyway during the weekly review, so I just change any Waiting Fors into an @email or @phone or whatever action chasing the person. On the odd occasion that I need something back at such short notice that I can't wait til the Weekly Review, I set an alert on the WF.

That said, it is nice to have the list available and broken down by person, so that if you end up in a meeting with that person, you can quickly find everything related to them.
 
bishblaize said:
I don't personally bother with chasing people via my WF list. I mainly use WFs so that when I look at a project it isnt just blank, which might confuse me about what's next. In practice I run through all my projects anyway during the weekly review, so I just change any Waiting Fors into an @email or @phone or whatever action chasing the person. On the odd occasion that I need something back at such short notice that I can't wait til the Weekly Review, I set an alert on the WF.

That said, it is nice to have the list available and broken down by person, so that if you end up in a meeting with that person, you can quickly find everything related to them.
Click to expand...
This is hard to visualize. Can you clarify the "project isn't just blank"? I mean I just use a simple list for projects. Then I put the very next action on a context list. Also what you have described seems to be what GTD calls Agendas. WF is specifically for things you are waiting for. Answers to questions, results from a delegated next action, or a reference item.
 
fooddude said:
This is hard to visualize. Can you clarify the "project isn't just blank"? I mean I just use a simple list for projects. Then I put the very next action on a context list. Also what you have described seems to be what GTD calls Agendas. WF is specifically for things you are waiting for. Answers to questions, results from a delegated next action, or a reference item.
Click to expand...
Sure, its just how the tools I use are laid out. I like ones where you have the Project and then the Next Actions nested underneath or next to it, see below.

CleanShot 2025-02-19 at 19.21.22.png
If I look and just see the project and no actions, I can't immediately tell if that means I haven't figured out what comes next, or if Im waiting for someone else. So even though I don't really use them to chase people up, I still put them there.
 
bishblaize said:
Sure, its just how the tools I use are laid out. I like ones where you have the Project and then the Next Actions nested underneath or next to it, see below.

View attachment 2230
If I look and just see the project and no actions, I can't immediately tell if that means I haven't figured out what comes next, or if Im waiting for someone else. So even though I don't really use them to chase people up, I still put them there.
Click to expand...
Ah. I stick more with classic GTD. A project list with the next action on a context list. Example of context list. With the very next action for projects. This way I work out of contexts and not projects. 1739994284889.png1739994385780.png
 
Last edited:
fooddude said:
Ah. I stick more with classic GTD. A project list with the next action on a context list. Example of context list. With the very next action for projects. This way I work out of contexts and not projects. View attachment 2231View attachment 2232
Click to expand...
I also work out of contexts, see below

CleanShot 2025-02-19 at 22.08.59.png
But I find the Project View better when I'm reviewing my projects. Then I can see all the Next Actions related to them, even if they're in different contexts.
 
You must log in or register to reply here.
Top