I'm having a problem in my workflow, maybe some of you can spot my problem with it and offer suggestions.
Say my project is "Process Executed Estate Planning Docs for Smith". That involves making sure all the signatures and notaries are correct, doing a little memo to my secretary on whether we're sending copies to the client, which form cover letter to use, whether to include one of several different memos, whether we're keeping copies for the file, etc.
I have no problem checking out the signatures. easy. I like that part! Then I do the little memo and send the project away for "doing". I move it to @waitingfor and forget about it. It comes back in about a week, with a letter to the client and their memos and copies, which I have to check and customize, a vault transmittal memo attached to the originals that I have to check and drop in the interoffice mail, and an updated document clip that I just have to stick in the file. All really easy next actions that I could do in my sleep. And not "yucky" NAs either. I don't mind them at all.
The problem is, after the project has been off my front burner for a week, I've got other stuff in front of me, and I seem to wait at least a week before coming back to that project. This happens on all sorts of stuff that I delegate and then switch to @waiting for. Even when I move the project off of @waitingfor and back onto @work, it just doesn't seem urgent to me anymore and it sits and sits.
I've tried coming up with gimicky @context categories like "@Work-Almost Done", but it doesn't really help, the stuff still sits. It doesn't really matter that it sits, there is no deadline and the client doesn't get crabby (usually) waiting for the executed docs, but it would be great to get them out of my way sooner.
Help! Any ideas? Any insight on why I might be avoiding picking stuff back up after I've had if off my desk for awhile? Does anybody else have this problem?