View Single Post
If the actions are truly things that other folks need to do, as your example implies, I'd suggest creating a hierarchy of contexts - groups that do things, with the people that make up the group inside. Assign the actions to those contexts. So if HR needs to send the email, it's an action in one of your projects assigned to their context.

Regarding how many miscellaneous projects/single action lists you need - my advice would be that it's better to start out erring on the side of too few than too many. Maybe just Work and Home, then break them up more if it is actually helpful to your workflow.

Don't just make one SAL for every subgroup - it's tempting to make a whole bunch of lists just to have some place to put things, but in practice that means you're wading through a bunch of lists you don't actually need.