Thinking about the Next Steps
This blog is about Measuring stuff. So, what "stuff" should be measured? Scorecard is our initiative to measure important aspects of the UEN network. I love the idea of quantifying. Quantifying and accountability go together. It is my goal to elevate the level of accountability at UEN. We can't get there without measuring. But, again, what should we measure?
Certainly circuit utilization, bit error rates, CPU utilization and some form of down time should be observed, measured and reported. Down time has always been difficult to deal with.What does that mean? Is it scheduled, unscheduled or all down time that is signficant? Is down time during non-working hours significant? Is there any such thing as non-working hours on a network? Reporting down time. Easy to discuss, tough to understand, tougher to make happen.
I've put significant time into considering what to measure. From a network perspective it is fairly straight forward. And I'm looking with interest to Scorecard.
But what if we are measuring the wrong thing? Or, more to the point, what if the user doesn't care about all of our network performance measurements? What if the user only cares about her/his experience with the network? How do we measure that? Perhaps the user experience and perspective is the only valid measure of network performance.
What about that?
Tomorrow: Scorecard or Report Card? What's the difference?