Discussion on:

The IT dashboard: Five metrics that spell success

I need some specific examples please, like what should go into Project Pipleline Status for the implementation of an Inventory system?

We've implemented the outages and support metrics. We've also started on the user satisfaction by sending out a short survey on a sample of closed support calls. Budget and spend are available elsewhere, but project status is probably what's missing and I agree it's an improtant part of the overall picture.

If the latter, doesn't matter what the metrics are.

Well unless you count, how much squinting you have to do before the metric can be used to point the figure at the wrong person...

I found your metrics reasonable, but I wonder about other metrics that you did not include. Items that I would have on the list are change success rate (because it is the major determinent of outages); incident escalations (because this causes higher cost and upset customers), project health (because it is a great aggregate for project performance overall), and post release bug capture (because this is a great proxy for quality and project processes). This is just a few that come to mind.