Since I really wanted the electronic Palm based system to work I've got a few questions about your implementation. Again for ease I'll ask them in line with what you wrote.
On the Palm I just change categories from Projects to Someday-Maybe
Are your projects and someday/maybe's in the memos or in tasks?
I have the maximum number of categories already. I tried to combine so I had 2 free ones in both tasks and memos but so far haven't managed that. I use my Treo for so much and as a reference that I ran into limits in the memo field for maximum number of characters and the categories as well as just plain memory limits.
I put a reminder for every single project on my one and only Projects list.
Are your reminders outcome based?
I'm trying to make sure that for all projects and for all my Someday/Maybe's I know what done looks like and indicate that in the project title. While I have not gotten that finished for all the items on those 2 lists for those I have it has really helped clarify my thinking about those projects.
I make no distinction or groupings of my projects by area of focus. A project is a project.
Do you have any projects that are all similar in that knowing you have 10 in a particular area or with specific prerequisites or tools needed you can combine them for more efficient completion? IOW it might be more efficient to activate a whole group of projects at once rather than one at a time but if they are scattered in a huge list you might not see they are related. See my weaving example in another message. Those kinds of projects are common for me.
If I decide to move an active project to S/M, I delete all of the associated actions on my next action lists and move the project to S/M. I'll decide the next action again once I reactivate the project.
How do you avoid reinventing the wheel? If you've thought of appropriate next actions or even a series of actions you will need to do why delete that and have to rethink it? That was one of the frustrating things for me with a Palm system is that, I need to get rid of the next actions related to projects that go back on the S/M list but I sure as heck don't want to lose the thinking that went into creating those or I'll have to do it all over again when those get activated. And re-activating a S/M back to a Project may happen quickly or in a few cases it may take a year or more before that one gets back to active due to season or weather conditions necessary for it to be worked on.
I find if my action lists get too big, it's hard to decide which one is the best to do.
Palm based stuff did seem to suffer more from long lists getting unwieldy. Part of why I am trying a paper system because I can't ever see myself with small project, someday/maybe or next action lists.