One possibility here could be to introduce checklists to your system. For example, if homework routinely comes back twice a week, I can imagine:
Originally Posted by RichB
- Creating a "process submitted homework" project folder. (OK, here I'm cheating and not doing the "outcome" title, because those annoy me. I suppose an outcome title could be "Fall semester's homework processed in a timely manner.")
- Creating a "process submitted homework" checklist, a checklist that lists all the steps for all the courses on one sheet. (Alternatively, you could have a separate checklist for each course.) This could include the necessary course numbers and other information for processing homework, if you ever delegate this task or if you ever have to look them up.
- Printing out a body of checklists, two per week for every week of the grading period, and writing dates on them.
- Putting all of those checklists in the "process submitted homework" folder.
- Then your system just needs to include "Work this Tuesday's submitted homework checklist," and "Work this Thursday's submitted homework checklist," repeating every week. That task is indeed in a project, but it's a project that's been rethought and resized so that it makes sense being project size.
I don't know if this is nice and GTD-compliant; it's been a little too long since I read the book. But I can't see anything really noncompliant about it.
Tags for this Thread