trying to use Leos B article on learning new skills to implement James Clear habit tracking template into my life

Mrs-Polifax said (from David Allen, I think):
8. It’s fine to have multiple next actions on any given project, as long as they are parallel and not sequential actions (e.g., “Buy stamps” and “Mail invitations” would not both be on Next Actions lists for the “Put on Party for David” project given that you need to buy the stamps before you can mail the invitations).

fooddude said:
I think this is one of the most important keys to the whole system. And one where many make a mistake. Or they have some project note with all the next actions and try to use that instead of contexts. I try not to do that unless it is a large project and I need it to get it off my mind.

I'm glad to know that there is no reason not to put multiple actions from any given project on our actions lists, if we are able to manage that. I agree about the importance of not putting dependent items that cannot be done yet on our lists. The lists need to be only for items we can act on, or it could get confusing.

Could you explain a bit what makes it a bad idea to work from action steps in Project Support material for people who prefer that approach?

Thanks, Emily
 
Mrs-Polifax said (from David Allen, I think):


fooddude said:


I'm glad to know that there is no reason not to put multiple actions from any given project on our actions lists, if we are able to manage that. I agree about the importance of not putting dependent items that cannot be done yet on our lists. The lists need to be only for items we can act on, or it could get confusing.

Could you explain a bit what makes it a bad idea to work from action steps in Project Support material for people who prefer that approach?

Thanks, Emily
Mostly because you have to write down the next actions twice. Plus you aren’t working out of contexts. Which is a fundamental of gtd. That is why I only have a list of projects and the very next actions on a context list.
 
Project R: Plant Rhododendron for wife.

You Write on Agenda for Wife:
Where to plant the Rhododendron?

You Write on Next Actions List/@Computer context:
Locate a store that sells Rhododendrons.

Next Actions List/@Computer context:
You learn that Lowes sells Rhododendrons.
Done.

You write on Next Actions List/@Errands context:
Buy Rhododendron at Lowes.

You stop for Today.

Four days from now:

Agenda for Wife: Where to plant the Rhododendron?
Wife says to plant the Rhododendron at X location.
Done.
Next Actions List/@Errands context
You buy the Rhododendron at Lowes.
Done.
Next Actions List/@Home Context:
You plant the Rhododendron at X location.
Done.

---------------------------------------------------------------------------------
Thank you, @fooddude. I remember the Rhododendrons in Golden Gate Park long ago when I lived in San Franscisco. I love examples, especially ones about typical things around the house. It really clarifies how it works to have these details.

I think you want to point out that you have only one Next Action for a Project until you complete that Next Action. It is a little hard to see that because of not knowing exactly when things happened, but I get the idea.

I'm sorry I can't see the links you posted. Google won't let me see them unless I sign in. I see the photo, though, and you do have Project Support Folders (and nice bright colors). I am pretty sure I will need Projects folders.

I happened to find this article online from (I'm pretty sure) David Allen. It is a fortuitous find because it mentions the conditions under which we might have more than one Next Action for any Project.

Managing projects with GTD​

Having a complete and current projects list is one of the cornerstones to GTD mastery. To support you in getting there, here are 10 keys to defining and managing projects:

1. Projects are defined as outcomes that will require more than one action step to complete and that you can mark off as finished in the next 12 months.

2. Think of your Projects list as a current table of contents of the current outcomes on your plate.

3. Most people have 10-100 current projects, personally and professionally.

4. Current projects have at least one next action, waiting for, or calendar action, in order to be considered current.

5. Projects that have no current next action, waiting for, or calendar action are either no longer projects for you, or should be incubated to Someday/Maybe.

6. Future actions (i.e., actions that are dependent on something else happening first) do not go on the Next Actions lists until you can take action on them. They get stored with project plans.

7. The Projects list and project plans are typically reviewed in your GTD Weekly Review, ensuring each project has at least one current next action, waiting for, or calendar item.

8. It’s fine to have multiple next actions on any given project, as long as they are parallel and not sequential actions (e.g., “Buy stamps” and “Mail invitations” would not both be on Next Actions lists for the “Put on Party for David” project given that you need to buy the stamps before you can mail the invitations).

9. Projects are listed by the outcome you will achieve when you can mark it as done (what will be true?).

10. Effective project names motivate you toward the outcome you wish to achieve, and give you clear direction about what you are trying to accomplish.

###

Thanks, again.

Emily
@Mrs-Polifax

Actions . . . as . . 'Next Strategic Completion(s)' ?
 
@fooddude
Mostly because you have to write down the next actions twice. Plus you aren’t working out of contexts. Which is a fundamental of gtd. That is why I only have a list of projects and the very next actions on a context list.
==
Yes, of course, it is historical GTD to work from Contexts, and you have a good point that the latter involves a duplication of effort.
 
Could you explain a bit what makes it a bad idea to work from action steps in Project Support material for people who prefer that approach?
I think it’s great to have project support files and have action steps spelled out there, as needed.

Your Next Action List should contain a trigger with one next action to send you to that support file for when you’re up to “doing” that action. (For example “work on taxes, make list of all forms needed”) Then once you’re “doing”, you can work from the support file to know exactly which forms you need & the next steps to take. When you stop working (or “Doing”), you put one very next action on your Action List as a trigger for you to continue when you’re ready to “do” again at a later time.

Would you agree @fooddude & other experienced GTDers? Is that clearly explained?

Sarah
 
Last edited:
I think it’s great to have project support files and have action steps spelled out there, as needed.

Your Next Action List should contain a trigger with one next action to send you to that support file for when you’re up to “doing” that action. (For example “work on taxes, make list of all forms needed”) Then once you’re “doing”, you can work from the support file to know exactly which forms you need & the next steps to take. When you stop, you put one very next action on your Action List as a trigger for you to continue when you’re ready to “do” again at a later time.

Would you agree @fooddude & other experienced GTDers? Is that clearly explained?

Sarah
Personally I don’t do that. I just have a list of projects with the very next action on a context list. That way I don’t have to tag and cross reference information. If and it’s rare I have a very large project I may have a support file. I currently have three. I don’t have next actions laid out for them anywhere though. I just have the very next action in a context list. But yes it was clearly explained.
 
Personally I don’t do that. I just have a list of projects with the very next action on a context list. That way I don’t have to tag and cross reference information. If and it’s rare I have a very large project I may have a support file. I currently have three. I don’t have next actions laid out for them anywhere though. I just have the very next action in a context list. But yes it was clearly explained.
Thanks. Yes, I agree. Not every one of my projects has a support file and I only plan the next steps as necessary, I don't lay out all my next actions for each project.

It is important to note that not all projects need a project support file and not all projects need all the plans laid out.

I was responding to the idea of "work[ing] from action steps in Project Support material for people who prefer that approach"

If one has project support files and keeps actions there, one should still have a next action list with triggers to go to each of those files and take actions.

If one only works from actions in project support files, they may miss taking actions that belong only on a next actions list and don't have support files.
 
Thanks. Yes, I agree. Not every one of my projects has a support file and I only plan the next steps as necessary, I don't lay out all my next actions for each project.

It is important to note that not all projects need a project support file and not all projects need all the plans laid out.

I was responding to the idea of "work[ing] from action steps in Project Support material for people who prefer that approach"

If one has project support files and keeps actions there, one should still have a next action list with triggers to go to each of those files and take actions.

If one only works from actions in project support files, they may miss taking actions that belong only on a next actions list and don't have support files.
@Sarahsuccess

GTD 'nimbleness' is a Calendar [chronos] / Context(s) [kairos] / Project 'priority' must ?

Thank you very much
 
Last edited:
@Mrs-Polifax

Actions . . . as . . 'Next Strategic Completion(s)' ?
' I scanned over this thread - see that there a 9 more posts by 1 2 3 4 - other users

which I am un able to fully cognize

writing with termonology , like a type of format

GTD 'nimbleness' is a Calendar [chronos] / Context(s) [kairos] / Project 'priority' must ?

- I don't understand how you type or write in this type of format - with the different bold, italics etc - did you copy that from somewhere?

send'
 
Top