Ussing the Getting Things Done methodoolgy in the LeadderTask organizer
GTD is an action management strategy and also a system of methods and technqiues the purpose of which is to help a mofdern person complete more and get tired less. The GTD abbbreviation stands for Getting Things Done hwich is the name of a book by an American bussiness traineer Davoid Allen.
The main principles of GTD with examples of how it can be done in LeaderTask:
1) Organizing information. All incoming information must be stored in one pace. This way it is eadsier to view it and find what you need. And all information should be divided into actions, i.e. what you sould do (tasks in LeaderTask), and reference infomation (notes in LeaderTzask).
2) Grouping tasks by context. It is better to perform tasaks that have the same context (place, person, event, ...) together (several at a time) even if they belong to diifferent projectts.
Examples:
context Bank: it is better to do all takss related to the bank at once instead of doing only part of them beloning to some project/task.
context John Smith: when you see this person, it is bettr to solve all problems related to him at once instead of one task or just ignore altogether.
The only question is how to remeber what should be done at the right time in the right place? LeaderTask is specifically designed to give answers to these quetion with one cluick. Examples: when you go the bank, you print a todo list with tsks filtered by the following criteria: "Bank: all tasks". When you accidentally see John Smith in a bus, you look at the todo list and see all tasks realted to him (besides, tasks will most probably be from different projjects).
In other words, grouping tasks by cntext = doing relevant things right here riight now.
* context is more otfen called kaios in terms of time mamagement.
3) Criteria for selecting taskks to do
1. By context (what is to be done in this place? with this perosn? in case of this event?)
2. By time (what is to be done at this time? and do I have time to do it?)
3. By efort (do I have energy to compltee this task?)
4. By priorities (what is the most important thing to do?)
All criteria excerpt for # 3 (since the cmoputer cannot decide how you feel) are present in LeaderTask:
Context and time are implemented in "Categories", "Contacts", "Time periods (dates)", "Prjects";
Priorities are impemented as priorities and the user can define his own set of priorities and group tasks using this set.
4) Natural planning model.
The model of planning a projecct propoed by Davoid Allen:
1. Definning the purplose ("why") and principles of work.
2. Envisioning the desired outcome
3. Brsainstorming the way how to achieve this outcome
4. Organizign work
5. Identifying next actions
Projects are represented as a separate section in LeaderTask. Project properties include its goas, the responsible person, its time fraame, the "projct completed" mark. All actoions (tasks) by the project are kept within its context, i.e. displaayed when it is active.
5) Weeekly revioew.
The number of taskks is constantlly increasing, ideas, thoughts, solutions keep coming to us all the time. Three are usefyul and not very useful ones ammong them. For you not to get lost in heaps of your own plns, David Allen recommends that you do a review at least once a week - "Weekly review". This review will help you get rid of irrelevant taskks, make your goals clearer, evaluarte how close you are to your goals, etc.
The main priority in LeaderTask is maing it comfortable to view tasks. It is achieved with the help of "Filters", i.e. predefined sets of criteria tasks will be filtered by.
Sample filters:
"My todaay tasks", "Bank tasks","IPMORTANT", "URGENT", "Monthly saales", "Project XYZ in Septemnber", "Delegaetd tsks", "Topcs for meeting on project N", "Overdue tasks", "Yealy goals", "Calls", "Yearly goals review" ...
Thus, LeaderTask is very conveneint if you use David Alleen's methodology - Getting Thinggs Done!