Please express an Easier way [GTD or Otherwise] to execute Next Actions

GTD Opportunity Management

A D D I N G [Parlaying]
W H A T
N E E D S
t o
B E
C O N T E X U A L L Y
D O N E
t o
W H A T
i s
A L E A D Y
B E I N G
C O N T E X U A L L Y
D O N E
 
Last edited:
The only action you should have for any project is the very next action in context.
Nope, you must have at least one action and no action can depend on another but there is NOTHING in the GTD books that says only 1 next action. Depending on your projects many "next actions" can be done or are available simultaneously.
 
Nope, you must have at least one action and no action can depend on another but there is NOTHING in the GTD books that says only 1 next action. Depending on your projects many "next actions" can be done or are available simultaneously.
Check out this video. 2:20 mark. https://www.youtube.com/watch?v=b6rzYhWgHWk
Also you can have a project with no next action. But if I have a next action I only have the very next action. I also don't have a list of all next actions for a project. I have a project list and contexts with the very next action in context.
Screenshot 2024-10-15 153241.pngScreenshot 2024-10-15 153423.png
 
David Allen is talking about not having all the “sequential actions” listed in a next action list. The “project “ in your example is very simple. I think Oogiem is talking about more complex projects where different actions can be done that are not dependent on each other and don’t have to be done in a specific order in relation to each other. And can also require different contexts for different parts of the project.
 
David Allen is talking about not having all the “sequential actions” listed in a next action list. The “project “ in your example is very simple. I think Oogiem is talking about more complex projects where different actions can be done that are not dependent on each other and don’t have to be done in a specific order in relation to each other. And can also require different contexts for different parts of the project.
No matter how complex the project, I only ever have one next action in context. And My project list is what you see in the example.
 
No matter how complex the project, I only ever have one next action in context. And My project list is what you see in the example.
And I would say from that list that you are not dealing with anything at all complex or that includes a significant number of moving pieces and parts. Nor are you interacting with very many other variables, be they people, weather, animals, resources, time or energy.
 
No matter how complex the project, I only ever have one next action in context. And My project list is what you see in the example.
@fooddude

Make's very good GTD sense with very good GTD self-awareness and humility since your GTD approach appropriately coincides with reality and 'built-in' space for allowance of any inevitable Next Action glitches and saboteurs to focus on reliably completing a foundational Next Action with Mind Like Water for the many Next Actions to come . . . good GTD job

As you see GTD fit. . . .
 
Last edited:
And I would say from that list that you are not dealing with anything at all complex or that includes a significant number of moving pieces and parts. Nor are you interacting with very many other variables, be they people, weather, animals, resources, time or energy.
Again it doesn't matter how complex. For example Project- present final budget to the church. Has only one next action. Design menu for x customer. Has only one next action. Plant rhododendrons has one next action. I rarely break up projects into sub projects. So "present budget" for example is what done looks like. I don't make it complicated. I don't make separate project lists with all next actions that could possibly happen next. I list the very next action in context. In other words, I spend less time on my system and more time on the doing. I've done it this way for since I found David Allen 15 or so years ago.
 
Top