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

Displaying articles for: January 2013

Complex IT, made simple

Rafa2.jpgI don’t do New Year’s resolutions - but once again this year I made a personal commitment to “Add more value by focusing on what really matters.”  The problem is, with IT today playing such a transformative role in driving business change, more and more of what we all do “really matters”. In fact, it’s business critical.


Optimizing your service delivery through improved problem management

IMG_1614-Edit_SML.jpgIn my most recent post, I wrote about good IT configuration management. This post turns to the discipline of problem management: identifying and classifying problems; determining their root causes; and providing timely resolution to prevent recurring incidents. Doing this well accomplishes many things, including increasing availability, improving service levels, reducing IT costs, and improving customer satisfaction by reducing the sheer number of operational problems.

HP technology to get from "Ideas to Outcomes"

four roads to 2020.pngIn this post, I look at the four technologies that HP is investing in that will help us get to faster, better "Ideas to Outcomes" in 2020. 

5 steps to leading a successful government IT transformation project

davidwray.jpgBy David Wray, Chief Technology Officer, HP Software Federal Professional Services


In my last blog post I talked about the two ingredients that go into the “secret sauce” for IT transformation: evangelistic leadership and application rationalization. Knowing the secret sauce is nice, but now you’ve actually got to act on it. And there’s a lot more to leading change than simply having an ingredients checklist.


Now, many of the federal agencies I work with know they need to change. The IT Reform program and related initiatives such as Federal Data Center Consolidation have put forth a vision of sweeping change in federal IT. In May 2012, the OMB released its digital strategy for creating a 21st century digital government and U.S. Federal CIO Steven VanRoekel introduced the IT Shared Services Strategy. To achieve these visions, agencies will have to consolidate applications, create shared services and seize opportunities in mobile and big data. The mandate for change in federal IT has never been clearer. But as agencies start with varying degrees of success to change, I see a lot of false starts. Federal IT is an extremely siloed environment, and all those silos make it very difficult to lead transformative change.  


Let’s look at one area in which federal IT needs to change: application transformation. It’s hard, but I know it can be done. Here’s a five-step blueprint for leading change based on my own experience working with agencies.

Labels: Federal IT

To lay the foundation for a successful transformation understand your 3 stakeholder levels

joshuabrusse.jpgBy Joshua Brusse, Chief Architect, Asia Pacific and Japan, HP Software Professional Services


I’ve written before about the importance of managing change—this is what the success of your transformation depends on! And yet, even when leaders recognize that they need to pay attention to managing change, I still see them struggling to lead transformation.


To lay the foundations for a successful IT transformation I advise leaders to start with the concept of stakeholder management. Organizations tend to think about the stakeholders as the senior sponsors: the organizers and the leaders. And then they think about the other people as just other people—not stakeholders. But my view is always that anyone who has a vested interest in the change or is affected by the change is a stakeholder. This approach helps you avoid any exclusions. You just consider that everyone is a stakeholder. And this is the truth: Everyone is affected by change.


The Three Ways: The principles underpinning DevOps

Exec-Kim.pngBy Gene Kim

Researcher, DevOps guru and former CTO Gene Kim recently co-authored The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win. The novel, written with Kevin Behr and George Spafford, demonstrates just how bad enterprise IT can get—and how the right approach can save the entire business. The following guest post recently appeared in Kim’s IT Revolution newsletter.

(Discover Performance readers can download an extended 170-page excerpt of the book here.)


In The Phoenix Project, our protagonist, Bill Palmer, the acting VP of IT Operations has ninety days to figure out how to get the most critical projects deployed, increase their uptime, and get the auditors off their back!

Through the course of the book, Bill learns about “The Three Ways,” which are the principles that all DevOps patterns can be derived from.  By putting The Three Ways into practice, Bill figures out how to replicate his own “good to great” transformation.

Labels: DevOps

Optimizing your configuration management

IMG_1614-Edit_SML.jpgIn my most recent post, I wrote about good IT asset management. This post looks at what some could say is the reverse image of asset management, configuration management. Configuration management is about defining and maintaining information on all your IT assets and their overall relationship. With good configuration management you greatly reduce your business risk because you can more easily see the effect of any proposed change. Configuration Management and Configuration Management Databases (CMBD) obviously have been hot topics for several years because of the need for IT organizations to establish fundamental control over their IT infrastructure. Naturally, interpretations of configuration management can vary from company to company. Typically, people mean one of the following:

From "Ideas to Outcomes" in 2020


Every organization, government or enterprise, takes ideas and makes them reality. For most organizations, the faster they can do this and the more they can maximize the outcomes when their ideas become reality, the more successful they will be.  


This blog post looks at the steps in the "ideas to outcomes" process and how they will change as we head for 2020.

Looking for huge gains in productivity and time-to-market? Plan for disruptive improvement in IT Ops

Keith small.jpgBy Keith Macbeath, senior principal consultant with HP Software Professional Services


I was recently in the UK where HP is working with a government agency to create a completely new system reflecting a policy change.  This is a big IT project: It needs to factor in different business rules both for validation and execution that reflect the new policy approach. So here’s an opportunity to totally rethink the infrastructure. What the team  is coming up with is a model where there’s fully automated service creation, provisioning and discovery. It’s essentially a fully automated end-to-end private cloud.


That’s a big disruption. Harvard Business School professor Clayton Christensen uses the phrase disruptive innovation to talk about innovation that creates new value and disrupts existing markets. Well, disruption happens in IT operations, too—call it disruptive improvement. Christensen talks about disruptive innovation being an entirely different animal from incremental innovation. Likewise, disruptive improvement is an entirely different animal from the traditional ITIL mindset of continual improvement.


Here are two tools for disruptive improvement.

Labels: IT operations

HP Discover Performance ebook preps CIOs for 2013

Technologists and IT thought leaders provide insights to help CIOs map out 2013 — and beyond.

Fix these 2 things for service management that moves at the speed of cloud


Some people think that adopting cloud means you no longer need to do service management. Now this is truly wishful thinking, because all the things you did with service management still apply with cloud. It doesn’t just go away. But what I find is that many organisations don’t know how to adapt their ITSM practices to a cloud world.


This problem has its roots in a false premise about service management. Fundamentally the argument goes that in a modern, agile business things move too fast for ITIL and service management. There’s this perception that service management would stop the benefits of the cloud. Now, I don’t believe this at all. But I also recognize that in a cloud-enabled world, you can’t have a change management process that takes three weeks to decide to do something. 

Labels: ITSM

2 goals for optimizing asset management

IMG_1614-Edit_SML.jpgIn recent posts, I have discussed several aspects of IT Service Management. This post looks at another element, Asset Management. If you’re not familiar with this topic, the asset management process is about managing IT assets through their life cycle to make sure that their use delivers value at an optimal cost. To do this, assets need to be accounted for, physically protected, and made reliable and available.


The asset process needs to consider software as well. For software assets, the process is about ensuring that the optimal number of licenses are acquired, retained, and deployed in relation to business usage requirements and that installations are in compliance with license agreements. Software asset management, therefore, is a balancing act between perceiving customer needs and not over purchasing unneeded assets. Simply, put the goal for this process is to account for all IT assets and optimize the value provided by them.

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.