So I am in the camp that the traditional GTD contexts are not terribly useful for me, so i am not planning to set things up using @office, @calls, etc. I rarely need to make a call, my "office" is the same place where I can do my personal computing work, and so on. Give that I freelance, I'm going to be switching between personal tasks and things I get paid to do, depending on the day.
I've struggled mightily with trying to blend GTD with keeping up with things little that I tend to forget about that change over time (the really low priorities) and I keep falling down. I think part of this is not getting the context idea down properly, which throws off projects, which throws off next, and so on.
The thing I was doing on Nirvanna--small number of projects, high number of contexts--probably was the wrong way to do it. But after no word for months, I didn't want to keep paying for high levels of projects. If they had said boo, I probably wouldn't even be trying something else. But I'd rather be in an imperfect place I trust than one that's just keeping up a front.
My thinking on contexts this go is to keep it limited and use more projects for when I am moving a task along. So instead of the project holding multiple contexts, it would be reversed.
I'm thinking of using the following to start. Most of my freelance work is with a certain set of clients, so I'd give each a context, so I can easily see what I am doing with that client at any given time (including next, scheduled, waiting, etc.)
-Client Name 1
-Client Name 2
-Other Clients (for one off assignments)
etc
The number of these contexts would change over time, but I think that would give me a clear picture of what I needed, rather than just @computer, where 90% of my client tasks would be anyway.
For personal stuff (like the website I run as part of a group, cleaning up my reading lists, and so on), I figured I would give the biggest ones a context:
-Reading
-Website Name
-Hobby
etc
This would allow me to quickly sort to the thing I wanted to spend some time on.
And last, the things that tend to be typical for anyone
-Shopping
-Chores
My question is--is this too fragmented? Would it just be better to go @freelance @personal @shopping @chores, then use projects to separate out? I liked Folke's 5 things, and I'm wondering if maybe that's a wiser course.
Thoughts appreciated.
We are all different. And that makes it difficult to give advice. But let me give you a few very personal and spontaneous reflections, that may have no relevance at all in your case:
I do not like to organize my stuff by "type of work" at all. I prefer a "role based" organization, even if they can be quite similar. For example, if a client is coming to discuss a purchase of my services and I need to make the table nice and clean, would I put that under "Cleaning" (i.e. the type of work)? No. I would put it under Salesman (a role). But if I clean my office on a routine basis, or following some major incident, I would put it under Cleaner (a role), In other words, I would split it up according to "who of me" (which role) is responsible for this initiative.
So, I would be wary of having contexts or projects or anything labeled "Chores", "Shopping", "Reading" etc.
I like my Contexts (and/or Tags) to reflect situational requirements necessary in order to be able to do a task, e.g. I need this person, or I need to be out, or I need silence or energy etc.
I like my higher hierarchical "do units" (project, goals, whatever) to be either completable "real projects" ("big tasks"), or purely role based general containers of smaller items. I like this mix. All tasks do not really belong in any real projects, and all projects do not really belong in any larger new objective, so my hierarchy would be very incomplete if I did not have the role based containers as a complement for those things that do not belong anywhere.
If I were you I would split up my client work primarily in such hierarchical containers, not as contexts. Well, in fact that is how I do it myself, and it suits me.
Do you do the same type of work for all your clients? Or do you have different types of roles for different clients? Do you do more work for some clients than for others? If I were you I would probably have separate folders at the appropriate level (e.g. project) for the larger clients, and more general (role based) containers for smaller jobs.
I do not like to organize my stuff by "type of work" at all. I prefer a "role based" organization, even if they can be quite similar. For example, if a client is coming to discuss a purchase of my services and I need to make the table nice and clean, would I put that under "Cleaning" (i.e. the type of work)? No. I would put it under Salesman (a role). But if I clean my office on a routine basis, or following some major incident, I would put it under Cleaner (a role), In other words, I would split it up according to "who of me" (which role) is responsible for this initiative.
So, I would be wary of having contexts or projects or anything labeled "Chores", "Shopping", "Reading" etc.
I like my Contexts (and/or Tags) to reflect situational requirements necessary in order to be able to do a task, e.g. I need this person, or I need to be out, or I need silence or energy etc.
I like my higher hierarchical "do units" (project, goals, whatever) to be either completable "real projects" ("big tasks"), or purely role based general containers of smaller items. I like this mix. All tasks do not really belong in any real projects, and all projects do not really belong in any larger new objective, so my hierarchy would be very incomplete if I did not have the role based containers as a complement for those things that do not belong anywhere.
If I were you I would split up my client work primarily in such hierarchical containers, not as contexts. Well, in fact that is how I do it myself, and it suits me.
Do you do the same type of work for all your clients? Or do you have different types of roles for different clients? Do you do more work for some clients than for others? If I were you I would probably have separate folders at the appropriate level (e.g. project) for the larger clients, and more general (role based) containers for smaller jobs.