[dp1]

I've got a Single Actions project that contains 80+ actions in the same context. All are available. None has a hard deadline. None is contingent upon another. From OF's point of view, they are all equal. But from my point of view some are more important or more urgent than others. I could sort the list manually, but I would need to revise it constantly, the very tedium that I'm trying to avoid. The only other options I see are to flag the more urgent ones, or to assign artificial deadlines. I'd be grateful for recommendations from more experienced users. Thanks.

[Lucas]

If it were me and, like you say, they are all in the same project and have the same context and lack any due date, I would start at the top, work my way down, and not worry so much about priority. If they are the same in project, context, and due date, they are not all that different in priority in any way that matters; accordingly, the time worrying about priority is wasted time. That's just me though; YMMV.

[whpalmer4]

Maybe sort by date added, and do the oldest ones first...or knock off all the shortest ones (or longest) if you have duration estimates. If there really is some difference in importance between them that only you know about, drag the most important ones to the top of the list, or flag them. If you only do that with a few at a time, then presumably you'll spend less time doing that when circumstances change and today's hot items become tomorrow's back burner items. Might also take a look at Mark Forster's Autofocus scheme and see if it resonates with you as a way to work though the list.

[Brian]

If the "some are more important than others" condition is relatively stable, I'd order the list and then work on it in that order. If the condition is unstable, as you suggest, then flagging the important ones would be the way to go...

[GrumpyDave]

Since you want to avoid continual manual sorting as tasks are added and removed, you might consider splitting it into two or three single-action lists. Name them appropriately (high, medium, low, etc.) and then just move tasks between them as needed during reviews or whenever. Then you won't need to worry about sorting or moving tasks up and down as a measure of priority and it'll be easy to focus on the priority you wish to work on at any moment.

[dp1]

Good feedback. Thanks to everyone. I'm leaning toward the idea of separate groups for different levels of priority. What are the tradeoffs of that approach?