Mrs-Polifax
Registered
Mrs-Polifax said (from David Allen, I think):
fooddude said:
I'm glad to know that there is no reason not to put multiple actions from any given project on our actions lists, if we are able to manage that. I agree about the importance of not putting dependent items that cannot be done yet on our lists. The lists need to be only for items we can act on, or it could get confusing.
Could you explain a bit what makes it a bad idea to work from action steps in Project Support material for people who prefer that approach?
Thanks, Emily
8. It’s fine to have multiple next actions on any given project, as long as they are parallel and not sequential actions (e.g., “Buy stamps” and “Mail invitations” would not both be on Next Actions lists for the “Put on Party for David” project given that you need to buy the stamps before you can mail the invitations).
fooddude said:
I think this is one of the most important keys to the whole system. And one where many make a mistake. Or they have some project note with all the next actions and try to use that instead of contexts. I try not to do that unless it is a large project and I need it to get it off my mind.
I'm glad to know that there is no reason not to put multiple actions from any given project on our actions lists, if we are able to manage that. I agree about the importance of not putting dependent items that cannot be done yet on our lists. The lists need to be only for items we can act on, or it could get confusing.
Could you explain a bit what makes it a bad idea to work from action steps in Project Support material for people who prefer that approach?
Thanks, Emily