CHANGE MANAGEMENT NOTES
CHANGE MANAGEMENT NOTES
To be effective, the change management strategy 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, communicating change, scheduling and
implementing change, documenting change and 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.
To understand how change management works, it helps to apply its concepts and tools to specific
areas of business. Below are examples of how change management works for project
management, software development and IT infrastructure.
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. An acceleration of the project schedule, in particular, can affect
quality as defects can occur if work 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 of materials and contract
labor.
When an incremental change has been approved, the project manager documents 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 can be used to manage many types of organizational change. The three
most common types are the following:
In addition, here are some ways that change management can help add structure to IT and
operations:
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. Additional change management challenges include the following:
As a conceptual business framework for people, processes and the organization, change
management increases the success of critical projects and improves a company's ability to adapt
quickly.
Business change is constant and inevitable, and when poorly managed, it has the potential to
cause organizational stress, as well as unnecessary and costly rework.
By standardizing the consistency and efficiency of assigned work, change management assures
that the people side of an organization is not overlooked. As changes to work occur, change
management helps employees understand their new roles and build a more process-driven
culture.
Change management also encourages future company growth by enabling it to remain dynamic
in the marketplace.
Three principles of change management build on the three stages of change management
introduced by Kurt Lewin in his seminal book, Principles of Topological Psychology:
Unfreeze the current state. Change agents need to identify what precisely they want to
change. At this stage, they need to formulate a "why" that other participants are likely to
buy into. In essence, they need to reverse-engineer the future state and translate this
benefit to other possible participants. Then, they need to enroll people who can
participate in the new idea. This could include executive sponsorship for a big change or
co-workers for a departmental change.
Change the system. At this stage, change agents and any collaborators can begin to put
the change into practice. The change agents need to work with collaborators to
communicate the idea and bring other participants on board. It is important to pay
attention to any pushback and find areas of shared understanding to either help move the
change forward or shift its implementation in response to feedback. Tensions might be
high as everyone gets used to the new system. It's important to be respectful of their
feelings and ideas.
Refreeze. Eventually, people get used to the new system, or they revert back to what was
working before. At this stage, it is important to declare that the change is over -- whether
the change was accepted or rejected. Even if the change was rejected, declaring it over
gives everyone a chance to relax. It is also helpful at this stage to document what
happened for future reference.
In general, no one likes to change, even it is for the better in some way. Here are some best
practices to help mitigate this resistance to change:
Clarify the goal of the change being made, and identify how it can benefit others.
Listen to objections, and find ways to address them.
Take the time to build consensus rather than bulldoze dissenters.
Consider feedback as a guide rather than an obstacle.
Celebrate success at the end to plant the seeds for further change.
Be willing to backtrack when the change does not meet desired goals.