Four fold model
I agree that grouping tasks by context is clever. I use it quite a lot. It gets me to take advantage of the context to get some things done, no doubt.
Originally Posted by bcmyers2112
That being said, I believe the 4 fold model it's too reactive. And I think it is what most of my clients find difficult to implement, because it's difficult to trust. If you have your systems really complete with lots of tasks, when you browse it by context, you keep seeing things that are totally secondary, along with ultra-important things. You may have "make_50.000$_urgent_transfer" next to "browse_possible_web_sites_about_music", just because there are @computer+net. And they find that quite suspicious in terms of guidance.
I recomend separating the global repository and the guidance_sheet. The first has everything, is complete and easily browsable, enabling trustful selections. The second, valid for a certain period of time, has only whats pertinent for that period. After constructing the guide, the rest of the repository should disappear for a while. That also enhances the feeling of completeness (if you make a shorter to-do-list you can hope to get it all done).
Gonšalo Gil Mata