Health in Decatur or Health indicators
Derek Huether has an interesting thought about Measuring (Project) Health. There are many ways to go about doing this, some useful and some not-so-useful (and some downright destructive). Derek's example this time is more of a check-up on the status of your project work.
In this case, he's interested in how often you talk to people from whom you need advice or assistance but who aren't involved in the project on a daily basis. His suggestion is a little formulaic, but it's a good starting point for thinking about the reality of projects: they don't fit into the neat boxes on a Gantt chart.
[Y]ou need to make sure you do a few things, when interacting with these team members. One, identify the maximum amount of time that will elapse between interactions. Two, identify some threshold criteria. Exceed the threshold and you should be interacting with this team member.
For me a key element of this thought is the reality that projects need input from a wide variety of people, and it doesn't make sense to write all of these interactions into a project plan. Experts and management can help projects move along, but they only know that they can help when you go and ask them. The other part of this is that the experts and managers cannot have their days scheduled and planned to the minute because the project teams will never be able to find them to resolve issues - which should be their job.
I'd rather think of Derek's suggestion as a way to monitor my own tasks and projects, rather than a direct indicator. But then, as he sets up the thought, it's fairly easy to think, "When was my last visit to the doctor."
Sorry about the title. It's an old misunderstanding from when we lived in Illinois. I was talking to my wife about a call I had gotten from a company in Decatur, IL. But we were on the phone and was very confused about a "job indicator."
[Photo: "Decatur after dark" by Joe Harper]
Previous entry: Pay now or pay later. But pay you will.
Next entry: Feeling Lean?