[dhm2006]

Originally Posted by gary

In my mind it's not a project if it can't be completed. Fixing up an old car is a project. Keeping it running is an area of responsibility. But, obviously, for others this works.

In his book, DA talks about projects that don't have finish lines so much as what he calls "outcomes." One example he gives is "Create a way to regularly spend more time with my daughter," about which he goes on to say "is as specific a project as any, and equally demanding of a next action to be determined."

How do you track actions required for your areas of responsibility? Do you track these actions differently than you do actions for projects that have definite completion possibility?

I am interested because most of my work are areas of responsibility rather than projects that can be completed, to use your terminology.