By dumping and forgetting you ensure every thought will be saved. The reason is that sometimes you will have many thoughts racing through your head and the last thing you want to happen is that you forget one of them. You want to get your thoughts in the inbox, not worrying about specifics, and deal with them later (in the processing phase, as explained later). The mentality behind capturing can be described as “dump-and-forget”. The goal is to get your thoughts in the inbox as soon as you have the thought, and not worry about whether the thought is actionable or not. CapturingĬapturing is the process of putting your thoughts into Omnifocus. After months of trial-and-error and researching other people’s Omnifocus workflows, I think I came up with a great solution that will be applied to our imaginary user Tom Jenkins. I will use this framework to show you a workflow that works with Omnifocus. Click here for more information.įor those who are unaware or forget the phases of the GTD system, here they are: It’s our guide that is simple, practical and it has a lot of field-tested workflows and solutions to help you use OmniFocus the right way. If you are looking for a shortcut to use OmniFocus the right and effective way, check out OmniFocus Premium Posts. I’ll show you can how you apply this with Omnifocus phase by phase. The phases of GTD align nicely for creating a workflow with Omnifocus. While I’m not a true GTD person, I do use the same framework. I’m really excited to share how I implement Omnifocus in harmony with the Getting Things Done(GTD) system of David Allen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |