• Our deepest thanks to the many GTD enthusiasts who have posted in and read this forum over the years. Because use has been steadily declining in recent years, we have reluctantly decided to make this forum a read-only reference archive. There is an active GTD discussion community on the new GTD Connect. Copy/paste this link to get a free trial: https://bit.ly/4hYicYV We still offer a range of other free resources for GTD enthusiasts at: https://gettingthingsdone.com/resources/

Management, the Project List, and Projects

W

wdr1

0
With a team of ~20 reporting to me, my teams have a lot of distinct projects running concurrently. I've heard David Allen say a few times "the project list is king." I'm stumped on if it makes sense for my project list to contain every project that rolls up under me, just the projects I'm actively working on, or some combination?

I'm curious what others things and/or have done?
 
wdr1;108777 said:
With a team of ~20 reporting to me, my teams have a lot of distinct projects running concurrently. I've heard David Allen say a few times "the project list is king." I'm stumped on if it makes sense for my project list to contain every project that rolls up under me, just the projects I'm actively working on, or some combination?

I'm curious what others things and/or have done?
Click to expand...

Great question. When we coach people in your situation, we often suggest they create a separate list for the projects they are monitoring to completion, but which are not their direct project to take actions (just get updates.) So it might look like separate lists like this:

-Projects
-Projects - Delegated (or Projects - Overseeing or Projects - Monitoring or Projects - Direct Reports)

Does that help?
 
You must log in or register to reply here.
Top