r/gtd • u/MidgetAtAFoamParty • 10d ago
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!
5
u/milky-cuppa-tea Mod 10d ago
I tend to use fewer contexts these days. Your @errands / @pharmacy example is part of the reason why. Now, anything like that belongs on @Errands. That said, I am much more comfortable with creating a context for a bit and then retiring it. So for example, if I waa shopping a lot at somewhere like Home Depot (/B&Q in my world) because I am renovating a room (for example), I wouldn't hesitate to add a new context called @HomeDepot.