Quote:
Originally Posted by dp1
That's an interesting idea. Since I'm just starting, and have no legacy overhead to convert, let's extend it a bit. What if I had no sub-contexts, but populated the note with whatever variables were appropriate? I would have one large context called Work, and could populate the note not only with sub-context tags, but with project tags, and anything else that might be helpful. &Boss, &Project X, &networking, etc. Do you see any downside to this approach?
|
I think this could end up biting you further down.
You can create nested contexts.
Work
-email
-computer
-agendas
-waiting for
Home
-email
-computer
This is how I separate my home from my work stuff. While not pristine GTD, work isn't paying me to do personal stuff and I'm not going to do work on personal time.
Contexts should be broken down to:
locations
tools you need
things you have access to (agendas: boss)
Projects should be organized by projects in the projects tab.
You can use folders in the projects tab to help separate projects.
If you need to focus on one project then use the focus command to only see that project, and only that projects actions will be in the contexts.
You can also focus on a folder and only see projects within that folder.