Routine task

M

Moera

Registered
I read "Getting Things Done" (GTD). I created 4 lists:

1. Next Actions
2. Waiting
3. Projects
4. Someday/Maybe

I don't understand where to put things like vacuuming, ordering food, and other routine tasks. I'm afraid that putting these into 'Next Actions' will ruin it because there would be too many of them.

Should this go into a checklist?
 
As I think you’ve discovered, having a single list for all your next actions can be unwieldy. If a separate checklist or checklists for routines handles the problem for you, that’s great, Many people break their next actions into several lists, usually organized by what David Allen calls contexts. For example, someone might have @Work, @Home and @Errands lists. Others might have @Compute and @Calls or other lists. You can have both context lists and checklists, too. So there’s a lot of flexibility. You can test what works best for you, but a simple set of lists is often better.
 
Moera said:
I read "Getting Things Done" (GTD). I created 4 lists:

1. Next Actions
2. Waiting
3. Projects
4. Someday/Maybe

I don't understand where to put things like vacuuming, ordering food, and other routine tasks. I'm afraid that putting these into 'Next Actions' will ruin it because there would be too many of them.

Should this go into a checklist?
Click to expand...
I have four notes.
Projects- list of all projects
Agendas-Melissa, Megan, Ryan, and a work meeting.
Next Actions- @computer, @errands, @phone, @home @waiting for
Someday/maybe-list of all someday maybes
I used to have notes for each next action and agendas but wanted it more simple. I put all next actions on the list under the right context.
1779274167909.png1779274505113.png
 
cfoley said:
My life has evolved such that there are things I need to do every day, so I have created a daily routine checklist. It is fairly new but seems to be working well so far.
Click to expand...
@cfoley

Nice . . . great GTD tactic . . . easier daily routine @Context checklist to 'jump-start' handy-dandy 'separate' @Context list with it particular Next Actions

Very GTD . . . love it . . . thank you very much
 
Last edited:
Moera said:
I read "Getting Things Done" (GTD). I created 4 lists:

1. Next Actions
2. Waiting
3. Projects
4. Someday/Maybe

I don't understand where to put things like vacuuming, ordering food, and other routine tasks. I'm afraid that putting these into 'Next Actions' will ruin it because there would be too many of them.

Should this go into a checklist?
Click to expand...
Familiar confidence supporting 'Routine List' to 'jump-start' the less familiar @Context Lists . . . the commonality factor reduces friction between the familiar to the less familiar . . . while keeping Routine List 'separate' for many subtle reasons?
 
Last edited:
I use an app, Things 3, built for managing Areas, Projects and Actions. It has start dates and deadlines, and repeating events which can recur regularly or on a fixed interval after completion. So I use that feature for reminders about routines. I don’t have any special category for routine items. I remember David Allen saying that he dumped items from his physical tickler file right into his physical in-tray for processing, which is kind of similar.
 
mcogilvie said:
I use an app, Things 3, built for managing Areas, Projects and Actions. It has start dates and deadlines, and repeating events which can recur regularly or on a fixed interval after completion. So I use that feature for reminders about routines. I don’t have any special category for routine items. I remember David Allen saying that he dumped items from his physical tickler file right into his physical in-tray for processing, which is kind of similar.
Click to expand...
@mcogilvie

GTD interesting:

"start dates and deadlines"

Thank you very much
 
You must log in or register to reply here.
Top