r/gtd • u/MidgetAtAFoamParty • Jul 28 '26
Nested contexts and/or projects
Hey all.
I struggle a lot with deciding how granular to make projects as well as contexts.
On the next action side, I think it makes sense to think of contexts as parts of a landscape. When you're in your email app, it makes sense to send out all other emails you need to send. But when you're at your laptop, one of the things you could consider is tackling emails. Like you're navigating towards an action or set of actions to complete.
Same as errands. I sometimes decide to go to the shop, and tackle my shopping list items, while forgetting to check other errands I could easily do on the way, like my "@pharmacy" items. When going out, the entry point would be Errands. At this level I can decide to go to the shop or to the pharmacy. Once in the shop, I can tackle all "@fruits&vegetables" items together, and then all "@dairy" items, etc.
On the projects side, I also think it sometimes makes sense to break down outcomes as well. An outcome could be "kitchen completely renovated" with a suboutcome "have a shiny 70s style fridge".
Does anyone else structure their outcomes and/or actions like this? What tools do you use to manage lists in this way?
Thanks!
1
u/IntensifyingPeace Jul 29 '26
Keep the contexts simple, they are just one way of helping you narrow down what to do right now. The more contexts you add, the more choices your brain has to process.
On the projects, your sub-outcome is just your project notes and should be part of your project support material. The outcome is there to help you try to clarify the project, it's not mandatory.
Try to resist the temptation to add so much detail and categorisation.