Change Management

The structured approach to transitioning individuals, teams, and organizations through significant change — from technology rollouts to reorganizations — with the goal of minimizing disruption and resistance.

Change management is the discipline of planning, communicating, and implementing significant organizational changes in ways that minimize disruption, reduce resistance, and improve adoption. It applies to a wide range of organizational transitions: new technology implementations, process redesigns, mergers and acquisitions, restructurings, leadership changes, and strategic pivots. The core insight of change management is that organizational changes fail far more often because of the human response to them than because of flawed strategy or poor execution — and that the human response is predictable and manageable with deliberate effort.

The most widely used frameworks in organizational change management are Kotter's 8-Step Process (create urgency, form a coalition, develop a vision, communicate it, enable action, generate short-term wins, consolidate gains, anchor the change) and the ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) — a framework focused on what individual employees need to move through successfully. Both frameworks emphasize that change doesn't happen to organizations; it happens to people, one at a time — and that the pace of adoption is ultimately determined by the slowest credible voice, not by the change announcement.

For employees navigating organizational change — a new manager, a restructuring, a technology shift, a merger — the experience is often characterized by uncertainty, loss of familiar structures, and a period of reduced productivity known as the 'change curve.' Elizabeth Kübler-Ross's grief stages (adapted for organizational change): denial, frustration, experimentation, and acceptance. Understanding that this curve is normal and predictable helps both individuals and managers navigate it. Organizations that communicate early, involve people in the design of the change where possible, and provide clarity about what's changing and what's not tend to move through the curve faster with less lasting damage to morale and performance.

Why Organizational Changes Fail

Research by McKinsey and others consistently finds that 60–70% of major organizational change initiatives fail to achieve their objectives. The failures cluster around predictable causes: insufficient communication of the 'why' behind the change (people resist what they don't understand); inadequate involvement of the people most affected (resistance is highest when change happens to people rather than with them); underestimating the time and effort required for human adoption (treating change as a launch event rather than a sustained process); and leadership that champions the change verbally while behaving inconsistently in practice. The organizations that change successfully tend to over-communicate rather than under-communicate, invest heavily in manager enablement (managers are the primary interpreters of organizational change for their teams), and measure adoption as rigorously as they measure technical implementation.

Navigating Change as an Employee

  • Seek clarity on what's actually changing and what isn't — rumor fills information vacuums, and the unknown is almost always worse than the reality.
  • Engage with the change rather than waiting it out — people who shape how change happens to them fare better than those who resist or disengage.
  • Express concerns through legitimate channels (manager, skip-level, formal feedback mechanisms) rather than venting — it's more effective and less costly.
  • Give the change time to settle — productivity typically dips during transitions and recovers as new structures become familiar.
  • If the change is fundamental to why you joined (a mission shift, a culture reversal, a role that no longer exists), that's a legitimate reason to reassess the fit — it doesn't mean the change is wrong.
  • Build relationships with the people who will shape how the change is implemented — early relationships with new leadership have outsized influence on your experience of the transition.

Example

A 500-person software company implements a new engineering process requiring all teams to adopt a standardized CI/CD pipeline and code review cadence. Teams that were briefed on the 'why' (reduce production incidents, which had been rising), involved in a pilot phase, and given a 90-day ramp period adopted the change within a quarter with no attrition. Teams that received a top-down mandate with a two-week timeline and no input saw three senior engineers leave and another six months of passive resistance before real adoption.