Leaving specific next action undefined

[AGrzes]

For some of my tasks I find that defining next action ahead of time does not work right. It is usually with creative tasks with multiple possible approaches I'm on one state of mind and I'm excited about one approach when planning but this does not feel so right after I get back to actually performing the task few days later.

Do you see drawbacks with in putting such thing on action list without decision on next action and only note possible approaches in support materials?
Lets assume all ways to approach task require the same context and as task is complex each require non-trivial amount of time and energy.

Sample task would be for example "Refine scenario for upcoming RPG session" or "Implement new project format parsing for personal GTD system".

 

[Oogiem]

Sample task would be for example "Refine scenario for upcoming RPG session" or "Implement new project format parsing for personal GTD system".

What about those makes you think they are not next actions?

I've got a bunch of actions like that right now in my system.

For example:
Create queries for my belt pouch lists in LambTracker - There are many things I could do and several approaches so that is the placeholder to get me started.

Design tables for EBV dates and ranges in LambTracker database - again a big part of the task will be to decide on an approach. There are several waysd I could do it and I am not yet sure which way will work better for me.

Complete UI design of official scrapie reports in LambTracker

So I think your act are fine as they are. ions

 

[Folke]

AGrzes, I agree with Oogiem. I often think of these as "single-line projects". Just as you say, this often happen with creative tasks. I can also happen with explorative and iterative tasks and with tasks that are very familiar territory, even if they are quite big. What I often do though, is move them from one context to another along the way, if I notice that the next unwritten step will require that. I think probably the key factor is whether I think I will be better off writing down the individual actions or not. Often it is worth it, of course, but often I feel it would be unnecessary or even restrictive and counter-productive.

 

[mcogilvie]

For some of my tasks I find that defining next action ahead of time does not work right. It is usually with creative tasks with multiple possible approaches I'm on one state of mind and I'm excited about one approach when planning but this does not feel so right after I get back to actually performing the task few days later. Do you see drawbacks with in putting such thing on action list without decision on next action and only note possible approaches in support materials? Lets assume all ways to approach task require the same context and as task is complex each require non-trivial amount of time and energy. Sample task would be for example "Refine scenario for upcoming RPG session" or "Implement new project format parsing for personal GTD system".

I usually prefer to put a specific next action in place, but I don't hesitate to throw it away if a better approach suggests itself in the moment. Of course, "Brainstorm actions" is itself a valid next action.

 

[JamesT]

I usually prefer to put a specific next action in place, but I don't hesitate to throw it away if a better approach suggests itself in the moment. Of course, "Brainstorm actions" is itself a valid next action.

I think mcogilvie has hit the nail on the head here. Even in the cases where you don't know exactly what the specific next physical action will be in the future, you can still write the next action in a way that tells you what you need to do, when you are ready. The next action may very well be to "think through the correct approach for upcoming RPG session" To help capture and preserve the mood you were in while creating the action, you could maybe jot down some notes about the idea in the notes section of your task.