Change Management is not a step at the END of your project. Change Management is all about HOW you approach your project.
In this lesson, we'll review the basics of change management.
Introduction to Change Management:
The purpose of Change Management is to ensure successful adoption of a change within a team or an organization. It's addressing the people side of change, as opposed to the technical aspects of a change.
We need change management any time we change:
- how process is performed
- roles & responsibilities within a team or a department
- strategy, objectives or goals
Organizations, process improvers and project leaders typically underestimate the level of effort needed to prepare for change. Most project teams wait until they are ready to implement an improvement, then decide they need a "Change Management Plan". This is a setting them up for failure.
Change Management is not a step at the END of your project. Change Management is all about HOW you approach your project. It's a part of every step in the problem-solving process. When you're solving the right problem, and actively engaging your customers and your stakeholders throughout the project, adoption of the change will much easier!
Three common change management terms:
- Preparing for successful adoption of change within an organization
- Related to continuous and process improvement; Focused on the people side of change
- Ensuring changes to a software or system have been properly reviewed, tested, documented and approved before implementation
- Related to quality management, software or IT
- Sometimes considered as a step within Change Management
Management of Change (MOC):
- Ensuring a change does not impact health, safety or the environment
- Related to Occupational Safety and Health Administration (OSHA) Process Safety Management
Here at CII, we're focused on Change Management. If your project results in a change within a software system, you may also need a Change Control plan.