Let’s set aside any discussion of how ridiculous it is to be attempting so many discrete activities. For example, I basically have five different domains in which I live: my Guard job, my University job, finishing my dissertation, blogging at Productive Flourishing, and consulting via Productive Flourishing.
I need to articulate and think about my position a bit better, as it may turn out that I’ve ingrained GTD-ish principles that make lists redundant. But I’m so interested in the dialogue that I’ll put concerns of incoherence aside. Now’s probably not the best time for me to respond, as I’ve been having trouble writing this afternoon. It made logical and intuitive sense that looking at a list of 13 next actions is easier than looking at a list of 130. I’ve always found that position curious, since context lists were one of the first things I latched onto when reading Getting Things Done.
Omnifocus contexts examples how to#
In his post Using Context to Simplify List Management that’s partially motivated by a comment I left on his post When to Do Low-Priority Tasks, Andre brilliantly canvasses some possible problems people have with understanding and applying GTD principles and how to amend these problems.Ĭontext lists are popular within GTD, but some users are like Charlie: having multiple lists like and seems to create more work than it saves. This one’s not about the whole “ To shut off comments or not to” discussions – rather, it’s an example of how two bloggers keep conversations going.Īll that said, Andre and I have had several comments and posts back and forth over the last few months regarding some of the tenets of GTD and why some of us tweak or abandon the system. For those of you who worry that comments aren’t worth the trouble and that meaningful dialogues are a spectre of wishful thinking, I entreat you to take note of this blog post.
0 kommentar(er)
