This is Part 2 of a three-part series on change management. In Part 1, I addressed the question, “What is change management?” and examined change management from the perspectives of both process and use case. In this blog, I’ll look at what it takes to make change management initiatives succeed — including metrics and requirements, best practice concerns, and some of the more common pitfalls. Much of the content is derived from past EMA consulting experience as reflected our book, CMDB Systems: Making Change Work in the Age of Cloud and Agile.
Metrics and Requirements
Whether you’re targeting lifecycle endpoint management, data center consolidation, or the move to cloud, it’s important to have some way to measure your progress. These measurements might address operational efficiencies, impacts on the infrastructure and its supported applications, and even impacts on your service consumers and business outcomes. Some of the high-level metrics EMA analysts recommend include:
■ Reduction in number of change collisions
■ Reduction in number of failed changes and re-dos
■ Reduced cycle time to review, approve, and implement changes
■ Improved time efficiency to validate that changes made are non–service disruptive
■ Number of changes that do not deliver expected results
In one consulting engagement in particular, we also saw the following:
■ Degree of conformance to current software licensing agreements
■ Exceptions detected during configuration audits (e.g., when actual state is not as authorized)
■ Cost savings for acquisition and retirement of assets
■ Faster ability to provide services
Of course, these are just a few examples, and these metrics are primarily beginning points. In other words, they are not fully fleshed-out requirements you can use to create the very specific, and hence more measurable, objectives that you will need to go forward.
Going from high-level metrics, such as those above, to more detailed requirements typically means understanding ownership, process, and impact specifics. One example cited in our book involved documented costs in terms of phone time spent in the service desk trying to find the right individual in operations to handle incident-related issues, or what they called “mean time to find someone (MTTFS).” In this case, a CMDB-related initiative saved them nearly $100,000 per year, just in terms of personnel costs of time spent on the phone. The same MTTFS metric might apply to requests involving changes, such as those made in response to service requests or onboarding new end users—where a mixture of IT and non-IT stakeholders for approval and review is often required. Knowing who owns a specific problem for a specific configuration item (CI) is worth its weight in gold.
Some Common Change Management Issues
Developing an appropriate set of metrics and requirements typically involves dialog with relevant stakeholders and executives. While it might be nice to simply legislate your change management initiative with a few emails, EMA consulting experience consistently underscores the need for two-way dialog in which stakeholders are both informed and listened to. These dialogs or interviews not only help to pave the way for new and better ways of managing change, they will usually shed light on other issues that, once documented, can help your IT organization move forward in any number of (sometimes surprising) ways.
Scope Creep: While you want enthusiasm for going forward, and in fact you’ll probably want to target your more enthusiastic stakeholders, many change management initiatives can get bogged down by trying to do too much at once. Two of my favorite quotes from our consulting reports along these lines are:
“The biggest issue now is scope creep. Trying to make everyone happy at this point is like trying to rebuild the Titanic from the bottom up.”
Another change management initiative was more prescriptive: “We’re managing scope creep by being incremental in how we’re driving our deployment—going forward with small steps on a regular schedule.”
Toolset Ownership: Managing changes well requires attention to technologies, both those already in use and new technology investments, as I’ll discuss in my next blog. But making the right technology choices can often become a political as well as a technology challenge. EMA consulting has seen literally hundreds of tools addressing monitoring, inventory, configuration, and change management in larger enterprises, each affiliated with its own determined set of owners. This can create problems when you’re trying to promote more cross-domain capabilities for discovery, automation, and configuration updates. So once again, dialog, leadership, and attention to consistent processes are key. Two quotes from EMA consulting serve to underscore this point:
“We are territorial and don’t want to replace our tools.”
“We have issues with toolset ownership. There is no confidence that others will do the work. So, you do it yourself.”
Issues Surrounding Standards and Best Practices: Whether you’re seeking to leverage processes defined in the IT Infrastructure Library (ITIL) or other formalized best practices or you’re simply documenting your own, trying to establish good change management processes across a heterogeneous and often siloed set of stakeholders may well be your biggest single challenge. Even when good technology is in place, trying to get the necessary mix of players to use it well and consistently is not often easy, especially without some level of executive sponsorship. Here are a few additional quotes from EMA consulting reports to provide you with some process-related examples:
“There are over 5000 change requests per year, and all of them are marked ‘high priority.’”
“Change control needs to hold people accountable if it is to be effective. No one questions why.”
“I believe in standards, as long as they’re mine.”
And finally, something positive: “We had an opportunity to reinvent change management in our organization and go from a project management approach that was very ambivalent when it came to execution to a much more enforceable approach that supported clear ownership and led to increased levels of automation.”
Dennis Drogseth is VP at Enterprise Management Associates (EMA).
The performance gap between customer experience leaders and runners-up is widening, with those on top being disproportionately rewarded. Gartner said organizations must ignore three myths in order to achieve a superior customer experience ...
This summer marked three years since Microsoft announced Windows 10, its first "Windows as a service" Operating System (OS). Windows 10 brought with it a new Software-as-a-Service-like approach to updates, moving Microsoft and the millions of environments that depend on it, more frequent, bundled updates. Whether you believe the shift was for better or worse, one thing is certain, this "as a service" model is a natural progression for today's operating systems. That is why Windows 10 is changing not only how frequently updates are pushed out, but inherently how technology is purchased, how people consume it, and perhaps most importantly, how IT is run. Let's take a look at how Windows 10 has impacted these three key areas over the past three years ...
To celebrate IT Professionals Day 2018 (this year on September 18), the SolarWinds IT Pro Day 2018: A World Powered by Tech Pros survey explores a "Tech PROactive" world where technology professionals have the time, resources, and ability to use their technology prowess to do absolutely anything ...
Are digital war rooms obsolete because they're just a place for managers of siloed business units to find someone else to blame for a critical IT event such as a security breach? Far from it. Enterprises find these emergency response teams just as important, if not more important, than ever ...
The goal of EMA's latest research was to look at how advanced IT analytics (AIA) — EMA's term for primarily what today is best known as "AIOps" — is being deployed. Here are the remaining four of my seven personal takeaways ...
OK, the data is in! The goal of EMA's latest research was to look at how advanced IT analytics (AIA) — or EMA's term for primarily what today is best known as "AIOps" — is being deployed. Here are seven of my own personal takeaways ...
By maximizing the knowledge of end-to-end quality of service (QoS) using virtualized network functions (VNFs), the SD-WAN (edge) gateway establishes a suitable connection with minimal latency and maximum performance so that entire organizations can make the most of the Office 365 application suite ...
Market exuberance for Office 365 has inspired business mandates to adopt the cloud-hosted collaboration and productivity suite without regards to the underlying chaos. While multi-location organizations are virtualizing, operating models haven’t necessarily changed. This partial transformation that excludes automation and simplification of the network puts Office 365 deployments (and other software-as-a-service offerings) in danger of failing ...
Most organizations are undergoing a digital transformation that directly impacts how they do business, yet 70 percent of employees have not mastered the skills they need for their jobs today, and 80 percent of employees do not have the skills needed for their current and future roles, according to Gartner ...
In a survey within the VMware User Group community, Blue Medora took a closer look at how various metric collection strategies and access to Dimensional Data impacts IT success. We started with one question: How important is your monitoring integration strategy? ...