View Single Post
David Allen says that for work that pops up and you can finish it in 2 minutes or less, to just do the work (the 2 minute rule). Longer 'work as it shows up' (WAISUP) (or other self-created spontaneous) actions that get started and will completed the same day, and assuming you stay with an Action through completion, also don't require tracking in a trusted system for many folks. But for those who do need/want to track that kind of work, I'm curious about any novel approaches people have.

A traditional OF work flow is to create an Action and assign it to a Project or SAL, and also to a context. But then it sort of gets buried (filed), and then you need to search or browse for it in order to mark it complete and update the time spent on it (again, only for those who need/want that data). Sometimes I'll get involved with several WAISU issues in a short period of time. I've found that if I leave them in the Inbox (either by not cleaning up, or by not assigning to a Project/SAL and/or Context (my prefs are set to require both for cleanup to take place), that seems to be one way to keep them handy (but remembering to not clean up, or to not assign, is not very systematic.

I just realized I could set up a Perspective, Context mode, grouped and sorted by when 'Added', and filtering on 'Remaining'. That seems like a good approach that I'm going to try. Just checking for ideas ...