Change management

Change management is the discipline of preparing, supporting, and helping individuals and organizations make transitions. It encompasses the processes, tools, and techniques used to manage the people side of change - ensuring that changes are adopted and sustained rather than resisted and rejected. While project management focuses on the technical aspects of change, change management focuses on the human aspects.

Why it matters

Organizations don't change - people do. A new system, process, or strategy is only as good as people's willingness and ability to adopt it. Change management matters because without deliberate attention to the human dimension:

Adoption fails. People continue doing things the old way, making the investment in change worthless.

Productivity drops. Poorly managed transitions create confusion, frustration, and disengagement that hurt performance.

Resistance grows. Unaddressed concerns harden into opposition, making future changes even harder.

Talent leaves. People who feel changes are done to them rather than with them often choose to leave.

The cost of failed change isn't just the wasted investment - it's the organizational capability to change in the future.

Change management models

Several frameworks guide change management practice:

Kotter's 8-Step Model. Creates urgency, builds a guiding coalition, forms strategic vision, enlists a volunteer army, enables action by removing barriers, generates short-term wins, sustains acceleration, and institutes change.

ADKAR Model. Focuses on individual change through Awareness, Desire, Knowledge, Ability, and Reinforcement. Useful for understanding where individuals are stuck.

Lewin's Change Model. Describes change in three stages: Unfreeze (prepare for change), Change (implement), Refreeze (stabilize). Simple but captures the essential dynamic.

Bridges Transition Model. Distinguishes between change (external, situational) and transition (internal, psychological). Focuses on helping people through the ending, neutral zone, and new beginning.

Each model offers different insights. Practitioners often combine elements from multiple frameworks.

The change management process

Effective change management typically includes:

Assessment. Understand the change itself, who's affected, current readiness, and potential resistance. This informs the change strategy.

Planning. Develop communication plans, training plans, sponsorship roadmaps, coaching plans, and resistance management approaches.

Implementation. Execute the plans while monitoring adoption and adjusting based on feedback. Support people through the transition.

Reinforcement. After initial implementation, ensure change sticks through recognition, accountability, feedback, and corrective action.

This isn't a one-time process - it operates throughout the change lifecycle.

Key change management activities

Sponsorship. Visible, active executive support for change is the strongest predictor of success. Change managers ensure sponsors understand their role and fulfill it.

Communication. Multiple messages, through multiple channels, over time. Effective communication explains the why, not just the what.

Training. Building the skills people need to work effectively in the new environment. Training should be timely - close to when people will use the skills.

Coaching. One-on-one support helping individuals work through their personal transition. Especially important for managers who must lead change for their teams.

Resistance management. Identifying sources of resistance and addressing root causes. Resistance often contains valid concerns that, addressed, improve the change.

Resistance to change

Resistance isn't irrational - it's often a reasonable response to uncertainty, loss, or bad past experiences. Common sources:

Fear of unknown. Change creates uncertainty. People may prefer known difficulties to unknown possibilities.

Loss aversion. Change involves losing something - status, expertise, relationships, comfort. Losses feel larger than equivalent gains.

Lack of trust. Past changes that went poorly, or leaders who haven't earned trust, make current change harder.

Bad timing. People can absorb limited change at once. Too much change creates overload and resistance.

Perceived unfairness. If change seems to benefit some at others' expense, those on the losing end resist.

Disagreement. Sometimes people resist because they genuinely believe the change is wrong. This deserves engagement, not dismissal.

Understanding resistance sources enables addressing them appropriately. Forcing through resistance rarely works; addressing root causes often does.

Change management in product development

Product managers encounter change management in multiple contexts:

User-facing changes. Product changes require user adoption. Change management principles apply to feature launches, redesigns, and migrations.

Internal process changes. Adopting new tools, methodologies, or team structures requires managing change within the product organization.

Organizational changes. Restructures, leadership changes, and strategy shifts all benefit from change management.

Customer success. Helping customers adopt and succeed with your product is essentially change management work.

Change fatigue

Organizations undergoing continuous change face change fatigue - the exhaustion that comes from too much change too fast. Signs include:

Managing change fatigue requires prioritizing changes, ensuring adequate stabilization periods, and being honest about change capacity limitations.

Measuring change management

Change management success is measurable:

Speed of adoption. How quickly do people start using the new way? Faster is better, to a point.

Ultimate utilization. What percentage of people ultimately adopt the change fully?

Proficiency. Are people effective with the new approach? Errors, productivity, and quality indicate proficiency.

Organizational health. What's the impact on engagement, turnover, and performance beyond the change itself?

Tools like Klero support change management by capturing how users experience product changes. Feedback revealing confusion, frustration, or workarounds signals where change management needs attention.