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

Out of the box adoption isn’t enough

michael-garrett2.jpgI’ve written several posts about how to successfully implement software out of the box and drive user adoption—two important factors in achieving ROI and successful transformations. One of the keys lies in ensuring that you’ve delivered the business case. In working with customers, however, we’ve found that this can often be a difficult journey to map.


But what if you had a proven methodology and set of best practices that essentially showed you how to get alignment between stakeholders, deliver the business case, deploy software rapidly with a minimum of customization and increase user adoption? In this post I’ll share some of what we’ve learned about enabling rapid deployment. (For more insight from HP Software Professional Services, see our new ebook ‘Deliver business value.’)

6 months after your software project is finished, will this mistake come back to haunt you?

michael-garrett2.jpgIn HP Software Professional Services we often see situations like this: You’re rolling out new technology to customers and you’ve taken care to drive initial adoption. But as you start to get staff churn and the project’s starting to be a few months past implementation, you find yourself facing new challenges. How can your people keep their skills fresh after initial training? How do they retain knowledge of the tools and processes?


A year out, perhaps you’ve churned 20% of your staff, you’ve changed the system, changed your processes to meet business needs or are rolling the technology out to a new department—how do you make sure you don’t have to go back to square one? You don’t want to have to go back to your vendor, bring them in again, have people relearn the technology—not to mention spend a bunch of money doing so.


I’ve written before about the three keys to driving adoption. But although driving initial adoption is important, it’s just one piece of what should be an ongoing usage model. Here is what you can do to derive maximum business value from your technology investments.

3 key factors for successful software adoption

michael-garrett2.jpgIn my last post, I wrote about how IT often wants to implement new solutions, but then undermines the potential benefits by not adequately driving user acceptance and adoption.


In many cases software projects fail because they don’t get adopted in the end, and so the value isn’t returned. Or they continuously slip as the project is changed more and more and more through implementation.


So how do you drive adoption? Based on my experience as head of HP Software Professional Services, these are the three key factors.

You want to implement software out of the box? Here’s how

michael-garrett2.jpgHave you ever experienced this scenario? You’ve delivered a software implementation, it gets into user acceptance testing and users don’t like what they see.


This is a classic situation in IT—and unfortunately it occurs all the time. But why has it occurred? And how do you stop yourself from getting into this position?


We see this quite a lot in HP Software Professional Services, particularly in organisations that try to implement something out of the box. Customers will say, ‘Well, we want to go out of the box’. But then they don’t lay the proper groundwork. The software gets in front of users and they’ve got all sorts of problems with it. At some level the organisation hasn’t considered the impact this change is going to have on their business.

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.