What triggers you to act on your action items?

[Conejo23]

How do you know when you need to take action on something?

After several readings of GTD and RFA, it seems to me that in an ideal/pure GTD implementation, few if any tasks would actually have dates attached to them, and that the call to action is either reviewing a project and seeing next actions, or examining a context. Neither of these really work for me.

a quick note: I use OmniFocus as my task management system and I'm pretty happy with it, for the most part.

A good portion of my tasks are date driven. Call someone on a certain date, replace the air filter on a certain date, prepare payroll or a monthly royalty report on a certain date, etc...So I give those completion due dates and have a defined view (perspective) that shows me what is due now/overdue/coming soon (next few days).

Then I use the flag indicator to mark urgencies. So if I only have time to get a few things done that day, the ones with flags are the ones that MUST be accomplished. I have a separate view to show me flagged items by due date.

Another big chunk of tasks for me is responding to clients. When clients email or call me with a request for info or a question, I have a separate project called ‘Clients’, I add the task to that project and don’t bother with a due date and have a separate view to just see those tasks in a focused way.

And then there’s everything else, and that’s the category of stuff I feel like I don’t have a good handle on. The more items I put due dates on, the less I feel like there’s stuff floating in my system that I'm not on top of. But that means I'm now putting dates on things that don’t organically need them, so they’re getting arbitrary ones. And that means when that respective date rolls around, I like at what’s due now and see a mix of things that truly are due now combined with things I could really do whenever I felt like it, that’s kind of confusing. Intuitively, I feel like there’s a better way to handle this.

I’d love to hear if anyone else has had a similar issue in their workflow, and if they’ve successfully addressed it in a way that works for them, what that was.

Thanks.

[Cpu_Modern]

I tried tons of stuff to solve that problem, here's waht works for me:

1. I schedule projects. I always have a Most Important Project, each working day begins with working for a solid block of time on that project.

2. I dedicate blocks of time to contexts. For instance on many saturday mornings I am working solely on home improvement tasks.

3. On my endlessly long @computer list I do "mark" a bunch of NAs. These have to get done first. It doesn't matter if I work longer on each involved project (google this forum for "bookmark method") or if I do "unmarked" NAs. The point is the rythm, mark a few NAs, focus on them, complete them. Define the next bunch. I usually need half a week to complete the marked NAs.

Let me add two thing: a GTD-system will not magically induce self-discipline. That has to come from somewhere else. I found out that bigger clarity on the higher levels motivates me to do the work. You have to "own" your work. A bad job doesn't turn into a good one just because you are doing GTD.

The other thing is this: even if everything is awesome, you have to overcome a certain inertia. That's just physics and I found out you can overcome this quite literally with physiological tricks. For instance I sometimes shout out loud my NA-list like a drill-sergeant. Or I do some push-ups while screaming at me to go the f#*% to work now. I also have a flag in my office which shows me visually if I am "at work" or at 'home.

Sometimes just not doing your work is a message from the sub-consciouss that something is wrong. You are not commited fully because deep inside you know that your plan is crapp.

Hope this helps ;-)

[malisa]

Thanks to the OP for the question and to the poster above for some good ideas.

I like the 'Most Important Project' and 'blocks of time' ideas. I will also google the forum for the bookmark method. I know that I need a smaller list because when I look at my big context lists, they seem insurmountable. I've been pulling out a few actions that I feel I can knock out at a time and putting those on a list on the front of my binder. I've thought about highlighting things on my context lists, but then if I didn't finish them and they became less important than other things, I'd be tempted to re-copy my list to 'unhighlight' something. Maybe the bookmark method will be something to help me with this.

[malisa]

The only things coming up when I google "bookmark method" for this forum are our two posts. :?

[kewms]

Are you doing regular weekly reviews? The purpose of the weekly review is to help you stay on top of things and do this kind of prioritization.

Katherine

[cameron]

How do you know when you need to take action on something?

After several readings of GTD and RFA, it seems to me that in an ideal/pure GTD implementation, few if any tasks would actually have dates attached to them, and that the call to action is either reviewing a project and seeing next actions, or examining a context. Neither of these really work for me.

a quick note: I use OmniFocus as my task management system and I'm pretty happy with it, for the most part.

A good portion of my tasks are date driven. Call someone on a certain date, replace the air filter on a certain date, prepare payroll or a monthly royalty report on a certain date, etc...So I give those completion due dates and have a defined view (perspective) that shows me what is due now/overdue/coming soon (next few days).

Then I use the flag indicator to mark urgencies. So if I only have time to get a few things done that day, the ones with flags are the ones that MUST be accomplished. I have a separate view to show me flagged items by due date.

Another big chunk of tasks for me is responding to clients. When clients email or call me with a request for info or a question, I have a separate project called ‘Clients’, I add the task to that project and don’t bother with a due date and have a separate view to just see those tasks in a focused way.

And then there’s everything else, and that’s the category of stuff I feel like I don’t have a good handle on. The more items I put due dates on, the less I feel like there’s stuff floating in my system that I'm not on top of. But that means I'm now putting dates on things that don’t organically need them, so they’re getting arbitrary ones. And that means when that respective date rolls around, I like at what’s due now and see a mix of things that truly are due now combined with things I could really do whenever I felt like it, that’s kind of confusing. Intuitively, I feel like there’s a better way to handle this.

I’d love to hear if anyone else has had a similar issue in their workflow, and if they’ve successfully addressed it in a way that works for them, what that was.

Thanks.

The calendar is used for all date specific actions

[Cpu_Modern]

Some posts explaining NAs as "bookmarks":
http://www.davidco.com/forum/showpost.php?p=27671&postcount=9
http://www.davidco.com/forum/showpost.php?p=57676&postcount=3
http://www.davidco.com/forum/showpost.php?p=47084&postcount=2

[Conejo23]

Cameron....i disagree that the calendar is used for all date specific actions. For my workflow, a calendar is a place to record events, not tasks. Lunch will Bob on Tuesday, teeth cleaning on Thursday, taking family to the game Saturday night, meeting Monday morning.

Tasks go into my task list. Some have a date dependency, some don’t, but my tasks do not and will not be going into my calendar. So the question, again, is how to manage a task that where some are date driven and some aren’t.

Katherine.....the review is an area where I need to get better. I do periodic reviews, but even then the problem persists. I do the review, I see that I have a few projects with outstanding tasks that deserve and require some attention, and then I engage my day and what I remember from what I just reviewed basically goes out the window. I find I'm not getting much from my review sessions other than to see “yep, those tasks belong to those projects are still there, gotta get to those.”

I’ve developed process so that my needed client responses or urgencies or due now tasks don’t fall through the cracks and they are on my radar in a way I can easily find them, but I have yet to find a process for the rest of it that feels comfortable and will work.

I appreciate the first response to my post, and while those techniques may work for some, they haven’t for me. Although I do love the suggestion that perhaps I have tasks associated with projects that are not staying on my radar for a reason, that I'm not fully committed to the project itself or am resistant to it in some fashion so that I subconsciously instruct myself not to put attention there. That’s entirely possible.

The most important thing I can do for our business is to take exceptional care of our clients and encourage the others in our very small office to do the same. It’s like THAT is my biggest project and it does indeed get proper attention. Then I have a bunch of others that need to get done and we’ll benefit from getting them done but I'm about as enthusiastic about the work of doing them as going to the dentist, things like “finish writing copy for customer referral kit”, or add webpage discussing how we differ from physical therapy. Conceptually, I love those things. Pragmatically, I'm already working 60 hours a week and for me to do them requires giving something else up, usually family/personal time or sleep.

Gonna think on this one some more.

[Conejo23]

just read this at one of the ‘bookmark’ links provided above:

Now, if a next action is just hanging around for weeks... like 'clean the bedroom closet'... In this case, I know I can complete the whole thing in one sitting and in one context, but it's a cringe task. I just don't want to start. So, it gets promoted to a project, and the next action becomes something very, very small; something like 'throw out the dry cleaning bags that are still on clothes that I picked up from the cleaners last week'. It's a two minute task--one I won't mind doing--and it moves things forward. It may even get the juices flowing to the point that I'll actually complete the whole 'clean closet' project.

I love the description of a “cringe task” or project. It’s something I need to do, and it’s a result I want to obtain, but I just am not excited about the DOING of it. Even more, I like the idea of finding some really small thing I can to on that to break inertia and generate at least a little momentum.

Good stuff.

[humblepie]

Cameron....i disagree that the calendar is used for all date specific actions. For my workflow, a calendar is a place to record events, not tasks. Lunch will Bob on Tuesday, teeth cleaning on Thursday, taking family to the game Saturday night, meeting Monday morning.

Tasks go into my task list. Some have a date dependency, some don’t, but my tasks do not and will not be going into my calendar. So the question, again, is how to manage a task that where some are date driven and some aren’t.

Katherine.....the review is an area where I need to get better. I do periodic reviews, but even then the problem persists. I do the review, I see that I have a few projects with outstanding tasks that deserve and require some attention, and then I engage my day and what I remember from what I just reviewed basically goes out the window. I find I'm not getting much from my review sessions other than to see “yep, those tasks belong to those projects are still there, gotta get to those.”

I’ve developed process so that my needed client responses or urgencies or due now tasks don’t fall through the cracks and they are on my radar in a way I can easily find them, but I have yet to find a process for the rest of it that feels comfortable and will work.

I appreciate the first response to my post, and while those techniques may work for some, they haven’t for me. Although I do love the suggestion that perhaps I have tasks associated with projects that are not staying on my radar for a reason, that I'm not fully committed to the project itself or am resistant to it in some fashion so that I subconsciously instruct myself not to put attention there. That’s entirely possible.

The most important thing I can do for our business is to take exceptional care of our clients and encourage the others in our very small office to do the same. It’s like THAT is my biggest project and it does indeed get proper attention. Then I have a bunch of others that need to get done and we’ll benefit from getting them done but I'm about as enthusiastic about the work of doing them as going to the dentist, things like “finish writing copy for customer referral kit”, or add webpage discussing how we differ from physical therapy. Conceptually, I love those things. Pragmatically, I'm already working 60 hours a week and for me to do them requires giving something else up, usually family/personal time or sleep.

Gonna think on this one some more.

i do kept my calendar for time driven events as well. but the main baby is still the task list.

[Conejo23]

Ok, some more thoughts on this. I went back and re-read the section from David’s first book regarding the handling of date-driven stuff, and also heard him talk a bit on one of his podcasts about this.

David did NOT say that all date driven stuff should go into a calendar. What he wrote was that it should go into a calendar or the tickler file (presumably one of the 43 folders). Well, if I'm working a paper based system, unless I have a datebook kind of device like a Franklin Planner, then yes, a calendar is probably the most logical place for some of these items.

But technology changes things. An application like OmniFocus can act as both the action list repository AND as a digital tickler file, and can do so more efficiently and elegantly than can a physical tickler file. I need to call someone on a certain date and I need to reference 2 files on my computer stashed in my reference library. Well, I could write down “Call Bill” on a piece of paper, then print out the files, staple it all together and put it in the appropriate tickler folder, or I can add that as a task in my software, create direct links to the reference files and have that task show up on precisely the date upon which I need to act on it, and I can do the electronic version of this process much faster than the paper version, particularly if there are multiple pages to be printed. Moreover, I just saved money on ink and paper costs to boot.

So I would argue that this process is not a contradiction of what David advises, it’s just a different implementation of a tickler file, a different way to do EXACTLY what he advises.

But there was something he said on the podcast I'm listening to that tied it together for me and I felt like it gave me permission to structure my system in this way. He was taking a question from someone in the audience and to summarize what I heard him say, he basically said “I don’t have a problem with you using dates for your tasks as long as you are not enslaved by those dates. If you run out of day because you got a long phone call and the copier broke down and you had to pick your kid up early from school because he was sick, give yourself permission to understand that for those things that can be done tomorrow or later that it’s OK to do them then and not feel compelled to grind yourself down to the bone because you have some relatively arbitrary date on a task.”

that makes perfect sense to me. And I realized that in my system, I use dates in two ways. One set of tasks have dates that are hard, that task NEEDS to get done on THAT day (but again not at a specific time otherwise I'd put it on my calendar). Those are the tasks I flag. On a given day, those are the things I gotta get done, the rest would be great to get done that day and if I can’t, then I move it out. Then obviously the other set of tasks with dates is that last category. I use the date as a guideline of when I want to get it done but if it needs to get pushed out because of interruptions or changing priorities, that’s fine. And my software tool makes that VERY easy to do. I can reschedule 10 tasks in about 15-20 seconds.

Just wanted to address the implication from some posts above that it’s somehow a violation of GTD dogma to put a date driven action on a task list. With advances in the technology of our toolkits, the line between action lists and tickler files has been blurred.

[cameron]

David did NOT say that all date driven stuff should go into a calendar. What he wrote was that it should go into a calendar or the tickler file (presumably one of the 43 folders). Well, if I'm working a paper based system, unless I have a datebook kind of device like a Franklin Planner, then yes, a calendar is probably the most logical place for some of these items.

Just wanted to address the implication from some posts above that it’s somehow a violation of GTD dogma to put a date driven action on a task list. With advances in the technology of our toolkits, the line between action lists and tickler files has been blurred.

Yes, if it's a due date it doesn't need to go in the calendar, that wasn't entirely clear in your original post.

In the truest spirit of GTD i think the idea is that if you're regularly doing a weekly review then you don't need a visible link between Next Actions and projects - because you -know- what's what.

Similarly unless it's going to be a huge issue, adding deadlines to your next action is probably unnecessary baggage. If it's urgent, you do that as your current activity. If doing it between now and your next weekly review is sufficient, then it's sufficient. (note that it would make sense to add your due to date to the project level)

[Brent]

In the truest spirit of GTD i think the idea is that if you're regularly doing a weekly review then you don't need a visible link between Next Actions and projects - because you -know- what's what.

Similarly unless it's going to be a huge issue, adding deadlines to your next action is probably unnecessary baggage. If it's urgent, you do that as your current activity. If doing it between now and your next weekly review is sufficient, then it's sufficient. (note that it would make sense to add your due to date to the project level)

Yes!

You should be looking at your lists multiple times per day, and each time you do you'll be deciding what's most important at that moment.

Now, I have put due dates on a few Next Actions. Sometimes, it makes sense. But as a general rule, I honestly find I don't need them.

[Conejo23]

this has been a good discussion for me because it’s helping crystallize why I do some of what I do. I totally understand the intended/designed mechanics of working with few if any dates on the actions. But when I started out and tried that, what I found was it almost required a daily review process that I found very inefficient. I was constantly going through all these different tasks and making the same decisions over and over. “nope, I've got higher priorities than this task, it can wait, but this one over here, I need to get that done tomorrow”, that kind of thing, and I found myself spending a LOT of time reviewing those lists. It was like I was doing a mini weekly review multiple times a day just to pick out what to act on. What worked a lot better for me was to go through my weekly review, look at my next actions and then map out a plan of what I want to get done when, do that once, and now I let the dates bring those actions to my attention at the appropriate time and I don’t spend time each day reviewing the available actions list, I use that time acting.

And I have my views setup where I see what’s past due, what’s due today, what’s due tomorrow, and then everything else. So those days where I've gotten everything done I look at the ‘everything else’ list and pull in what can be done now and get it done. But most often, I'm just happy to get done what I decided I wanted to try to get done that day.

So far it seems to be working for me and it just feels way better than to be constantly reviewing my available actions list, but the weakness in this approach is making sure those items without associated dates don’t become out of sight/out of mind. But I'm finding ways to use my software app to address that.

[NewbGTD]

I’m starting to take a lot of my task/actions with dates attached to them and putting them in my tickler system.

Lately, my “waiting for” list is beginning to bug me, its filling up with quite a few waiting for’s that I don’t want or need to see (reviewing it just makes me “think” about stuff that needn’t be thought about). Most of my waiting for’s have time limits until I need or should follow them up so why not just tickler that date (digitally) to pop up when its time to follow it up instead of having a waiting for list that needs reviewing?

One of my goals is to have system that reminds me of everything I need to do that is someday in future, could be in a year, 6months, one month, or even a few days. I want it out my sight/out my head. Then get a nicely timed reminder telling me what to do. Mind like water baby haha

[Cpu_Modern]

I've set up my digital tickler so, that with a search I can get a list with every NA in there for Weekly Review purposes to make sure that every project has an active NA. Hurray! Give me an H, ...

[Rob78]

One thought - if you're using next actions as the GTD books describes them ("the next physical action that...") then it doesn't make sense to give them due dates because they're too small. Completing an NA on its own will rarely complete a project or project milestone, and it's those larger things that are going to be date sensitive.

E.g. if I'm writing a report, "sketch section headings" might be an NA, and that on its own isn't a useful milestone. "Circulate draft report to reviewers" would be such a milestone, and that could deserve a due date (indeed I might well have agreed to deliver a draft by that date).

[Conejo23]

Rob.....you are looking at due dates in this context (no pun intended) in a fundamentally different way than I. For me they are not milestones. It’s me planning my work.

During my weekly review I'm looking at the projects on which I want to make progress, the next actions I want to complete (some of which are tied to projects, some of which aren’t), and then I'm comparing that with my work schedule and looking to see where I have opportunity to make progress on these things.

One thing I omitted sharing which would probably be useful is that in my work, the majority of the day I cannot work on any of my next actions. My work day is primarily filled with working directly with clients. I’m not a physician, but think of a doctor seeing patients. If he has an absolutely full client load, whether he’s in surgery all day or seeing patients most of the day, he’s not going to be able to spend much time working on his projects. Some days he might not be able to do anything but a couple simple tasks. Other days he might have more discretionary time on which to make progress on those things.

So, during my weekly review I'll look at my work calendar, get a sense of which days I'll be able to have chunks of time to really move forward on things and then I'll schedule my tasks so that they are getting done by when that needs to happen but I'm scheduling my work so that I don’t overload myself on a day where I can’t realistically do much. Then that way during my actual work I'm not having to take time to go back and re-review my action lists to see what I can do or should be working on, I already made those decisions in a calmer, more reflective time outside the “heat of battle” and now I don’t have to clutter my head with that stuff. I just work my plan. I can have my software show me everything if I want, regardless of due date, or I can have it simply show me “what do I intend to do today”. That’s how I prefer to work.

I realized one of the reasons I didn’t stick with GTD in the past wasn’t that I didn’t mind doing the weekly review, but that I HATED what amounts to the daily re-review. Actually, it’s a multi-daily re-re-re-review and I found that process (for me) to be hideously inefficient. For me, being slammed with clients and then having a 30 minute window to get stuff done and now having to spend some of that time going back through my contexts to decide “hmm, what should I work on now” was both stressful and very unproductive. Now when I get to that window I already know EXACTLY what I'm working on and I just get to it. I feel a reduction in stress instead of an increase in it, I'm getting more done and I'm not resistant to the process.

If the majority of the time in my work I was working on my projects and time where I was unable to do that was the exception and not the rule, then perhaps I would turn this around and work more as you do. But for ME, that just wasn’t working and it feels terrible and terribly inefficient.

[cameron]

Yeah, that falls into 'whatever works' territority. I'm thankfully not in that position as i'm otherwise knocking stuff off my list as i go along or just dealing with the hundreds of "must do now" priorities that get thrown around in a day. (FMCG) I don't repeatedly re-review my tasks lists i just do what's next and hopefully that gets me far enough ahead of my deadlines that they aren't too pressing (that's not including all the stuff i've missed before I bothered reenergising my attempts at gtd)

Your case is interesting because i think that's sort of an example where it's talked about throwing things back and forward into the someday/maybe project file. But that's probably a LOAD of work.

[Conejo23]

Cameron.....i’m actually going to start a new thread talking about how one defines a project as active vs on hold or in some day status. But for me, yeah, on a typical day I'm getting maybe a 30 minute window in the morning, then a 20 minute window after lunch, and then another 30 minute window late afternoon, then whatever I want to do when I get home. So for me it’s important that when I get those windows I have it laid out in front of me what I want/need to get done. If I was in one of my prior jobs where I was constantly doing nothing but working on my projects, then it would be different.

But for me, every time I get one of these windows, to have to re-review my task list to pluck out what I can act on at that point? Just wasn’t working. At all.

[Cpu_Modern]

Conejo23, I think what you are doing is not so much attaching deadlines to next actions, but scheduling them. You are shaping your hard landscape proactively.

You already pointed at this by distinguishing your practice from attaching milestone's due dates to NAs. The point is: there is a difference between "due by" and "due on".

[Conejo23]

CPU....i think that’s a fair assessment, although I'd say that these kinds of items aren’t what I'd call ‘hard landscape’ unless I'm misunderstanding that term. Some of the things I say are due on a given date really ARE due that date and those are indeed hard landscape, and I supplement the date with a flag on those items. But most of them are simply scheduled, as you suggest. For me it’s a process of matching up and planning out when I'll have time available to work on actions with what actions I want to get done in those slots.

And what I've found is it takes me less energy and I make better choices more in line with my priorities when I make that decision in my weekly review as opposed to daily. Sunday night I can say “OK, I need to reconcile the business checking account during my window of time Wednesday afternoon”, a job I do not enjoy. If I waited until Wednesday afternoon and looked at my contexts, I would likely pick something else that was less mentally demanding.

So far, it’s working. Tomorrow may be a different story.

[Cpu_Modern]

I make better choices more in line with my priorities when I make that decision in my weekly review
Some on this forum mentioned 'mental contexts in past discussions about context-lists. Seems to be that the Weekly Review can be a mental context, a mental state, too. Makes some sense to me at least.

[Conejo23]

indeed. I think that’s one of the powerful things about the weekly review and why so far I like doing it on Sunday afternoon or evening. I can be a little more rational and dispassionate about my workload. When I'm in the middle of a day and if I just had a difficult client, or a long phone call or the printer is being a pain in the butt, it’s easy to “lose state”, as Tony Robbins would say, and then it’s easy for me to make less than optimal choices about what to do with my time. But by planning it earlier in the week I find I'm more grounded. Kind of an “OK Rick, shake it off and get to work, this needs to get done now” type of thing.

And I was just listening to a DA podcast, I think it was on best practices for organizing and their chief tech guy was saying he has a context for when he’s just mentally burnt and at really low energy, and into that he’ll put things he can do without a lot of thought. I thought that was a cool idea.

The more I read on and listen to GTD information, and the more I practice it, the more I'm struck by how it’s really not a system as much as a mindset, and that it can be flexibly implemented in a lot of ways to fit a lot of different workflows.

[Rob78]

The point is: there is a difference between "due by" and "due on".

Perhaps the full set is: "due by" (deadline), "must do on" (hard date but not time constraint) and "do on" (scheduling).

Often it's software tools that drive the confusion (e.g. I use RTM which has only "due date").

rob

[Conejo23]

those are good points.

My software (OmniFocus) has start date and due date (along with completion date, presumably for history but I don’t use it). For me there is no difference (in the context of an action) between due by and must due on. They gotta get done that day, so in my system those are represented by a due date and a flag. Those that are simply scheduled for that day but could move out if circumstances dictate are represented by a due date and no flag.

The reason for me that I don’t differentiate between the first two is that I perceive the main difference between the two (due by and must due on). The first implies that it might be something I started earlier than that day and it needs to be finished by the specified date. I don’t give myself any actions that take more than a day to complete. In fact, I try not to give myself any actions that take more than a few hours to complete at the most. For me, a multi-day action is probably a project, not an action, and I'll break down the actions accordingly, in smaller chunks I can actually do in the time that I have.

[TomW]

CPU....i think that’s a fair assessment, although I'd say that these kinds of items aren’t what I'd call ‘hard landscape’ unless I'm misunderstanding that term. Some of the things I say are due on a given date really ARE due that date and those are indeed hard landscape, and I supplement the date with a flag on those items. But most of them are simply scheduled, as you suggest. For me it’s a process of matching up and planning out when I'll have time available to work on actions with what actions I want to get done in those slots.

And what I've found is it takes me less energy and I make better choices more in line with my priorities when I make that decision in my weekly review as opposed to daily. Sunday night I can say “OK, I need to reconcile the business checking account during my window of time Wednesday afternoon”, a job I do not enjoy. If I waited until Wednesday afternoon and looked at my contexts, I would likely pick something else that was less mentally demanding.

So far, it’s working. Tomorrow may be a different story.

This has been a really fruitful discussion to me -- thanks.

I have a very, very similar work environment and had hit on nearly the same solution... only the opposite!

I put due dates only on NAs that are truly due that date. I flag NAs that are important to me, high priority, or urgent. My day begins with first checking the hard landscape on the calendar, then next checking the Due Date view which lists NAs with due dates, followed by NAs with a flag, and then all the rest. I then spend a couple of minutes choosing flagged NAs that I plan to do that day (i.e. schedule for that day as in your non-hard due dates.) It's essentially the same system but I do not put dates on NAs that don't have real due dates. I used to do it your way but found I spent too much energy recognizing/sorting what was really due and not due today. I realized that I was giving myself permission to ignore due dates for some NAs and not for others, and that seemed not an optimum path to follow, as NAs with overdue dates piled up.

[Conejo23]

Tom, glad this has helped you. It’s certainly helped clarify my own thinking, for better or worse. I’m actually having a free consult call this afternoon with one of the coaches to see if personal coaching is the right move for me, already forwarded her this thread and suggested that if she read it prior to our call it would give insights into where I'm at in the process. Will come back and post if I get new insights.

I realize my system wouldn’t work for a lot of people, maybe for most people. For me, I realized that I have two different modes of work. There are times when I'm just in the heat of it and I'm grinding out the stuff that I know I NEED to get done, and in that mode I just don’t have the time to go back and review context lists and re review my available NAs. When I tried doing that I just spun out, wasted energy and my productivity was terrible.

So each week during my review when I ‘schedule’ my workflow, when I get to that date I know what my plan is, and the way I represent tasks visually tells me whether it’s something I HAVE to get done that day or something I'd LIKE to get done that day. One thing I think is key, which is something I heard David say on a podcast (and I mentioned above) is that I give myself full permission to reschedule tasks that can be rescheduled if that needs to happen. I don’t view the due date as a fire alarm, but I view my “due today” list as almost a context to itself. And re the mechanics of it, rescheduling a task is super easy. I can reschedule 5 tasks in about 10-15 seconds, so it’s just not a big deal.

Then my other mode of work is when I'm not grinding in the heat of the workday and I can step back and say “OK, I've got some discretionary time here to advance some of my projects, let’s review my contexts and pick out what feels like it’s what should move forward right now.”

I know it’s kind of a schizoid approach, but my work environment is a little schizoid, so there you have it.

[Oogiem]

I know it’s kind of a schizoid approach, but my work environment is a little schizoid, so there you have it.

Sounds like lambing ;-)

During lambing all bets are off, the priority is keeping sheepies and lambies alive. All else, including food for the humans pales into insignificance. But once nighttime hits I try to do as much on contexts as my energy allows. I know that the mad crush will all start again at dawn the next day. During lambing we are out with the sheep from first light until after dark.

I don't use due dates but instead work to pre-load a lot of task and jobs.

So I have food prepared we can microwave, alert the neighbors that the lambalanch is imminent (the same neighbors who often arrive unannounced with wine, coffee, bread, or food or just a spare set of hands just when we really need it) and set all sorts of things onto automatic reply "I'm lambing, call back in June" type messages. I also set up a bunch of helper things, the checklist for dystocia triage printed out in large type so I can read it in the field w/o my glasses, (which often get slimed by the end of the day) the lamb bag contents so I could restock after each trip out to the ewes w/o thinking, the picture of how to tie a baling twine prolapse harness in my bag (only needed it once but I really needed it then), the proper place to euthanize a sheep and notes on how to do a field emergency c-section plus tools and instruments needed are also now in my bag for use if needed. Whatever I think I might need for any emergency was prepared in advance because during the crisis I can't stop to think I have to just do or follow a checklist.

I also found last year that the more I did in weekly review (actually pre-lambing review) to really chunk things down to the tiniest next action possible really helped. I needed to have no thought or brain capacity required to do anything on any action list or it never got done until the lull between lambing flights.

I went into lambalanch with a huge next actions list (I'd guess maybe 50-60 actions per context) but the actual actions were very small easy to do things, much more granular than my normal next actions lists. I came out of lambing with nothing critical left undone and nothing dropped, a first for me.