gtdstudente
Registered
With further reflection, would you also agree a Someday/Maybe list is by definition a Pre-Project list . . . at least potentially ?
With further reflection. . . .
- Thread starter gtdstudente
- Start date
Grinzecat84
Registered
I would agree that a Someday/Maybe list could be a sort of pre-project list, just as it can be a list of individual actions for someday.
Maybe.
My Someday/Maybe list certainly has some pre-projects that I could transplant onto my project list. It has other things that are waiting to crystallise in one form or another.
Some of them are fragments. When I am planning a project, I might use them as part of the project. You could classify these as pre-brainstorming.
Other things are just thoughts I have had. They weren't useful when I had them but they were interesting enough to keep in Someday/Maybe. Sometimes they evolve into something actionable.
My Someday/Maybe list certainly has some pre-projects that I could transplant onto my project list. It has other things that are waiting to crystallise in one form or another.
Some of them are fragments. When I am planning a project, I might use them as part of the project. You could classify these as pre-brainstorming.
Other things are just thoughts I have had. They weren't useful when I had them but they were interesting enough to keep in Someday/Maybe. Sometimes they evolve into something actionable.
gtdstudente
Registered
@cfoley,
Agree . . at the same time, as never before, using Someday/Maybe as [pull] inventory list seems to also help to keep the Project as [push] inventory list as a more honest commitment list even when it has a Next Action since the Someday/Maybe list can also have a Next Action with a 'lesser commitment' than that which is on the Project list
Someday/Maybe also used as a "pre-brainwashing" list, much like pre-project list, to better 'safeguard/upgrade' the Project's lists' attractiveness for trust-quality . . . very vice . . . thank you very much sir
Shady Waxwing
GTD Connect
For me, there are no Someday/Maybe list items that are 'lesser commitment.' Someday/Maybe items are all no commitment.
I must know what I am already truly committed to when I'm clarifying new inputs.
gtdstudente
Registered
@Shady Waxwing,
Totally appreciate what you are expressing . . . at the same time on this end a technique was needed as way to prevent items from 'rashly' going onto the Project list that fell short of being a current/proximate 'all in' Project without wasting deliberative energy and, as such, Someday/Maybe facilitated that space necessity as a 'Pre-Project' nuance without adding any additional complexity to the GTD system.
As such, it also helps to prevent the Someday/Maybe items becoming stale as well as Project items from becoming overwhelming
Thank you very much
As you see GTD fit. . . .
Shady Waxwing
GTD Connect
For those who may be new to GTD, the Someday/Maybe list gives you more freedom. You're free to move items onto the Someday/Maybe list that you originally committed to but are now renegotiating. Or activate projects when you are ready. Using it at as list of partial commitments will limit its value as a place to store creative ideas.
In GTD clarifying, you decide if an item is actionable or not. The "maybe" option is still deciding no, at least no for now. That leads to the choices for incubating the item in a tickler file or the Someday/Maybe list.
If deciding yes/no is hard, go up to higher horizons, areas of focus or even life purpose. Don't fudge with a list of partial commitments that mask the deeper issue that you could be committing to more than you can handle.
In GTD clarifying, you decide if an item is actionable or not. The "maybe" option is still deciding no, at least no for now. That leads to the choices for incubating the item in a tickler file or the Someday/Maybe list.
If deciding yes/no is hard, go up to higher horizons, areas of focus or even life purpose. Don't fudge with a list of partial commitments that mask the deeper issue that you could be committing to more than you can handle.
gtdstudente
Registered
@Shady Waxwing,
What if all . . . "higher horizons, areas of focus or even life purpose" . . . are humbly, gratefully, appropriately, and completely embedded in Areas-of-Focus to date without numbness, deliberation, and optimal clarity . . . then what ?
Thank you very much
Last edited:
Shady Waxwing
GTD Connect
Then good. Until something indicates those horizons need another review, like blending what's on the lists.
It's not a best practice to have blended lists of actionable and non-actionable items. The Someday/Maybe list is for non-actionable items. If there's an actionable item there, or something with partial commitment, then there wasn't a clean yes/no to the question, "Is this actionable?" If it's hard to say yes or no, asking why a few times often reveals the real issue, likely at a higher horizon.
gtdstudente
Registered
@Shady Waxwing,
Is it possible to have a Next Action for a listed item on the Someday/Maybe list since it is unable to be moved to the Project list because it lacks a complete commitment for completion while remaining on the Someday/Maybe in order to GTD forget about the item?
Thank you very much
Last edited:
FocusGuy
Registered
Yes a kind of Pre-Project list. But non only. My own practice of GTD is to put into someday may be list one item at a time everything I intend to do in the future. I use to be very strict with this and divided the list into different other lists. It was a mistake.
Now I put every thing in the future except dated items which goes into my diary or if it is physical into my tickler. I put a ? infant of anything I dont know if I will do or not.
The most important is to review this list (quickly) every day when I prepare my next day for avoiding stuff falling into the crack.
Now I put every thing in the future except dated items which goes into my diary or if it is physical into my tickler. I put a ? infant of anything I dont know if I will do or not.
The most important is to review this list (quickly) every day when I prepare my next day for avoiding stuff falling into the crack.
gtdstudente
Registered
@FocusGuy,
Yes . . . leaning how the Someday/Maybe list and Tickler file are actually compatible GTD 'tool buddies' for Weekly Review and Reflection . . . together they each and both offer extra GTD 'muscle' to all trusted GTD systems
And how invaluable Someday/Maybe list and Tickler file can be in preventing 'list proliferation' . . . huge!
Thank you very much sir for offering your GTD acumen . . . most appreciated
Last edited:
Shady Waxwing
GTD Connect
I guess you could. I would instead add it to the project as a note. If I ever reactivate the project, that item may no longer be a next action. I would definitely not move a project to Someday/Maybe and leave a next action for it stranded on a next actions list.
gtdstudente
Registered
@Shady Waxwing;
Thank you for for well thought out reply
The following is to be kindly understood as respectful reply for better GTD:
1. "add it to the project as a note"
The concern here is what prevents the Project list from being inundated with "project as a note" with each one possibly requiring repeatable excess deliberation(s) when Reflecting or Weekly Reviewing?
2. "If I ever reactivate the project, that item may no longer be a next action." With all due respect, seeming unclear
However, respectfully, if there is some degree of understanding to what is being expressed . . . so what . . . no biggie . . . just chuck the Next Action item and move on to greener pastures?
3. "I would definitely not move a project to Someday/Maybe and leave a next action for it stranded on a next actions list."
A 'stranded' Next Action or better still only 'stranded' Next Actions on Contexts list this end sounds like GTD nirvana, since this would imply no Open-Loop in regards to Projects and all Next Actions are the only existing Open-Loops . . . sign me up . . . I'll even take two
Whether the above has any GTD value is left up to you or any reader, my only hope is that it is understandable
Thank you very much
As you see GTD fit. . . .
Thank you for for well thought out reply
The following is to be kindly understood as respectful reply for better GTD:
1. "add it to the project as a note"
The concern here is what prevents the Project list from being inundated with "project as a note" with each one possibly requiring repeatable excess deliberation(s) when Reflecting or Weekly Reviewing?
2. "If I ever reactivate the project, that item may no longer be a next action." With all due respect, seeming unclear
However, respectfully, if there is some degree of understanding to what is being expressed . . . so what . . . no biggie . . . just chuck the Next Action item and move on to greener pastures?
3. "I would definitely not move a project to Someday/Maybe and leave a next action for it stranded on a next actions list."
A 'stranded' Next Action or better still only 'stranded' Next Actions on Contexts list this end sounds like GTD nirvana, since this would imply no Open-Loop in regards to Projects and all Next Actions are the only existing Open-Loops . . . sign me up . . . I'll even take two
Whether the above has any GTD value is left up to you or any reader, my only hope is that it is understandable
Thank you very much
As you see GTD fit. . . .
dtj
Registered
In my mind, it could be a pre-project, but it would be a fully formed project, or anything in between. I have “fully” fleshed out project that hit SomedayMaybe due to things changing (aka “Overtaken By Events”) like new priorities. I try and maintain atleast some sense of order, like bunches of undeveloped snippets get migrated under a high level domain like “Home” or “Work”. Rather than like 95 un-moored snippets in one pile.
gtdstudente
Registered
@dtj,
Perhaps the Someday/Maybe list could also be deemed a list that also includes "Potential" Projects, Contexts, etc. with 'Potential' as the operative word to keep the Projects, Contexts, etc. list all the more 'crisp-&-fresh' which would also seem to be helpful in turning down potential Project, Contexts, etc. list(s) numbness/overwhelm if ever a concern?
Thank you very much sir
Bottom GTD line for the Someday/Maybe list . . . a 'place' list for anything that might have any degree of attention/interest that stands guard to prevent all other lists from becoming loathsomely unattractive ?
Seems like some like their Someday/Maybe list to be part of their Weekly Review while some prefer less frequent
As such on this end, for many GTD reason, include the Someday/Maybe list on the Weekly Review as a less-stress 'Pull' list to better serve the more engaging Project, Contexts, ect. 'Push' lists and the Someday/Maybe list can end up actually helping all week by keeping the engaging lists all that much more engagingly clear if that makes any GTD sense?
As you see GTD fit. . . .
bcmyers2112
He does the hokey pokey
Someday/maybe items are items you have no commitment to at the moment. The list can include things you know you'll want to commit to at some point (someday) and ones where you're not sure if you're going to commit (maybe).
If you have an active project with one or more actions you're not sure about, the best place to put them is in project support rather than someday/maybe. That way you can see them every time you review the project. If the timing is right to consider turning one of those potential actions into a next action and it's not your weekly review time, you might forget to look in someday/maybe.
If there are no actions associated with that project that you're willing to commit to, the entire project belongs in someday/maybe.
If you have an active project with one or more actions you're not sure about, the best place to put them is in project support rather than someday/maybe. That way you can see them every time you review the project. If the timing is right to consider turning one of those potential actions into a next action and it's not your weekly review time, you might forget to look in someday/maybe.
If there are no actions associated with that project that you're willing to commit to, the entire project belongs in someday/maybe.