I'm not sure what the thinking with the templates is, but I'm guessing most people use them for ideas and then create or at least fine-tune their own system. If you are going to use the Android app, I would suggest you become familiar with it before you make final decisions on your structure and use-model, since some things are not as flexible on Android.
I have two kinds of contexts right now but it's really cluttered and I need to rework them. Generally I have @ contexts for the traditional meaning of contexts, and leave off the @ otherwise. For example, I have a context called "Routine" which I use sometimes to filter out or focus on my routine tasks. I find it to cumbersome to have my AoFs (Areas of Focus for anyone trying to follow) as both contexts and tree-structure, and because sometimes I move tasks around in the tree, I don't want them to start "collecting" inherited contexts so I only use the tree structure for AoFs. However, I did change recently to have each of my AoFs be both a folder and a Project. I don't use MLO Projects nearly as much as I "should" for GTD...I just don't think my brain works that way -- to me a project is something bigger than breaking down an amorphous task into subtasks. By having them be Projects, I effectively have a view on Android that is "tasks by AoF and major project". For a while I had a @Project context, which was my way of indicating that a task needed to be broken down into actions. Maybe @Process would be a better name. I may go back to that if I can discipline myself. One reason this worked well is that if I had broken the task down into actions, the @Project parent wouldn't show up as active, but it would if I hadn't acted on it yet. My advice is, have fun finding exactly what works for you. I find it works well for me to have my system be dynamic, and changing how I organize / process / use features every so often. It keeps my system fresh and new (kind of like buying new organizational supplies :), so I tweak it/ rearrange it / etc. That I can do that, is one of the things I love about MLO. Lisa On Sat, Jan 28, 2012 at 9:50 AM, rlw <[email protected]> wrote: > > > On Jan 26, 10:02 pm, Rob <[email protected]> wrote: >> > What is the thought process which has some MLO GTD templates have AoFs >> > with tree structures of subtasks and projects, and other templates >> > that have top-level AoFs and then have subtasks of @contexts/places, >> > and one project subtask? And all the AoFs have the same list of >> > @contexts/places in each one? >> >> I think this is mostly a demonstration of how you can slice & dice your >> tasks any way you want. -- Lisa ________________________________ Lisa Stroyan, mailto: [email protected] -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
