When processing something in the Inbox and realizing it should be part of a new project, I simply type the project name into the project field and press cmd+enter to create it at the bottom of the projects list. I have noticed a cognitive overhead having to think about filing each time a new project is added, which is why I simply refrain from doing that. Adding Projectsĭuring my weekly review, which I will discuss in detail later, I make sure to file projects under their respective area of responsibility. For your situation, professional areas could instead include “Development”, “Infrastructure”, “Support”, or maybe only having “Current Clients” if you are managing a lot of customers and their respective actions. It all depends on your roles, so these examples should be seen as guidelines. Professional areas of responsibility could include: For my personal role, some of the areas can include: The next level within these role folders contain areas of responsibility for the particular role. For me personally, it makes sense to define separate trees for my different roles in life, one for “Personal” and one for “Unomaly”, where I currently work. You’ve got to think about the big things while you’re doing the small things, so that all the small things go in the right direction.Ī central part of setting up OmniFocus is defining the projects list in a way that makes sense for you. Instead of letting work be defined by others, you are defining your work to be aligned with your goals. This is where you start to define goals and pave a path ahead. The last part is about looking upwards and onwards to the bigger things than the daily grind of going from task to task. The second part is the implementation step where the author David Allen guides you through the big task of setting up your own GTD system from scratch. The book is fairly short and is divided up into three parts, where the first is mostly about the underlying theory and why it works. If you are not already familiar with the Getting Things Done methodology, I strongly suggest that you to read the book before implementing the things I mention here. Since my GTD setup is an ever evolving organism, this can only be seen as snapshot in time for when this article is written, and the real changes will be visible when I write the 2017 edition of this very post and highlight the differences. Direct support for this functionality, as well as support for additional OmniFocus 4 features and design updates, will be made available in future test builds of OmniFocus for the Web.I have written countless posts on OmniFocus and the Getting Things Done methodology, but this is the very first time I have gathered my entire workflow and setup into a single piece. Preserve project and action group hierarchy in perspective outline.Ĭurrent test builds of OmniFocus for the Web support these features when enabled in a synced TestFlight build of OmniFocus 4, however it is not yet possible to enable or disable these options from within OmniFocus for the Web.Support for manual sorting in custom perspectives with flexible outline structure.Optionally hide items in On Hold projects.Flexible outline structure with support for displaying a “unified” list of Forecast items, and options for manual sorting and hierarchical project and action group display.Display additional types of items, like flagged items and items with Scheduled Notifications.OmniFocus 4 TestFlight participants who also use OmniFocus for the Web can now try out these test builds, which support the following synced features when they’ve been enabled in a TestFlight build of OmniFocus 4 on Mac, iPhone, or iPad:
0 Comments
Leave a Reply. |