4: Baseline, instrument, monitor, report and repeat

Posted on 2012-05-14 by Kevin

4: Baseline, instrument, monitor, report, repeat. “If you can’t measure it you can’t manage it” goes the saying. From the outset it is important to have key metrics about the current system. There will be detractors who will say “it used to take me 10 minutes to do this and now it takes all day.” If you have gathered metrics about the activity times, volumes, error rates, exception counts etc. you will be able to show the before and after differences. And as the roll out proceeds you will be able to see when the improvement rate changes. Ensure that, as part of your design, you instrument the process with KPI’s for each user role and make the reporting on these data points a priority.

About Kevin

In the past year Kevin has spoken at 20 conferences and seminars on a range of leading IT topics, including methodologies, business analysis, quality assurance techniques, governance, open source issues, tool interoperability, release management, DevOps, Agile, ITIL, from the mainframe to distributed platforms to the web, mobile, wearable and embedded systems. He is a much sought-after speaker, recognized around the world for his provocative and entertaining style. Kevin is a 40-year industry veteran, holder of three technology patents and today is a Technology Marketing Evangelist. In the past decade he has been crossing the globe and has met with over 4,000 people. He works closely with industry analysts, the press, customers, partners and employees to exchange ideas about industry direction and business issues. He was born and educated in the UK and lives and works in the Bay Area, California.

View all posts by Kevin →

This entry was posted in Business and Technology and tagged ALM, BPMS, Business, Disruptive Innovation, Orchestrated Application Delivery, Orchestrated Service Management, Process automation, Release Management, Requirements Management, Technology. Bookmark the permalink.