6 reasons why change management fails
TRANSCRIPT
Better Change Management
“Through 2018, up to 80% of the incidents I&O encounters will be caused by failed changes in organizations that have not implemented an effective change management process, a percentage relatively unchanged from 2013.”
15 December 2014 ITinvolve Confidential 2
“Top Six Strategies to Optimize Change Management” George Spafford, 8 December 2014
Every change has risk; so balancing risk with speed is the key to change success.
How can you move faster while also minimizing risk?
15 December 2014 ITinvolve Confidential 3
Top 6 reasons Change Management fails
1. IT and business stakeholders fail to see how change management is relevant to the organization, and they identify it as wasteful.
2. Change management requires a significant shift in behavior, including a movement away from ‘hero worship’.
3. Change management processes are implemented that do not properly balance the organization’s need for speed with its need for risk management, causing stress.
4. Management has no way of detecting who is making changes; therefore, the staff responsible with making changes to the production environment intentionally bypass the change management process and accountability breaks down.
5. I&O management attempts to implement all elements, including advanced capabilities, of the change management process in one step, rather than evolving it.
6. Change management is not sufficiently integrated with other key processes, which stifles its ability to operate efficiently and effectively.
15 December 2014 ITinvolve Confidential 4
“Top Six Strategies to Optimize Change Management” George Spafford, 8 December 2014
Establishing relevance
15 December 2014 5ITinvolve Confidential
1. Establishing relevanceBegin with WHY!Ensure planned worked doesn’t succumb to daily firefighting
ITinvolve captures and promotes why you are making each change
Shifting behavior from “hero worship”
15 December 2014 6ITinvolve Confidential
2. Shifting behavior from ‘hero worship’Working independently is an illusion of competence in today’s complex environments
ITinvolve identifies and engages everyone that needs to be involved from both IT and the business
Balancing speed with risk
15 December 2014 7ITinvolve Confidential
3. Balancing speed with riskKnow the risks right awayRecognize changes carry different risks and urgency
ITinvolve automatically identifies all upstream and downstream risks & helps establish the right level of process to address them
Ensuring accountability
15 December 2014 8ITinvolve Confidential
4. Ensure accountabilityFacilitate and document change approvals / non-approvals
ITinvolve manages and documents change approval workflows including escalations as needed
Evolving change management
15 December 2014 9ITinvolve Confidential
5. Evolve change managementBegin where need is greatest (e.g. approvals, impact analysis)Leverage metrics for improvement
Deploy ITinvolve functionality in phases as needs expand; Track & report on change activities for continual improvement
Integrating change management
15 December 2014 10ITinvolve Confidential
6. Integrating change managementChange must not exist in a vacuum but integrate with configuration, release, incident, and problem management
ITinvolve provides a “super CMDB”, coordinates release plans, and provides visibility into all related incidents and problems
Thank you!