This content is part of the Essential Guide: Project management strategies that transform businesses: A CIO guide

change management

Change management is a systematic approach to dealing with the transition or transformation of an organization's goals, processes or technologies. The purpose of change management is to implement strategies for effecting change, controlling change and helping people to adapt to change. Such strategies include having a structured procedure for requesting a change, as well as mechanisms for responding to requests and following them up.

To be effective, the change management process must take into consideration how an adjustment or replacement will impact processes, systems and employees within the organization. There must be a process for planning and testing change, a process for communicating change, a process for scheduling and implementing change, a process for documenting change and a process for evaluating its effects. Documentation is a critical component of change management, not only to maintain an audit trail should a rollback become necessary but also to ensure compliance with internal and external controls, including regulatory compliance.

Companies developing a change management program from the ground up often face daunting challenges. In addition to a thorough understanding of company culture, the change management process requires an accurate accounting of the systems, applications and employees to be affected by a change. Best practice frameworks can provide guiding principles and help managers align the scope of proposed changes with available digital and nondigital tools.

change management plan
This checklist can be used to create a simple change management plan.

Popular models for managing change include:

  • ADKAR: The ADKAR model, created by Prosci founder Jeff Hiatt, consists of five sequential steps:
    • Awareness of the need for change;
    • Desire to participate in and support the change;
    • Knowledge about how to change;
    • Ability to implement change and behaviors; and
    • Reinforcement to sustain the change.
  • Bridges' Transition Model: Change consultant William Bridges' model focuses on how people adjust to change. The model features three stages: a stage for letting go, a stage of uncertainty and confusion and a stage for acceptance. Bridges' model is sometimes compared to the Kübler-Ross five stages of grief (denial, anger, bargaining, depression and acceptance).
  • IT Infrastructure Library (ITIL): The U.K. Cabinet Office and Capita plc oversee a framework that includes detailed guidance for managing change in IT operations and infrastructure.
  • Kotter's 8-Step Process for Leading Change: Harvard University professor John Kotter's model has eight steps:
    • increasing the urgency for change;
    • creating a powerful coalition for change;
    • creating a vision for change, communicating the vision;
    • removing obstacles;
    • creating short-term wins;
    • building on them; and
    • anchoring the change in corporate culture.
  • Lewin's Change Management Model: Psychologist Kurt Lewin created a three-step framework that is also referred to as the Unfreeze-Change-Freeze (or Refreeze) model.
  • McKinsey 7S: Business consultants Robert H. Waterman Jr. and Tom Peters designed this model to holistically look at seven factors that affect change:
    • shared values;
    • strategy;
    • structure;
    • systems;
    • style;
    • staff; and
    • skills.

Popular change management tools

Digital and nondigital change management tools can help change management officers research, analyze, organize and implement changes. In a small company, the tools may simply consist of spreadsheets, Gantt charts and flowcharts. Larger organizations typically use software suites to maintain change logs digitally and provide stakeholders with an integrated, holistic view of change and its effects.

Popular change management software applications include:

  • ChangeGear Change Manager (SunView Software): change management support for DevOps and ITIL automation, as well as business roles.
  • ChangeScout (Deloitte): cloud-based organizational change management application for evaluating sea changes, as well as incremental changes.
  • eChangeManager (Giva): a cloud-based, stand-alone IT change management application.
  • Remedy Change Management 9 (BMC Software): assistance for managers with planning, tracking and delivering successful changes that are compliant with ITIL and COBIT.

Change management certifications

Change management practitioners can earn certifications that recognize their ability to manage projects, manage people and guide an organization through a period of transition or transformation. Popular certifications for change management are issued by:

  • Change Management Institute (CMI): CMI offers Foundation, Specialist and Master certifications.
  • Prosci: The Change Management Certification validates the recipient is able to apply holistic change management methodologies and the ADKAR model to a project.
  • Association of Change Management Professionals (ACMP): ACMP offers a Certified Change Management Professional (CCMP) certification for best practices in change management.
  • Management and Strategy Institute (MSI): The Change Management Specialist (CMS) certification attests to the recipient's ability to design and manage change programs.
  • Cornell University's SC Johnson College of Business: The Change Leadership certification program was developed to authenticate a change agent's ability to carry out a change initiative. The certification requires four core courses and two leadership electives.

Change management in project management

Change management is an important part of project management. The project manager must examine change requests and determine the effect a change will have on the project as a whole. The person or team in charge of change control must evaluate the effect a change in one area of the project can have on other areas, including:

  • Scope: Change requests must be evaluated to determine how they will affect the project scope.
  • Schedule: Change requests must be assessed to determine how they will alter the project schedule.
  • Costs: Change requests must be evaluated to determine how they will affect project costs. Labor is typically the largest expense on a project, so overages on completing project tasks can quickly drive changes to the project costs.
  • Quality: Change requests must be evaluated to determine how they will affect the quality of the completed project. Changes to the project schedule, in particular, can affect quality as the workforce may generate defects in work that is rushed.
  • Human resources: Change requests must be evaluated to determine if additional or specialized labor is required. When the project schedule changes, the project manager may lose key resources to other assignments.
  • Communications: Approved change requests must be communicated to the appropriate stakeholders at the appropriate time.
  • Risk: Change requests must be evaluated to determine what risks they pose. Even minor changes can have a domino effect on the project and introduce logistical, financial or security risks.
  • Procurement: Changes to the project may affect procurement efforts for materials and contract labor.
  • Stakeholders: Changes to the project can affect who is a stakeholder, in addition to the stakeholders' synergy, excitement and support of the project.

When an incremental change has been approved, the project manager will document the change in one of four standard change control systems to ensure all thoughts and insight have been captured with the change request. (Changes that are not entered through a control system are labeled defects.) When a change request is declined, this is also documented and kept as part of the project archives.

Change management in software development

In software project management, change management strategies and tools help developers manage changes to code and its associated documentation. Agile software development environments actually encourage changes for requirements and/or the user interface (UI). Change is not addressed in the middle of an iteration, however; they are scheduled as stories or features for future iterations.

An expert discusses change management and digital transformation.

Version control software tools assist with documentation and prevent more than one person from making changes to code at the same time. Such tools have capabilities to track changes and back out changes when necessary.

Change management in IT infrastructure

Change management tools are also used to track changes made to an IT department's hardware infrastructure. As with other types of change management, standardized methods and procedures ensure every change made to the infrastructure is assessed, approved, documented, implemented and reviewed in a systematic manner.

When changes are made to hardware settings, it may also be referred to as configuration management (CM). Technicians use configuration management tools to review the entire collection of related systems and verify the effects a change made to one system has on other systems.

This was last updated in January 2018

Continue Reading About change management

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

This article is so powerful. It's true without change no changes.
We are planning to work for one and we need opinion from the others.
Does your organization have change management policies in place?
None, many projects fizzle out midway
I've observed such policies in place at the most of organizations I worked at, as well as I observed clever "workarounds".
Not yet..
We do, we have a Change Control Board, and an extremely tedious process involving change requests.
Vailbhavrajebhosale, will you have change management policies in place for 2016? 
We do have an application and infrastructure CM process in place. The change manager has worked with the rest of IT to ensure that we don’t run into issues as noted above. The process is effective managing change, yet lightweight enough to handle changes pushed to production vi the CD pipeline.
Is any document change like preparation of new scripts for lets say OS hardening is also require change control and why?
Margaret, did you do an analysis on how many companies are using change management?


File Extensions and File Formats

Powered by: