A friend of mine offered a slight modification to this model. Instead of using Tags to categorize windows of completion, just use the more absolute completion date... but.. then use Tags as a way to capture expected duration (ie: 15 minutes, 1 hour, 1/2 day, full day)
This way, one could filter choices and select either a "big" task or a set of "small" tasks for a long period of time. Conversely, if you only have 30 minutes to kill, filter down to those things that are expected to be quick hitters. Any thoughts from others? On Dec 27, 8:55 pm, JC <[email protected]> wrote: > I am a new user of ToDo for the iPhone. > > I would like to see a discussion about how different folks use the > feature set of ToDo. > > Here is what I am currently doing (but interested in hearing others): > > I have exactly two Lists: Personal, Work. > I use Context only for things in the lists that must be done at a > location: Home, Office, Shopping. > I use Projects for any Task that is "big" and seems to naturally be > broken into sub-Tasks: Clean Garage (clean/organize tool workbench, > clean/organize shelves, clean/organize cabinets)... This also includes > "steps" in a Task that might require some dependent step to be done > before I can do my next step which is a separate discussion thread I > have seen recently. > I use Tags two different ways: 1) to identify long running topics of > activity: Financial, Strategy, etc.... and 2) as a way to identify > temporal activities w/o actually setting a due date: Today, This > Weekend, This Month, This Year, etc. > > I have only been using ToDo for about 10 days, but currently have > about 170 tasks entered, following the model above, and it seems to be > both easy to enter and easy to find focus topics for action. > > Example: Personal items, while Home, limited to Financial before Year > End. > Example: Personal items, while Shopping. > Example: Work items, no particular context, focused on Strategy items > with no particular due date. > > Some other observations: > > Very few tasks have a Context (ie, I can do a lot of work from home), > but Context, *is* critical when its "right". > (ie: I cannot repair my home computer while at Work, but must be @ > Home). > > By using Tags as a way to categorize time, I don't have to pick a > specific day, but can set a "range" of time for a task. > > By using Tags for long running topics, they tend to be a little like > projects, but the difference is there are always Tasks coming and > going within the Tagged topic (e.g. Financial Planning, Landscaping, > etc.) > > By breaking "big" tasks into Projects, I can make progress, and I can > also wait for external dependencies to be accomplished before > completion (e.g. Paint House -> Request Bids; <external dependency > waiting for bid responses>; Review Bids; Select Painter; Schedule Job; > Prepare Landscaping; <external dependency waiting for painter>; > Paint). Note: I don't enter the external dependencies.. they just > seem natural in the sub-tasks. > > Comments welcome. Would also like to see similar write ups with > other models that folks have come up with. -- Learn more about Todo (task management made simple), Corkulous (collect, organize, and share your ideas), Notebook (notes available everywhere), and AccuFuel (fuel efficiency tracker) on Appigo's website: http://www.appigo.com/ You received this message because you are subscribed to the Google Groups "Appigo Todo" 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/appigo-todo?hl=en
