Managing Organizational Change: Models That Actually Work
Every significant product initiative is, at its core, a change management challenge. New products require users to change their workflows. New features require teams to change their processes. Platform migrations require entire organizations to adopt new systems. The most technically excellent product that isn’t adopted hasn’t created value — and the difference between adoption and non-adoption is often determined by how well the change that adoption requires is managed.
Understanding the change management models that provide the most practical guidance — and knowing when to apply each — is one of the less commonly developed but highly valuable capabilities in the product management toolkit.
Kotter’s 8-Step Change Model
John Kotter’s model was developed from studying large-scale organizational transformations and identifies eight sequential steps for successful change: creating urgency, forming a guiding coalition, developing a vision and strategy, communicating the vision, enabling broad-based action, generating short-term wins, consolidating gains, and anchoring new approaches in the culture.
The model’s strength is its emphasis on the social and motivational dimensions of change — creating the felt urgency and the coalition of support that large-scale transformation requires. It’s most applicable to large, complex organizational changes and less applicable to the smaller-scale product adoption challenges that PMs more commonly face.
The Prosci ADKAR Model
ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) describes the individual-level change journey that organizational change requires everyone to complete. People must become aware that change is happening, develop the desire to participate, acquire the knowledge to participate, develop the ability to perform new behaviors, and experience the reinforcement that makes new behaviors durable.
The model’s practical value is its diagnostic utility: when change is failing, ADKAR helps identify where in the individual change journey the failure is occurring. Is it awareness (people don’t know the change is happening), desire (they know but don’t want to change), or ability (they want to change but can’t)?
Lewin’s Unfreeze-Change-Refreeze
Kurt Lewin’s classic model describes change as requiring three phases: unfreezing (creating readiness to change by destabilizing the current state), change (implementing the new behaviors or systems), and refreezing (stabilizing the new state so it becomes the new baseline).
The model’s insight — that change requires deliberate unfreezing before it can occur — is most practically useful for product changes that require users to abandon existing habits before they can adopt new ones. Features that compete with established workflows need to create a reason to unfreeze before they can drive adoption.
Key Takeaways
Change management models provide structured frameworks for the social and behavioral dimensions of product adoption that technical excellence alone can’t address. Kotter’s model is most relevant to large organizational transformations; ADKAR is most diagnostically useful for identifying where individual-level change is failing; Lewin’s model is most relevant for changes that require abandoning established habits. Product managers who develop fluency with these models bring a genuinely undervalued capability to product adoption challenges.