DON’T BE A STATISTIC!
Originally published in ITSM Review December 2012
For decades the industry experts have been telling us that 70% of organizational change fails. These experts include recognizable names such as Kotter, Blanchard, and McKinsey. It’s a scary story! This means that 70% of changes fail to recognize a return on investment, and achievement of stated goals and objectives.
In service management the change could be the introduction of new technology, organizational restructure or process improvement. These changes could represent a significant investment of time, money and resources. So can we afford not to break the cycle and allow history to keep repeating itself?
Not only do failed changes result in wasted time, money and effort but they also make subsequent changes even harder. Failed changes result in cynicism, lost productivity, low morale and change fatigue. Expecting people to change their ways of working will be increasingly harder if they have been subject to a series of failed change initiatives in the past.
It is my belief that 70% of changes fail due to the lack of focus on organizational change. Projects have specific objectives including on time, on budget and delivery of specified functionality. Projects install changes but do not implement them unless organizational change is included within the project.
If a change is to be truly embedded into the fabric of the organization and recognize the desired outcomes, there has to be a focus on the people. Organizational change is a challenge to many because it involves people and every one of those people is different. They have different desires, beliefs, values, attitudes, assumptions and behaviors. An individual may embrace one change because it is aligned with their value system and they can answer the “What’s in it for me?” (WIIFM) question. The next change may be rejected because that question cannot be answered or the change is perceived to have a negative impact on the individual, their role or their career.
Therefore before we embark on any change we need to clearly identify the target audience. That is any one who may be impacted in anyway by this change, both directly and indirectly. We need to understand the target audience and their level of awareness for the need to change.
Through identification of the right sponsors for the change at every level within the organization, equipping them with the skills and capability to raise awareness and create a desire to change we are more likely to have a successful outcome.
Announcing a change is not the same as implementing the change!
A communication strategy and plan is a key component of the organizational change program. It needs to address the needs of the audience, the key messages and how they will be packaged and delivered. The sender of the message is important. Messages around the business need for change are received better when they are delivered from the CxO level. Messages about how the change will affect an individual are better received from that person’s manager or supervisor.
We also need to select a variety of practices or activities to ensure that the change becomes embedded and people do not revert to old ways of working or their comfort zone.
In 2011 I wrote a book called ‘Balanced Diversity – A Portfolio Approach to Organizational Change’ which provides 59 distinct practices that can be selected from to embed change. Although the framework introduced in the book can be used for any change in any organization, I have discussed how it can specifically be used within IT service management.
In IT we often expect that providing people with some training or undertaking an ITSM maturity assessment will create the desire for change. It takes much more than that and because every change is different we need to use different practices that address the specific needs of the change and the target audience.
I don’t have the space here to discuss each of the 59 practices but a white paper on the subject can be read here.
Finally it is critical to keep checking back to ensure that the change is being successfully embedded into the organization. We often talk about the Demming cycle in IT service management but don’t apply it to organizational change. We need to plan what practices we are going to use to embed the change, do them but them continually check back to ensure they are having the desired effect. If they are not, we need to act before the situation is irretrievable.
If you don’t want to become a 70% statistic and you want to ensure that your changes are a success, get some organizational change capability on your projects. It will be worth the investment.