Discover Performance Blog

Welcome to the Discover Performance blog, a resource for enterprise IT leaders who share a passion for performing better. Here you’ll find strategic insights and best practices from your peers as well as from HP’s own practitioners who help others define, measure and achieve better IT performances.

For additional in-depth articles on critical topics for IT executives, visit

7 goals for taking business and IT risk out of your change management process

IMG_1614-Edit_SML.jpgIn a recent post, I discussed the importance of service agreements. This post looks at a major factor in whether services are in fact delivered as expected: how well changes and releases are managed. Change and release matter to the business and IT because “30-50% of the incidents in an organization are as a result of a change” (ITIL Version 3.0 Service Transition Book Draft, Page 25).  For this reason COBIT 5.0 says the management of change and release is about ensuring these functions are done in a “controlled manner.” Creating better control is built upon establishing standards, procedures, prioritization, and authorization.

How to reduce business and IT risk while limiting security vulnerabilities!

IMG_1614-Edit_SML.jpgIf emergency changes aren’t already a big issue for your IT shop, they should be. Why? Well, let’s get clear on what an emergency change is in the first place. It is a change that is recorded after the change has been implemented. It has been recorded largely for compliance reasons. Often it can be a change to fix an implementation gone south. COBIT 5 worries enough about this category of changes that it has even created a KPI to measure emergency changes that are not approved post implementation.

Limiting change failure + revenue loss during the holiday season

IMG_1614-Edit_SML.jpgA few years ago, I got to work with a major financial institution.They told me they were interested  to see their data in our product (we were using an early version of what would become the HP Executive Scorecard) and assured me they were particularly good at incident management.   But when we loaded their incident data into the scorecard I was shocked. This customer had given us four months of data—October through January. There were 20,000 incidents a month in October. But in the months that followed this number grew to 65,000 incidents a month. Even worse, incidents resolving in a day or less dropped by 75% after October. And core systems failures quadrupled. What had happened?

Delivering fast, reliable, and risk-mitigated change and release using COBIT 5

IMG_1614-Edit_SML.jpgIf you’ve been following my series of posts on COBIT 5, you already know that I think the new release of the COBIT standard will help IT organizations achieve greater financial transparency, customer satisfaction, operational excellence, and future orientation. Today, we will focus our attention on what COBIT 5 can teach us about optimizing change and release management.

Showing results for 
Search instead for 
Do you mean 

Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.