Areas of responsibility versus Someday/Maybe
I've tried to have areas of responsibility and found out that many(if not all) the Someday/Maybes fit into those areas. This is because those areas fill all what I do and want to do.
An example: "buy 2GB of RAM for server" is a project that would fit into the "responsible with server" AoR. However, I tend to see at this moment this project as a Someday/Maybe because I have no intention the next week/month to actually buy the RAM.
Another example: "create a personal blog" is a project that would fit into the "web master" AoR. This project is something that I don't want to think about now because it is not an active project. So normally I'd put this project in Someday/Maybe list, which I've split into 3 parts depending on the priority of the tasks in it. On a later review, I might decide that it is time for this to become an active project.
If I'd put all these items into AoR, then the review would become something very painful because I'd have to review all items even if at this moment they're not so important for me. In Someday/Maybe, since it's just a big list, I can move and prioritize items that would someday become active in my project list.
So if I'd put items like this into AoR, the Someday/Maybe would go down to zero.
Please explain the difference between AoR and S/M. What do you do with the projects in AoR that are not a priority at this moment?
Tags for this Thread