• Our deepest thanks to the many GTD enthusiasts who have posted in and read this forum over the years. Because use has been steadily declining in recent years, we have reluctantly decided to make this forum a read-only reference archive. There is an active GTD discussion community on the new GTD Connect. Copy/paste this link to get a free trial: https://bit.ly/4hYicYV We still offer a range of other free resources for GTD enthusiasts at: https://gettingthingsdone.com/resources/

Someday-Maybe Projects and Waiting For actions

B

Borisoff

0
Where do you keep your WaitingFor next actions if the project assosiated with them moved to Someday-Maybe category for one or another reason?
 
On the other hand it's easier to remind when and why the project was put to Someday-Maybe. Maybe it's convinient to copy the last WaitingFor to notes section of the Project?
 
Inform and delete.

Borisoff;51054 said:
Where do you keep your WaitingFor next actions if the project assosiated with them moved to Someday-Maybe category for one or another reason?
Click to expand...

So you asked somebody to do something for you (you are WaitingFor somebody's action) and then lost interest in this project?

I think you should inform this person that you are not interested any longer and delete the WaitnigFor item.
 
The Outlook Add-on handles this problem perfectly.

- You have a project and a next action (the NA could be a waiting for - but it doesn't matter what context it is.) THat NA may even have an email attached to it.
- Then, during a weekly review, you decide the project should be moved to your someday maybe.
- When you do that, the software moves the NA and the email that is tied to the project (which you are now incubating) to a place that is hiden but will be reactivated into the proper context once you decide to move the project back to your active project list from your someday maybe list.

Its even more smooth then I was able to describe it!

The way that outlook at the addon ties projects with NA and emails is the reason I haven't gone analog. It's just too easy and reliable in digital (not to mention searchable).

OK, I'm done with my propoganda.

Cheers
Ryan
 
Definitely let the other person/organization know what's changed (I like the idea of asking "Who needs to know about this?" when making changes). Then, depending on whether you want to recall the W/F in the future, either trash it, or jot a note in your project plans folder for it.
 
What if I need to remind a person about an action I need from him (@Waiting) in a month or two. Should I keep this project on my projects list or at SM?
 
Borisoff;51105 said:
What if I need to remind a person about an action I need from him (@Waiting) in a month or two. Should I keep this project on my projects list or at SM?
Click to expand...

I'd put the action to remind in my tickler so I won't keep seeing something non-actionable in the Action Lists. If it's definite that you're going to continue the project, I'd keep it on the projects list. If it's unknown whether you will continue the project, I'd put it on S/M. If there's a decision point I'd put it in the appropriate place (a meeting to decide goes on the calendar; a follow-up email you need to send in two months, in the tickler file; etc.)
 
You must log in or register to reply here.
Top