@Robisme Hmmm. Not a bad idea... I definitely haven't mastered Goals, although I had made an initial stab at them... using the Goals field(!). So my Goals field isn't completely available.
I am thinking however that it would seem more logical to use the Flags field which I do not currently use for anything else. The only thing that is holding me back is that I tried using flags about 9 months ago, but didn't get on with them. However I cant quite remember what went wrong. To get clear, I am looking for something to change the state of any given entire MLO project (of if the task is not inside a Project, then just the task itself) moving them to just one of the states A B C or D. I guess I could then create an MLO View for each of the flag statuses (i.e. A B C or D)... :^/ On Monday, 28 March 2016 19:21:13 UTC+1, robisme (Olivier R) wrote: > I think that if you keep with your idea, perhaps could you make a good use > of the "goal" field, which is very convenient to switch, and only assign > them to your head projects, not the subtask. > You could also use flags, with the disadvantage that they are currently > not editable on mobile app. > > A. "SOMEDAY MAYBE = no goal > B. "NOT YET" = yearly goal > C. "DO ASAP" = weekly goal > D. "DELEGATED / TICKLER" = monthly > > Olivier > > > Le lundi 28 mars 2016 16:36:43 UTC+2, J Smith a écrit : >> >> I am barely using Context at all. I find MLO Contexts are too time >> consuming to enter for small stuff. AND to be completely honest I don't >> really know how to use them. >> >> I mean yes I do use "errands" and "reflective mood" and "low energy" and >> "frog". >> (To explain, "Frog" refers to "anything I have put off a number of times" >> and which therefore needs doing soon in order to avoid it becoming much >> harder. I allocate specific times - generally at the start of a working do >> and/or at the end of a working weak - to tackle "high resistance" stuff >> that may have started to pile up. More: >> http://eatthatfrogbook.com/eat-that-frog-what-does-it-mean/ ) >> >> ...I may be missing something but apart from those Contexts I have not >> found Contexts to be very useful, due to the time it takes to enter them. >> >> >> >> On Monday, 28 March 2016 00:08:59 UTC+1, Elizabeth Lindsay wrote: >>> >>> It looks like everyone has already given you good answers. The key I >>> think to GTD is to structure your list by project (as David Allen defines >>> them) and not by context. Then tag each item in that project with the >>> appropriate context. In MLO, you can filter your views by context etc. >>> You can also had estimated times (to help with finding short tasks to fit >>> in time blocks). This makes it pretty easy for me to use. >>> >>>> >>>> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/3096610f-a7a5-469e-b0e2-c7dfbd8deb58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
