Simpler solution (which GTD practitioners already know): keep a Waiting On list. Put due dates on it. Follow up when you hit the due date.
I use Todoist, but this will work with many todo systems, including pen & paper ones. When populating a project with items, like "Email Greg with questions from the RFP", I also add an item, like "Get RFP questions from Greg" and tag it with @waiting. I will also give the latter item a due date (e.g. 24 hours). If I want to see everything I'm waiting on, I can just look at the @waiting tag, but it's going to pop up when it's due anyways.
This is a much better solution if you already have todo lists, since you don't have to train yourself to perform a different activity, or keep track of yet another list of things in another program. Plus, it separates todo list maintenance activities from your email inbox. That kind of mental separation makes me way more productive by reducing the complexity of the given activity (i.e. sending an email).
Comments
Simpler solution (which GTD practitioners already know): keep a Waiting On list. Put due dates on it. Follow up when you hit the due date.
I use Todoist, but this will work with many todo systems, including pen & paper ones. When populating a project with items, like "Email Greg with questions from the RFP", I also add an item, like "Get RFP questions from Greg" and tag it with @waiting. I will also give the latter item a due date (e.g. 24 hours). If I want to see everything I'm waiting on, I can just look at the @waiting tag, but it's going to pop up when it's due anyways.
This is a much better solution if you already have todo lists, since you don't have to train yourself to perform a different activity, or keep track of yet another list of things in another program. Plus, it separates todo list maintenance activities from your email inbox. That kind of mental separation makes me way more productive by reducing the complexity of the given activity (i.e. sending an email).