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.
 
The classic Allen-era contexts were anchored to real physical limitations.
You literally couldn't make a phone call from your @Computer station, and
they did real work.

For knowledge workers today, a lot of those boundaries have collapsed.
Most of my @Computer items are doable on my phone too, and vice versa.

So I've found context working less hard as a primary filter than it used to.

What's filled in for me: time and energy as the primary filter. "I have
25 minutes at medium energy, what fits?" gets me to a concrete next action
faster than scrolling a context list.

Area of Focus becomes a useful secondary mode-switch (am I in work mode
or personal mode), but I rarely need to drill deeper than that. When I do go deeper, I look at
the projects in the the area I'm fiiltered to.

Project lens stays critical for the weekly review and for planning the
week, but less useful for execution. Opening a project and picking off
"the next action on it" often surfaces work that doesn't match my
current energy or available time.

The list filtered by what I can actually do right now beats the list
filtered by what's organizationally important.

So my usual rituatl is: time and energy first, Area of Focus second, then projects in that
area then context only when it's still meaningful (errands, agendas, calls with specific
people). Calendar overrides everything when it's a hard commitment of course!

Hey, it's monday, enjoy the week!

James
 
@JamesT

Perhaps choosing an appropriate GTD 'Anchor' du jour:

@Calendar, @Contexts, @Projects, etc. with all other @GTD's being practical possibilities as secondaries as @mcogilvie appropriately suggests?

Thank you very much, very GTD helpful. . . .

Daily GTD anchoring . . . for potential flexible GTD guard rails for increasing Mind Like Water?
 
You must log in or register to reply here.
Top