![]() Prefixing tasks with a “mindset” such as “READ:” or “WATCH:” can also help you define your tasks by mode as well. There are due dates and flags to indicate urgency or importance and durations to indicate quick wins or when you’re looking for something to do during a set period of time. ![]() On paper it makes sense to define these various lists to drill down to what you can work on at any given moment, but if you use something as powerful as Omnifocus, there are more options available to you for this than just contexts. The problems tend to creep in when you start to factor in other things like energy levels, time available, or urgency. No matter how much I wish it were true, there’s simply no way I could get my shower cleaned while I’m at work. II need to be at home in order to clean the shower in my bathroom, so “home” is a great example of a context. In its purest form, a context is a tool or location. The age old answer of “It depends” truly applies here. That being said, a few things stand out for me when I look at those long lists of contexts that people have. How many should you have? What should they be? How many is too many? A quick look at the countless methods being discussed in the Omnifocus Forums show that there is no single right way for picking contexts, and when you consider the possibility of a task having multiple contexts (not currently possible in Omnifocus), it gets more complicated. ![]() ![]() Contexts seem to be a point of contention when it comes to any GTD system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |