leading product change (kotter's model)

Product managers are change agents. Every feature you ship asks users and internal teams to change how they work. Every roadmap revision asks the organization to reprioritize. Every new product strategy asks leadership to change what they believe is true about the market.

Why change initiatives fail

Research consistently shows that 60-70% of organizational change initiatives fail. The causes are predictable:

• Insufficient sense of urgency: Change requires people to abandon comfortable routines. Without a compelling reason to change, inertia wins.
• No guiding coalition: Change led by one person, even a senior one, stalls. Change requires a coalition of credible advocates across the organization.
• Lack of a clear vision: People resist change when they cannot see what they are changing toward. Vision is not strategy — it is an emotionally compelling picture of a better future state.
• Under-communication: One email announcement is not change communication. The vision needs to be communicated across multiple channels, multiple times, through multiple voices.
• Not removing obstacles: Even willing adopters fail if the organizational systems (incentives, processes, tools) are still optimized for the old way.
• Celebrating too early: Declaring victory at the first sign of progress invites regression. Change is not complete until new behaviors are embedded in culture and processes.
• Change not anchored in culture: Changes that are not connected to the organization's identity and values revert when pressure increases.

Kotter's nine-step change management model

John Kotter's model, derived from studying dozens of successful and failed change initiatives, describes nine steps. The model applies to organizational change broadly — and maps cleanly to how PMs should manage major product changes.

Step 1: Establish a sense of urgency

Change begins with people believing the status quo is not sustainable. Without urgency, there is no energy for change. As a PM, you create urgency by making the cost of not changing concrete and visible: data on user churn, competitive moves, market shifts, or customer feedback that makes the problem undeniable.

"Our activation rate dropped from 45% to 38% in three months" creates more urgency than "we should improve activation." The specific, current data is the urgency lever.

Step 2: Create a guiding coalition

You need allies. For a major product change, identify the 3-5 people in the organization whose endorsement will move others. This coalition must include: someone with organizational authority, someone with technical credibility, and someone with user proximity (customer success, sales, or support). Build their understanding and buy-in before the broader rollout.

Step 3: Develop a clear vision

The vision answers: what will be true in 12-18 months if we execute this change successfully? It should be simple enough to explain in 90 seconds, emotionally compelling, and connected to the organization's goals. A product vision like "every new user reaches their first meaningful outcome within 7 minutes" is more compelling than "improve onboarding metrics."

Step 4: Communicate the vision

Communicate through every available channel. Use stories, not just data. Involve the guiding coalition in communication — peer-to-peer communication is more trusted than top-down announcements. Address concerns explicitly rather than dismissing them.

Step 5: Empower broad-based action

Remove the obstacles that prevent people from acting on the vision. For product changes, this often means: updating internal tools to support the new workflow, revising incentive systems that reward old behavior, and providing training and documentation. The most common failure here is identifying obstacles but not removing them because "that's someone else's problem."

Step 6: Generate short-term wins

Early momentum is crucial for sustaining change. Identify and celebrate quick wins within the first 60-90 days. These wins prove to skeptics that the change is working and give the guiding coalition evidence to show the broader organization.

Step 7: Consolidate gains and produce more change

Use early wins to push for deeper change. Change leaders who stop at the first win allow organizational inertia to pull the change backward. Each win should create platform for the next wave of change.

Step 8: Anchor new approaches in culture

Connect the change to the organization's identity and values. Show explicitly how the new ways of working connect to what the organization cares about. Reinforce through hiring, performance management, and public recognition.

Step 9: Evaluate and iterate

Measure the outcomes of the change. What worked? What did not? What needs adjustment? This feeds the next cycle.

The PM's application: launching a major product change

For a significant product change — a redesigned core flow, a new pricing model, a major feature deprecation — the change management work runs in parallel with the product work:

Before launch: Identify the guiding coalition. Brief customer success, sales, and leadership before external communication. Build internal advocates. Create training materials and FAQ documents. Define early success metrics.

At launch: Over-communicate. Use multiple channels. Tell stories about early users who benefited. Make it easy for the organization to explain the change to customers.

After launch: Celebrate early wins publicly. Track and share adoption metrics. Address obstacles as soon as they appear. Do not let early momentum die from neglect.