I do the same thing, and sometimes write
Originally Posted by Myriam
next action > mini-project
updating the next action, and moving or duplicating and changing context as needed.
A real-world example:
Discuss departure time w spouse > make plane reservations for niece's wedding
In this case, the travel is complicated by another trip I'm taking
right after the wedding. This is probably just a few steps,
but it helps me to remember the mini-desired outcome of the mini-project.
In your case, I would say that it is not merely of some importance, but is of fundamental importance, that you not only be organized, but that you manifestly and undoubtedly be seen to be organized. (allusion to a quote in http://en.wikipedia.org/wiki/R_v_Sus...parte_McCarthy )
I would suggest therefore that you expend some effort in attempting to understand as clearly and fully as possible what exactly the committee meant by "organized", how they were able to perceive your degree of organization, and what impact it has or is seen to have on the university, students, members of the committee etc.
You might want to consult an objective observer -- possibly another professor whom you trust -- to help interpret the committee's message and figure out what they meant. You might also want to review the actual wording of the committee's comments at regular intervals. That way, you may be better able to direct your efforts in the most fruitful directions. For example, possibly the committee's only real concern is that you submit marks on time; or possibly their concern is something else, or some combination of things. "Organized" can mean different things to different people.
You might want to define a goal, area of focus or other higher horizon of focus something like "become organized to the committee's satisfaction". This way, you can try not only to satisfy your own, or David Allen's, or this forum's definition of organized, but you can focus on satisfying the committee's idea of what organized is, and to do it in such a way that it has a positive impact on the university and is perceived by the committee members.
I also use OneNote - this might help
My OneNote system consists of several notebooks:
-Areas of focus
-Done (move completed projects here)
In the Projects Notebook I have several sections:
-Projects (for all the mini projects like the office party, Awards ceremony, anything that only needs one page to plan and track outcomes
-One section per project (for you I would have it as one per subject, eg Biology, Maths etc. when you move it to the Done folder, include the year in the section name so there would be Biology 2012, Biology 2013).
In each project section I would have several pages for the plan, information, and each subproject and keep notes of them. Use subpages to group pages together and rollup the pages for easier page navigation.
Tags - I use them a lot. Need to customise them, get rid of the default and setup these:
Check box Project
I use the first two since I capture a lot of info directly into OneNote, but might want to process and review it later.
Use one check box per project, and use this to tag each committed outcome, like Prepare chapter 14 lectures, and Grade chapter 13 homework.
The advantage of tags is that your outcomes can be anywhere in OneNote but easily consolidated into a central list. Do this by pressing Find Tags, and Group tags by Tag Name. It will do this in alphabetical order, which is why I have a + at the start of Process and Review, so they'll be at the top of the list and not mixed up with the projects.
By ticking the check box and ticking Show only unchecked items you can hide items from the list. You can print the list by Creating a summary page - but delete this afterwards as it creates duplicates which will show up in subsequent summary pages. I don't tend to bother with it, as I only want to read my list on the computer, and not print it out.
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.