2. “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.”
“Top Six Strategies to Optimize Change Management” George Spafford, 8 December 2014
15 December 2014 ITinvolve Confidential 2
3. 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
4. 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.
“Top Six Strategies to Optimize Change Management” George Spafford, 8 December 2014
15 December 2014 ITinvolve Confidential 4
5. Establishing relevance
1. Establishing relevance
Begin with WHY!
Ensure planned worked doesn’t succumb to daily firefighting
ITinvolve captures and promotes why you are making each
change
15 December 2014 ITinvolve Confidential 5
6. Shifting behavior from “hero worship”
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
15 December 2014 ITinvolve Confidential 6
7. Balancing speed with risk
3. Balancing speed with risk
Know the risks right away
Recognize changes carry different risks and urgency
ITinvolve automatically identifies all upstream and downstream
risks & helps establish the right level of process to address them
15 December 2014 ITinvolve Confidential 7
8. Ensuring accountability
4. Ensure accountability
Facilitate and document change approvals / non-approvals
ITinvolve manages and documents change approval workflows
including escalations as needed
15 December 2014 ITinvolve Confidential 8
9. Evolving change management
5. Evolve change management
Begin 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
15 December 2014 ITinvolve Confidential 9
10. Integrating change management
6. Integrating change management
Change 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
15 December 2014 ITinvolve Confidential 10