Which 'Batch' Focusing seems

G

gtd solo-studente

Registered
Fellow GTDers,

Which 'Batch' Focusing seems GTD cognitively easier for Getting your things Done . . .

1. Area-of-Focusing on a particular Area-of-Focus ?

2. @Contexts: Rifling through the 'varying' Next Actions on a particular @Contexts List ?

3. Another way?

Thank you very much
 
TesTeq said:
@gtd solo-studente I often use Project focusing. Sometimes it is inefficient because it may require @context switching. But I am definitely one-thread executor.
Click to expand...
@TesTeq

Your overall reply is much appreciated

Finding "one-thread executor." along with "Sometimes it is inefficient because it may require @context switching." especially illuminating

When going-out of 'one-thread executing' to @context seemingly comes with some implied engagement rhythmic appropriateness, in that, while in "@context", one might seemingly gain some additional benefits:

1. Might be able to do an additional(s) Next Action while 'visiting' @Context without excess 'one-thread executing' derailment

2. Some 'perspective refreshment' might seemingly be gained from any 'inefficiencies' thereafter when returning to the 'one-thread' by having possibly achieved some elevated focus from the 'micro-disengagement' ?

Thank you very much for the increased appreciation-&-awareness for 'focusing' on the Area-of-Focus in the midst of appropriately allowing for the @Context 'opportunities' prompted by the Area-of-Focus 'focusing'
 
Last edited:
I generally use both a project lens and a calendar lens to determine what I really want to do and have to do on a given day. I may filter by context if the day is not too full to find additional next actions “as long as I’m in this context.” @computer, @tablet/paper/phone and @home are highly available, but @errand, @Spouse and @agendas not as much. Context is really secondary for me but still useful.
 
You must log in or register to reply here.
Top