There is no ‘One size fits all’ here. Your approach is sound and similar to how I group stuff but you will have to experiment to get what works for you.
It can take a year or so of ‘tweaking’ to get a workflow that is optimised for the way tasks hit you and the way your brain works. The weekly review is critical (alternatively randomise the review dates of projects and do a couple of reviews every day)
Until omnigroup get round to fixing the search (which isn’t a search, but a filter) you have to set up the project view so that it is easy to navigate. The projects view is really for planning what has to be done. With contexts and perspectives for doing - the ‘what can I do now’.
I use folders to help me organise projects. For me the folders are areas of focus (my various businesses, plus house, and self) There are some projects that don’t sit in folders but are ‘loose’ in the list - that works for me. I know there are people who have a folder for all the ‘loose’ stuff. There is a businesses that has two folders (I have two ‘hats’ in that business.)
I only have single level folders (I don’t nest them, though this is possible)
Within the folders I have my projects. There is frequently a single action list for an area of focus (which contains the Just do it actions). Everything else is a parallel or sequential project.
All too frequently within parallel or sequential projects there are blocks of tasks that should be grouped. Pressing cmd-] will indent an action and create a group. These groups can be set to parallel or sequential themselves (independent of their containing project or action group) and can be nested to give as much granularity as you need. I try to keep mine as small as possible. BTW cmd-[ moves actions to the left (out-denting). Groups can be expanded/contracted as needed.
It sounds like there may be routine 'steps in your work. There are some scripts (search the old forums and these ones for template script) that enable you to use Templates. I don’t have many duplicating projects any more, but when I did the template scripts held the answer. A full project outline was kept in a template folder and set to on-hold. When I needed to run the project again, I ran the script that prompted for all the appropriate info and made a new copy. All I then had to do was drag it into the right location in my structure.
As I had a ‘learning opportunity’ in a project I would update the template so that the task appeared automatically the next time that I ran a similar project.
As a final couple of bits of advice:
- Have as few steps/actions as you can get away with as this eases planning and completion of actions. For example ‘Get dressed’ is probably more efficient than ‘put on underpants’, ‘put on left sock’, ‘put on right sock’…
- If you can stretch to the expense, get and follow Kourosh Dinis’ book and purchase/watch the Macsparky field guide on omnifocus.
Hope this helps
