I have watched many teams struggle when there are scope shifts, time gets compressed, or there are changes to stakeholder priorities. The truth is that almost every project faces significant changes during execution, and without proper management, these changes derail even the best-laid plans.
Change management in projects means being able to understand the challenges and obstacles brought upon by bad changes, making sure that they are managed and do not cause the project to become part of the 70% of change initiatives fail statistic that continues to impact organizations globally. Knowing how to manage change and the challenges it brings is important in being able to protect time, cost, and team spirit. This solid foundation is acquired through the PMP certification training. The training gives you the needed skills and management frameworks to ensure that chaos does not ensue during your projects.
Change management pertains to the processes and tools that are designed to assist in managing change at an organizational level or project level. This consists of 2 main components, namely managing the change itself and the people affected by the change.
At a project level, change management is needed to ensure that all changes to a project management plan are approved and documented. This will ensure that there are no scope, time, or cost changes that will cause a surprise to the project team.
To illustrate, project management brings the technical solution within the deadline and budget. Change management makes sure people embrace and successfully make use of that solution. They both serve the same purpose from different angles.
Terms are often misused here. What matters is the difference.
Change control is about decision-making. It could be about a request to include an additional feature. The change control board looks at cost, timeline, and value and makes an approval/rejection decision.
Change management is about what happens next. After approval, what needs to be done to assist people in adjusting to the new ways? This is about setting the reasons for the change, training, new ways of measuring, and ongoing support to assess where people are.
Consider a new electronic health record system in a hospital. Change control approves the chronology for the purchase of the system and the execution of the implementation. Change management makes sure that the training is done so that the physicians, the nurses, and the other staff understand the system, the advantages of the new system, and are able to shift from the old ways to the new ways.
Projects experience four primary categories of change. Knowing what type you are dealing with helps you to adopt the right strategy.
Anticipatory changes involve preparing for situations you expect to happen. For instance, when a senior employee is planning to retire, you make succession plans. These changes allow you to prepare comprehensively.
Reactive changes address unplanned events. A shift in the market or a crisis is likely to necessitate quick decision-making and adjustments. There is little time to plan, your team must move quickly.
Incremental changes introduce a series of complex shifts gradually. In this context, adding certain features to software is a typical example. These small changes probably won't create major disruptions to the systems or processes.
Strategic changes, on the other hand, are all-encompassing changes that affect the entire organization. These involve a lot of planning, money, and resources to make changes to the entire technology infrastructure of the company and reshuffle how business is done.
In the absence of good change management, I have seen projects failing to an astounding degree. Unfortunately, the problems go much deeper than the immediate frustration of the people involved.
If the processes are not top-down, the day-to-day activities will quickly become chaotic. In the absence of any plans, small changes in a workflow will create a lot of confusion. If employees are not aware of how the structure or the systems have changed, productivity declines--even in situations that should be simple.
The risks of major changes are even higher. Strategic adjustments forced certain elements of processes and structure to change. When there are no good mechanisms for managing change, there is resistance from the teams, stakeholders push back, and the entire project is likely to fail.
The benefits of project management systems are intensified when paired with robust change processes. Effective systems minimize disruption, encourage acceptance, empower performance, and foster a culture of flexibility.
While a system is configured, other processes must also be put in order. Here is my approach.
What are the specific criteria defining the change? Identify and ask: Is the implementation of the system planned or unplanned? Is the change incremental, or will it require a faster change? These criteria will assist in the gathering of relevant data.
Document everything. Providing a detailed change description will assist in the elimination of confusion and resistance later.
Your change vision describes what the organization looks like after successful adoption of the system. This is similar to gap analysis, and it shows the difference between the current and desired states, as well as the benefits of the change.
These criteria will assist in the gathering of relevant data. This vision will be your North Star. If and when team members oppose the change, this vision will help everyone stay focused on why this change is necessary.
There are various frameworks designed for the structuring and organization of change. Kotter's 8-Step Model is effective and prescriptive for large-scale changes that require strong management and leadership. The ADKAR Model, however, is oriented toward the individual and designed for adoption at the levels of awareness, desire, knowledge, ability, and reinforcement.
Choose according to your project scope, company culture, and resource availability. These frameworks are taught as part of the comprehensive PMP certification program, where you learn to correlate the methodology with the situation.
Your change management plan details how change will be handled at the project or organizational level. This includes outlining roles and responsibilities, the composition of the change control board, strategies for communication, and frameworks for training.
This document serves as your roadmap. Everyone should understand their role in ensuring the change succeeds.
Change, in its entirety, is best analyzed with a variety of approaches. Do not hesitate to create a team with differing views. Make sure you have cross-representation from all impacted areas, as well as from the business, a few subject matter experts, and executive sponsors.
Execution in and of itself is not the finish line. Use project management to identify and monitor the impacts using the defined KPIs in project management. Keep an eye on how things are moving, be proactive about problem-solving, and refine your strategy as necessary.
| Models | Best For | Focus | Complexity |
| Lewin's 3-Stage | Simple changes | Process (Unfreeze, Change, Refreeze) | Low |
| Kotter's 8-Step | Large Scale Transformations | Growth in leadership | High |
| ADKAR | Understanding of Individuals | People (Awareness through Reinforcement) | Medium |
| Bridges Transition | Emotional resistance | Managing feelings through change | Medium |
Lewin's model works well for straightforward processes, and Kotter's for organizational change. Each of the models also helps with individual components of resistance in its own way.
The first and biggest challenge is resistance. People tend to resist change, and even more so if no clear reasoning is provided for why the changes are necessary. The best way to combat resistance is to include stakeholders, keep the communication open and show early results (quick wins) to foster confidence in the new changes.
Change is disruptive, and without the proper framework, attempts to change can quickly lose focus. The best way to keep disruptions to the change manageable is to set clear and open channels of communication, listen to questions and comments with the intent to make the change the best it can be.
Limited resources can be disruptive to change, and when change is resource-limited, focus training on key individuals and equip them to train the other employees. Use free, minimal tools and make changes as focused as possible.
The tails of scope creep and budget creep are always circling a timeline. Keep a change itinerary so that every proposed change takes a new gate request and has to pass a change control circle before getting an update.
Cutover is not the first time to engage with change management participants, so begin your engagement with stakeholders, your communication plan, and your training plan well in advance of implementation.
Disclose fully. Trust is rooted in honesty. Describe both problems and progress. People are more likely to back your efforts when they see the big picture.
Be sure to train adequately. Gaps in skills derail adoption. Use varied learning methods, include hands on, and provide support materials that are accessible.
Recognize and celebrate. Motivation is the recognition of the effort. Celebrate the milestones, acknowledge the efforts, and publicly praise the positive results.
Change amplifies the role of leadership in project management. Leaders set the tone, exemplify the behaviours they want, and provide the support teams need to navigate the ambiguity.
Effectively managing change in projects requires both experience and knowledge. Start by reviewing your current practices. Do you have defined processes for managing and assessing changes? Is your team clear on their responsibilities in the course of transition?
Build your base with established methodologies and frameworks. Learning what is PMP certification, shows you how professional bodies deal with change. Such approaches will save you from the chaos that follows when changes are bound to happen.
Keep in mind that change management is not a one-off practice. It is a continuous activity that safeguards your projects from setbacks while increasing the resilience of the organization. Managing change successfully adds to the team's confidence in facing the next hurdle.
Shashank Shastri is a PMP trainer with over 14 years of experience and co-founder of Oven Story. He is an inspiring product leader who is a master in product strategies and digital innovation. Shashank has guided many aspirants preparing for the PMP examination thereby assisting them to achieve their PMP certification. For leisure, he writes short stories and is currently working on a feature-film script, Migraine.
QUICK FACTS
Change control is the process by which an organization reviews and decides whether to reject or approve change requests. Change management deals with the implementation of the requests and helps everyone adjust afterwards. Both are needed to ensure project success.