Hi Guys,
I am looking for any Doit.im example projects so that I can get my head around and better understand how to use tasks, subtasks in projects with contexts,dates, tags etc -
I am pretty sure I can streamline my own workflow if I have exposure to some example/template projects to get the brain juices flowing :)
Any ideas would be greatly appreciated.
Matthew
Personally I make use of the full four-level hierarchy Goals-Projects-Tasks-Subtasks.
I use Goals both for really big "super-projects" (GTD 30 k objectives) and as "Areas" (GTD groups of areas of responsibility): http://help.doit.im/group/topic/92
I have 5 such Goals all in all at the top level (3 areas and 2 super-projects)
I use Projects both for medium/small projects (GTD 10 k) and as "permanent containers" for single actions in a given area of responsibility (GTD 20 k): http://help.doit.im/group/topic/60
I have a few dozen such Projects (10 AoR single task containers and a few dozen completable projects)
I use Contexts for being able to group my lists into the five most essential types of requirements that tasks can have for being possible for me to do:
@Person (requires real-time interaction by phone or face to face)
@Out (requires me to leave by Base location)
@Reflection (requires a particularly calm and clear state of mind)
@Base (requires certain tools, documents etc only available at home/office etc)
@Device/Anywhere (requires almost nothing except my hands, brain, wallet, smartphone etc)
http://help.doit.im/group/topic/23#comment-25
I hardly use Tags at all, because they are not visible, so I cannot trust my own tagging.
I use dates only for "objective" ("external") things, not for doing any planning or setting up targets etc. This is in line with GTD. I keep my appointments etc (GTD calendar actions) in my regular calendar. My Doit "scheduled" dates all represent "the earliest possible objective date" that a task can even be considered (GTD tickler file item), for example to buy the new phone that will be released only on Oct 1. I have many dozen repeating tickler actions listed, e.g. to review/cancel all kinds of contracts, subscriptions, maintenance etc etc. The same objectivity principle applies to due dates (deadlines) - I enter any or all stipulated deadlines that I consider as "external facts", e.g. xx has promised to do X if I do not do Y by the (deadline date). This date has only an indirect bearing on whether I will do the task or not, or when. GTD style, I continually use my judgment to select what I will do, and sometime use dates, if any, as a guide. And I consistently use the Priority field as my main guide. It helps me mark and locate those tasks that I do not want to overlook when I select tasks to do, and vice versa: http://help.doit.im/group/topic/55
I use subtasks especially for such subtasks that can be seen as checklist items for the task. They are very useful for this purpose. I have such checklists in many of my repeating ticklers, and even for listing groceries to buy. Using Tasks+Subtasks for regular projects is not equally useful, since you cannot attach any attributes, such as context requirements, for the subtasks.
I use Goals both for really big "super-projects" (GTD 30 k objectives) and as "Areas" (GTD groups of areas of responsibility): http://help.doit.im/group/topic/92
I have 5 such Goals all in all at the top level (3 areas and 2 super-projects)
I use Projects both for medium/small projects (GTD 10 k) and as "permanent containers" for single actions in a given area of responsibility (GTD 20 k): http://help.doit.im/group/topic/60
I have a few dozen such Projects (10 AoR single task containers and a few dozen completable projects)
I use Contexts for being able to group my lists into the five most essential types of requirements that tasks can have for being possible for me to do:
@Person (requires real-time interaction by phone or face to face)
@Out (requires me to leave by Base location)
@Reflection (requires a particularly calm and clear state of mind)
@Base (requires certain tools, documents etc only available at home/office etc)
@Device/Anywhere (requires almost nothing except my hands, brain, wallet, smartphone etc)
http://help.doit.im/group/topic/23#comment-25
I hardly use Tags at all, because they are not visible, so I cannot trust my own tagging.
I use dates only for "objective" ("external") things, not for doing any planning or setting up targets etc. This is in line with GTD. I keep my appointments etc (GTD calendar actions) in my regular calendar. My Doit "scheduled" dates all represent "the earliest possible objective date" that a task can even be considered (GTD tickler file item), for example to buy the new phone that will be released only on Oct 1. I have many dozen repeating tickler actions listed, e.g. to review/cancel all kinds of contracts, subscriptions, maintenance etc etc. The same objectivity principle applies to due dates (deadlines) - I enter any or all stipulated deadlines that I consider as "external facts", e.g. xx has promised to do X if I do not do Y by the (deadline date). This date has only an indirect bearing on whether I will do the task or not, or when. GTD style, I continually use my judgment to select what I will do, and sometime use dates, if any, as a guide. And I consistently use the Priority field as my main guide. It helps me mark and locate those tasks that I do not want to overlook when I select tasks to do, and vice versa: http://help.doit.im/group/topic/55
I use subtasks especially for such subtasks that can be seen as checklist items for the task. They are very useful for this purpose. I have such checklists in many of my repeating ticklers, and even for listing groceries to buy. Using Tasks+Subtasks for regular projects is not equally useful, since you cannot attach any attributes, such as context requirements, for the subtasks.
