Project and Next Actions
I am a product of the FranklinCovey days of defining your 5 to 7 roles, goals, and so forth. I do not divide projects and actions by role. The key, at least for me, is the contexts that I use since that is how I sort getting work done. The defining action (context) can be as varied as you want them to be so that they are helpful. For example, I have @Computer (work that can be done on a computer, but does not need the internet), @Cloud (work that needs to be done on a computer with internet access). In some cases, when my computer list is rather long, I even use the @HComputer (for home computer work) and @WComputer (for work that has to be done on my work computer that cannot be done at home). Since most of the work that I do is compartmentalize to specific locations (I work in the insurance world, I am a minister, and I do coaching). I use context descriptions to aid in separation of projects based on roles without keeping separate project list. For example, @Work if my primary job, @Church relates to my minstery role, and my coaching work comes out of the home and occurs at different locations so I use the best contexts to guide that. I also have the major contexts like @Call, @Errand, @Home, and so forth that David recommends.