16.3 Managing Change

Change Management Models and Approaches

Change management gives organizations a structured way to move from where they are to where they need to be. Without a deliberate approach, even well-intentioned changes tend to stall, face heavy resistance, or quietly revert back to the old way of doing things. Two of the most widely taught models are Lewin's three-step framework and Kotter's eight-step process.

Steps in change management models

Lewin's Change Management Model breaks change into three phases:

1. Unfreezing — Challenge the status quo and build motivation for change. People need to understand why the current state is no longer acceptable. This is sometimes called creating a "burning platform," where the cost of staying put becomes obvious (e.g., declining market share, a failed product launch).
2. Changing (Transition) — Execute the planned changes. This is the messy middle where restructuring, new processes, or new roles actually take effect. People are learning new behaviors and letting go of old ones, so support and communication matter most here.
3. Refreezing — Stabilize the organization in its new state. New policies, reward systems, and routines lock the changes in place so the organization doesn't drift back to old habits.

Lewin's model is simple and intuitive, which is its strength. The limitation is that it can make change sound like a one-time event with a clear endpoint, when in reality many organizations face continuous change.

Kotter's 8-Step Change Model provides a more detailed, sequential roadmap:

1. Create a sense of urgency — Show stakeholders why change can't wait (e.g., a competitor entering your market, shifting customer expectations).
2. Build a guiding coalition — Assemble a cross-functional team of influential leaders and respected voices who can champion the effort.
3. Form a strategic vision and initiatives — Develop a clear picture of the desired future state and the concrete steps to get there.
4. Enlist a volunteer army — Recruit change champions at every level who will spread enthusiasm and support implementation.
5. Enable action by removing barriers — Eliminate structural obstacles like outdated approval processes, misaligned incentives, or skill gaps that block progress.
6. Generate short-term wins — Deliver visible, early successes that build momentum and prove the change is working. This is critical for maintaining credibility.
7. Sustain acceleration — Use the credibility from early wins to tackle bigger, harder changes. Don't let up after initial progress.
8. Institute change — Embed the new behaviors into organizational culture, hiring practices, and performance systems so they become "how we do things here."

Kotter's model addresses a common failure point that Lewin's doesn't emphasize as much: the tendency to declare victory too early (step 7 exists specifically for this reason).

Top-down vs. bottom-up change approaches

These two approaches represent fundamentally different assumptions about where change should originate.

Top-down change is initiated and driven by senior leadership.

• Relies on formal authority and hierarchical structures to push changes through (directives, mandates, reorganizations)
• Can be implemented quickly because decisions don't require broad consensus
• Works well for urgent, organization-wide shifts like mergers, compliance requirements, or major strategic pivots
• The risk: employees who weren't consulted may resist or comply only superficially

Bottom-up change is initiated by employees at lower levels of the organization.

• Emerges from local adaptations, frontline innovations, and grassroots problem-solving
• Spreads through informal networks and peer influence rather than formal authority
• Tends to generate stronger employee buy-in because people feel ownership over the changes
• The risk: it's slower, harder to coordinate across the organization, and may lack strategic alignment

In practice, the most effective change efforts often blend both approaches. Senior leaders set the direction and remove barriers (top-down), while frontline employees adapt the changes to local realities and surface problems early (bottom-up).

Managing Emergent Change

Complex adaptive systems for emergent change

Not all change can be planned in advance. Emergent change arises organically as organizations respond to shifting conditions, and it's best understood through the lens of complex adaptive systems (CAS).

A CAS perspective treats organizations not as machines to be engineered but as living systems made up of many interacting agents (employees, teams, departments). These interactions produce non-linear dynamics, meaning small actions can sometimes trigger large, unpredictable outcomes. The system adapts and self-organizes in response to its environment without anyone directing every move from the top.

Managing emergent change within this framework involves three key practices:

1. Embrace self-organization and local experimentation

   • Allow teams to run pilot projects and test new approaches without waiting for top-level approval for every detail
   • Set minimal constraints and simple guiding principles rather than rigid procedures, so people have room to adapt

2. Leverage informal networks and relationships

   • Foster connections across departmental boundaries through communities of practice, cross-functional projects, or shared digital spaces
   • Identify opinion leaders and informal influencers who can accelerate the spread of new ideas

3. Monitor and adapt to emerging patterns

   • Continuously sense what's happening on the ground and respond quickly, similar to an agile approach
   • Use feedback loops to amplify changes that are working and correct those that aren't

The CAS perspective is especially useful when the environment is volatile and unpredictable, because it doesn't assume leaders can foresee every outcome. Instead, it positions the organization to learn and adapt in real time.

Change Implementation and Organizational Dynamics

Overcoming resistance and fostering engagement

Resistance to change is normal, not a sign of failure. People resist for legitimate reasons: fear of job loss, uncertainty about new expectations, past experiences with poorly managed change, or simply not understanding why the change is happening.

To address resistance effectively:

• Diagnose the sources. Is the resistance rooted in lack of information, lack of trust, lack of skill, or genuine disagreement with the direction? Each requires a different response.
• Communicate early and often. Explain the reasons for the change and its expected benefits. Vague announcements breed anxiety; specific, honest communication builds trust.
• Involve stakeholders from the start. People who participate in planning a change are far more likely to support its execution. Tailor your engagement approach to different groups, because what a senior manager needs to hear differs from what a frontline employee needs.

Change readiness is also worth assessing before launching a major initiative. This means evaluating whether the organization has the capacity (resources, skills, bandwidth) and the willingness (motivation, trust in leadership) to take on the change. If readiness is low, invest in training, communication, and relationship-building before pushing forward.

Leadership and organizational factors

Transformational leadership is strongly linked to successful change. Transformational leaders inspire employees through a compelling vision, model the behaviors they want to see, and encourage innovation and calculated risk-taking. They don't just announce change; they make people want to be part of it.

Organizational culture can either accelerate or derail change efforts. If the change aligns with existing cultural values, implementation is smoother. If it conflicts with deeply held norms, leaders face a harder task: they need to actively work on shifting the culture itself, reinforcing desired behaviors through recognition, incentives, and consistent messaging.

Organizational learning ties everything together. Organizations that treat each change effort as a learning opportunity, capturing what worked, what didn't, and why, build a stronger capacity for future change. Fostering a learning mindset means encouraging knowledge sharing, tolerating thoughtful failures, and using after-action reviews to inform the next initiative.